AS12897
ISPENTEGAMEDIANET
Also known as: formerly known as HEAG MediaNet GmbH (1996-2011) and HSE Medianet GmbH (2011-2016)
ENTEGA Medianet GmbH
32
IPv4 Prefixes
0
IPv6 Prefixes
163.6K
IPv4 Addresses
RIR
RIPE
Scope
Regional
Traffic
100-200Gbps
Ratio
Mostly Inbound
Peering
Selective
IRR AS-SET
RIPE::AS-MEDIANET
Risk Score
0/100
Network Characteristics
Unknown
Residential Customers
IPv6 Enabled
宣告的前缀 (显示前 32 个)
| 前缀 | 网络类型 | 风险分 | 标签 | 首次发现 |
|---|---|---|---|---|
| 5.182.236.0/22 | isp | 0 |
住宅
|
2026-01-31 |
| 45.10.60.0/22 | isp | 0 |
住宅
|
2026-01-31 |
| 45.14.188.0/22 | isp | 0 |
住宅
|
2026-01-31 |
| 45.93.108.0/22 | isp | 0 |
住宅
|
2026-01-31 |
| 45.128.180.0/22 | isp | 0 |
住宅
|
2026-01-31 |
| 45.131.36.0/22 | isp | 0 |
住宅
|
2026-01-31 |
| 45.136.168.0/22 | isp | 0 |
住宅
|
2026-01-31 |
| 45.143.76.0/22 | isp | 0 |
住宅
|
2026-01-31 |
| 46.243.80.0/21 | isp | 0 |
住宅
|
2026-01-31 |
| 85.132.192.0/19 | isp | 0 |
住宅
|
2026-01-31 |
| 92.119.8.0/22 | isp | 0 |
住宅
|
2026-01-31 |
| 94.16.64.0/19 | isp | 0 |
住宅
|
2026-01-31 |
| 94.46.64.0/19 | isp | 0 |
住宅
|
2026-01-31 |
| 95.131.96.0/21 | isp | 0 |
住宅
|
2026-01-31 |
| 134.101.16.0/20 | isp | 0 |
住宅
|
2026-01-31 |
| 139.29.127.0/24 | isp | 0 |
住宅
|
2026-01-31 |
| 141.187.0.0/16 | isp | 0 |
住宅
|
2026-01-31 |
| 145.224.39.0/24 | isp | 0 |
住宅
|
2026-01-31 |
| 149.249.128.0/19 | isp | 0 |
住宅
|
2026-01-31 |
| 185.9.28.0/22 | isp | 0 |
住宅
|
2026-01-31 |
| 185.101.36.0/24 | isp | 0 |
住宅
|
2026-01-31 |
| 185.117.68.0/22 | isp | 0 |
住宅
|
2026-01-31 |
| 185.189.140.0/22 | isp | 0 |
住宅
|
2026-01-31 |
| 185.194.64.0/22 | isp | 0 |
住宅
|
2026-01-31 |
| 185.238.252.0/22 | isp | 0 |
住宅
|
2026-01-31 |
| 195.2.160.0/19 | isp | 0 |
住宅
|
2026-01-31 |
| 195.80.52.0/22 | isp | 0 |
住宅
|
2026-01-31 |
| 212.126.192.0/19 | isp | 0 |
住宅
|
2026-01-31 |
| 212.232.80.0/20 | isp | 0 |
住宅
|
2026-01-31 |
| 213.157.0.0/19 | isp | 0 |
住宅
|
2026-01-31 |
| 213.188.96.0/19 | isp | 0 |
住宅
|
2026-01-31 |
| 217.173.144.0/20 | isp | 0 |
住宅
|
2026-01-31 |
PeeringDB 备注
We have a selective but generally open peering policy and evaluate each request based on its value for our network.
Peering through route servers is usually preferred over direct BGP sessions, especially for low-volume, low-prefix peers that already use the route servers.
This is to avoid unnecessary maintenance and configuration overhead.
For direct BGP sessions we require a significant amount of traffic coming from or destined to your network.
Also an up-to-date PeeringDB entry is required for all public peering requests.
PNIs are preferred for peers with 95/5 > 3 Gbps.
* We filter all our customers with strict prefix-lists, no exceptions.
* We filter RPKI invalids on all sessions.
* We filter TIER1 ASNs in path on all peering + customer sessions.
* We do not accept prefixes smaller than /24 (IPv4) or /48 (IPv6).
Additional BCP filtering as strictly as possible and other security measures are implied.
Please review your registered ROAs to reduce number of invalid prefixes.
API 调用
# 使用 cURL 查询此 ASN
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://ipv4.dev/api/v1/asn/12897"