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.
Problem: AS134238 (CT-Jiangxi-IDC) announces 108 IPv4 and 10 IPv6 prefixes. 1 problem · 2 warnings
| AS page | AS134238 |
|---|---|
| Holder | CT-Jiangxi-IDC - CHINANET Jiangx province IDC network |
| Allocation | APNIC, China (CN), allocated 2015-06-11 |
| Prefixes (IPv4 / IPv6) | 108 / 10 |
| RPKI valid | 98% (116 / 118) |
| Upstreams and peers | 1 |
What to fix
-
Problem
2 of 118 announced prefixes are RPKI invalid: 106.225.204.0/23, 115.153.228.0/24.
A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.
Fix: Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes.
-
Warning
19 of 118 announced prefixes have no IRR route object: 106.225.198.0/23, 115.153.228.0/24, 106.225.208.0/21, 106.225.136.0/21, 106.225.144.0/24 (+14).
Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.
Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS134238 in your RIR’s IRR database (or RADB).
route: 106.225.198.0/23 origin: AS134238 route: 115.153.228.0/24 origin: AS134238 route: 106.225.208.0/21 origin: AS134238
- Warning
Checks
Routing and RPKI 2 of 118 announced prefixes are RPKI invalid: 106.225.204.0/23, 115.153.228.0/24.
- Pass: AS134238 announces 108 IPv4 and 10 IPv6 prefixes.
- Problem: 2 of 118 announced prefixes are RPKI invalid: 106.225.204.0/23, 115.153.228.0/24.
- Info: 116 of 118 announced prefixes are RPKI valid.
- Warning: 19 of 118 announced prefixes have no IRR route object: 106.225.198.0/23, 115.153.228.0/24, 106.225.208.0/21, 106.225.136.0/21, 106.225.144.0/24 (+14).
- Info: One upstream or peer seen (AS4134): an outage there takes the whole network off the internet.
| Holder | CT-Jiangxi-IDC - CHINANET Jiangx province IDC network |
|---|---|
| IPv4 prefixes | 108 |
| IPv6 prefixes | 10 |
| RPKI | 116 valid · 2 invalid |
| Without IRR route object | 19 |
| Downstream networks | 12 |
| Prefix | RPKI |
|---|---|
| 106.225.204.0/23 | RPKI invalid |
| 115.153.228.0/24 | RPKI invalid |
Upstreams and peers seen to the left 1
Announced prefixes 118
Showing the first 100.
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration Found at rdap.apnic.net.
- Pass: Found at rdap.apnic.net.
| Name | CT-Jiangxi-IDC |
|---|---|
| Handle | AS134238 |
| Range | AS134238 |
| Country | CN |
| Status | active |
| Registered | 2015-06-11T06:04:42Z |
| Last changed | 2020-05-14T11:17:56Z |
| Abuse contact | fjnic@fjdcb.fz.fj.cn |
| Registry (RIR) | APNIC |
|---|---|
| Country | China (CN) |
| Delegated on | 2015-06-11 |
| Status | Allocated |
| Delegated range | AS134238 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| abuse | IRT-CHINANET-FJ | fjnic@fjdcb.fz.fj.cn |
| administrative, technical | Chinanet Hostmaster | anti-spam@chinatelecom.cn |
Source: https://rdap.apnic.net/autnum/134238. Registration data from rdap.apnic.net, shown under its terms of use (terms): not for marketing or bulk collection.
Open in WHOIS / RDAP lookupPeeringDB 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