Network report
Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
Warning: AS39635 (MMI-AS) announces 3 IPv4 and 0 IPv6 prefixes. 2 warnings
| AS page | AS39635 |
|---|---|
| Holder | MMI-AS Mini Maritsa Iztok EAD |
| Allocation | RIPE NCC, Bulgaria (BG), allocated 2006-03-30 |
| Prefixes (IPv4 / IPv6) | 3 / 0 |
| RPKI valid | 100% (3 / 3) |
| Upstreams and peers | 2 |
What to fix
-
Warning
No IPv6 prefixes announced.
Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.
Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.
- Warning
Checks
Routing and RPKI No IPv6 prefixes announced.
- Pass: AS39635 announces 3 IPv4 and 0 IPv6 prefixes.
- Warning: No IPv6 prefixes announced.
- Pass: All 3 announced prefixes are RPKI valid.
- Pass: Every announced prefix has an IRR route object.
- Info: 2 upstreams and peers, 0 downstream networks seen.
| Holder | MMI-AS Mini Maritsa Iztok EAD |
|---|---|
| IPv4 prefixes | 3 |
| IPv6 prefixes | 0 |
| RPKI | 3 valid |
| Downstream networks | 0 |
Upstreams and peers seen to the left 2
Announced prefixes 3
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration The registry is limiting how often it can be asked. Please try again in a minute.
PeeringDB PeeringDB did not answer: HTTP 404
- Warning: PeeringDB did not answer: HTTP 404
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup