Network · data from 2026-11-12
AS45570 NETPRES-AS-AP - Network Presence
Registry name: NETPRES-AS-AP - Network Presence, AU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS45570, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 203.17.225.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 103.1.204.0/22 | No ROA | Other IRR onlyNTTCOM, RADB | 3 0%low visibility |
| 113.212.98.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 113.212.98.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 113.212.99.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 113.212.96.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 113.212.97.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 163.47.117.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 163.47.119.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.0.155.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 2400:c401::/32 | Valid | RIR databaseAPNIC, RADB | 636 100% |
| 2400:c400::/32 | Valid | RIR databaseAPNIC, NTTCOM | 635 100% |
AS-SET
AS45570 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 49 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced45
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.17.225.0/24 | No ROA covers it. Add a ROA for AS45570, maxLength 24. |
| Route object: RIR | 203.17.225.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 103.1.204.0/22 | No ROA covers it. Add a ROA for AS45570, maxLength 22. |
| Route object: RIR | 103.1.204.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS45570 whose prefix no peer sees AS45570 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.1.204.0/24 | RADB | No ROA |
| 103.1.205.0/24 | RADB | No ROA |
| 103.1.206.0/24 | RADB | No ROA |
| 113.212.96.0/22 | APNIC, RADB | Valid |
| 125.63.48.0/20 | RADB | No ROA |
| 125.63.48.0/24 | RADB | No ROA |
| 125.63.49.0/24 | RADB | No ROA |
| 125.63.50.0/24 | RADB | No ROA |
| 125.63.51.0/24 | RADB | No ROA |
| 125.63.52.0/24 | RADB | No ROA |
| 125.63.53.0/24 | RADB | No ROA |
| 125.63.54.0/24 | RADB | No ROA |
| 125.63.55.0/24 | RADB | No ROA |
| 125.63.56.0/21 | RADB | No ROA |
| 125.63.56.0/24 | RADB | No ROA |
| 125.63.57.0/24 | RADB | No ROA |
| 125.63.58.0/24 | RADB | No ROA |
| 125.63.59.0/24 | RADB | No ROA |
| 125.63.60.0/24 | RADB | No ROA |
| 125.63.61.0/24 | RADB | No ROA |
| 125.63.62.0/24 | RADB | No ROA |
| 125.63.63.0/24 | RADB | No ROA |
| 163.47.116.0/22 | APNIC, NTTCOM, RADB | No ROA |
| 163.47.116.0/23 | APNIC | No ROA |
| 163.47.116.0/24 | APNIC | No ROA |
| 163.47.118.0/23 | APNIC | No ROA |
| 163.47.118.0/24 | APNIC, RADB | Valid |
| 203.18.235.0/24 | NTTCOM, RADB | No ROA |
| 2400:c400::/33 | APNIC | Valid |
| 2400:c400:8000::/35 | APNIC | Valid |
| 2400:c400:a000::/48 | APNIC, NTTCOM, RADB | Valid |
| 2400:c400:a001::/48 | APNIC | Valid |
| 2400:c400:a002::/47 | APNIC | Valid |
| 2400:c400:a004::/46 | APNIC | Valid |
| 2400:c400:a008::/45 | APNIC | Valid |
| 2400:c400:a010::/44 | APNIC | Valid |
| 2400:c400:a020::/43 | APNIC | Valid |
| 2400:c400:a040::/42 | APNIC | Valid |
| 2400:c400:a080::/41 | APNIC | Valid |
| 2400:c400:a100::/40 | APNIC | Valid |
| 2400:c400:a200::/39 | APNIC | Valid |
| 2400:c400:a400::/38 | APNIC | Valid |
| 2400:c400:a800::/37 | APNIC | Valid |
| 2400:c400:b000::/36 | APNIC | Valid |
| 2400:c400:c000::/34 | APNIC | Valid |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.