bgpreport

Network · data from 2026-11-12

AS18111 NETSPEED-AS-AP - Netspeed Internet Communications

Registry name: NETSPEED-AS-AP - Netspeed Internet Communications, AU · not in PeeringDB

5IPv4 routes 80.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
47Route objects not announced registered with origin AS18111, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS18111, 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.130.160.0/20 No ROA Other IRR onlyRADB 673 100% 67
203.20.62.0/24 Valid RIR databaseAPNIC 671 100% 67
203.30.98.0/23 Valid RIR databaseAPNIC 671 100% 67
203.31.48.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
203.33.171.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67

AS-SET

AS18111 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: none1
  • Route object: RIR1
  • Route object: not announced47
ChangePrefix or setDetailFull-table peers
ROA: none203.130.160.0/20No ROA covers it. Add a ROA for AS18111, maxLength 20.673 of 673
Route object: RIR203.130.160.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS18111 whose prefix no peer sees AS18111 announce. Many are kept on purpose (backup routes, space announced only in some places).

122.49.200.0/21RADBNo ROA
180.214.168.0/21RADBNo ROA
202.46.136.0/21RADBNo ROA
202.78.32.0/20RADBNo ROA
202.92.240.0/21APNIC, RADBValid
202.92.240.0/22APNICValid
202.92.240.0/23APNICValid
202.92.240.0/24APNICValid
202.92.241.0/24APNICValid
202.92.242.0/23APNICValid
202.92.242.0/24APNICValid
202.92.243.0/24APNICValid
202.92.244.0/22APNICValid
202.92.244.0/23APNICValid
202.92.244.0/24APNICValid
202.92.245.0/24APNICValid
202.92.246.0/23APNICValid
202.92.246.0/24APNICValid
202.92.247.0/24APNICValid
202.168.16.0/21RADBNo ROA
203.17.68.0/24RADBNo ROA
203.20.18.0/24RADBNo ROA
203.22.236.0/22APNICValid
203.22.236.0/23APNICValid
203.22.236.0/24APNIC, RADBValid
203.22.237.0/24APNIC, RADBValid
203.22.238.0/23APNICValid
203.22.238.0/24APNIC, RADBValid
203.22.239.0/24APNIC, RADBValid
203.26.204.0/24RADBNo ROA
203.28.45.0/24APNICValid
203.29.64.0/24RADBNo ROA
203.32.183.0/24RADBNo ROA
203.34.140.0/24RADBNo ROA
203.34.141.0/24RADBNo ROA
203.34.200.0/24RADBNo ROA
203.55.120.0/23APNIC, RADBValid
203.55.120.0/24APNICValid
203.55.121.0/24APNICValid
203.55.137.0/24RADBNo ROA
203.55.152.0/24RADBNo ROA
203.56.186.0/24RADBNo ROA
203.130.160.0/24RADBNo ROA
203.130.162.0/24RADBNo ROA
203.221.196.0/23RADBNo ROA
210.9.156.196/30RADBNo ROA
210.9.230.0/23RADBNo ROA

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.