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.
5.34.89.0/24 ·
Warning: 5.34.89.0/24 is announced by AS35566 (KARTEL-AS Kar-Tel LLC). 2 warnings
| Announced as | 5.34.89.0/24 |
|---|---|
| Origin AS | AS35566 KARTEL-AS Kar-Tel LLC |
| Allocation | RIPE NCC, Kazakhstan (KZ), allocated 2012-05-10 |
| Size | 256 addresses |
What to fix
-
Warning
5.34.89.0/24 from AS35566 is RPKI not found: no ROA covers it.
Routes without a ROA are still accepted almost everywhere, but nothing protects them from a hijack.
Fix: Create a ROA for this prefix with origin AS35566 and a max length equal to the prefix length.
prefix: 5.34.89.0/24 origin: AS35566 max-length: 24
-
Warning
No IRR route object for 5.34.89.0/24 with origin AS35566.
Many networks build their prefix filters from IRR data; without a route object some of them drop the route.
Fix: Create a route object in your RIR’s IRR database (or RADB):
route: 5.34.89.0/24 origin: AS35566
Checks
Routing and RPKI 5.34.89.0/24 from AS35566 is RPKI not found: no ROA covers it.
- Pass: Announced as 5.34.89.0/24 by AS35566.
- Warning: 5.34.89.0/24 from AS35566 is RPKI not found: no ROA covers it.
- Warning: No IRR route object for 5.34.89.0/24 with origin AS35566.
- Pass: Seen by 100% of RIPE RIS peers.
| Route | 5.34.89.0/24 |
|---|---|
| Origin AS | AS35566 KARTEL-AS Kar-Tel LLC No ROA |
| Visibility (RIS peers) | 321 / 321 |
| First seen | 2018-07-12 |
| Covering prefixes | 5.34.0.0/17 |
Source: RIPEstat (RIPE NCC RIS, Routinator)
Open in ASN & BGP prefix lookupReverse DNS Reverse DNS is delegated (89.34.5.in-addr.arpa).
- Pass: Reverse DNS is delegated (89.34.5.in-addr.arpa).
| Zone | Nameservers |
|---|---|
| 89.34.5.in-addr.arpa | ns.2day.kz, ns2.2day.kz |
Registration 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
About the network that announces this space, so not in the fix list.
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup