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: AS8312 (ZYLON-AS) announces 9 IPv4 and 1 IPv6 prefixes. 2 warnings
| AS page | AS8312 |
|---|---|
| Holder | ZYLON-AS Bas Smit trading as Zylon |
| Allocation | RIPE NCC, Netherlands (NL), allocated 2004-11-11 |
| Prefixes (IPv4 / IPv6) | 9 / 1 |
| RPKI valid | 90% (9 / 10) |
| Upstreams and peers | 1 |
What to fix
-
Warning
1 of 10 announced prefixes have no ROA (RPKI not found): 193.193.165.0/24.
Without a ROA, networks cannot tell your routes from a hijack.
Fix: Create a ROA for each at your RIR portal, with origin AS8312 and a max length equal to the prefix length:
193.193.165.0/24 AS8312 max-length /24
- Warning
Checks
Routing and RPKI 1 of 10 announced prefixes have no ROA (RPKI not found): 193.193.165.0/24.
- Pass: AS8312 announces 9 IPv4 and 1 IPv6 prefixes.
- Warning: 1 of 10 announced prefixes have no ROA (RPKI not found): 193.193.165.0/24.
- Info: 9 of 10 announced prefixes are RPKI valid.
- Pass: Every announced prefix has an IRR route object.
- Info: One upstream or peer seen (AS31477): an outage there takes the whole network off the internet.
| Holder | ZYLON-AS Bas Smit trading as Zylon |
|---|---|
| IPv4 prefixes | 9 |
| IPv6 prefixes | 1 |
| RPKI | 9 valid · 1 not found |
| Downstream networks | 0 |
| Prefix | RPKI |
|---|---|
| 193.193.165.0/24 | No ROA |
Upstreams and peers seen to the left 1
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