bgpreport

Network · data from 2026-11-12

AS10022 Datacom Group

Registry name: DSLAK-AS-AP - Internet access for Datacom Systems Auckland, NZ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10022, 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.

103.88.230.0/24 No ROA Other IRR onlyRADB 671 100% 68
103.88.231.0/24 No ROA Other IRR onlyRADB 671 100% 68
202.27.64.0/24 No ROA Other IRR onlyRADB 671 100% 68
202.27.65.0/24 No ROA Other IRR onlyRADB 671 100% 68
202.37.23.0/24 No ROA Other IRR onlyRADB 671 100% 68
210.55.5.0/24 No ROA Other IRR onlyRADB 671 100% 68
192.188.71.0/24 No ROA Other IRR onlyRADB 670 100% 69
203.214.200.0/23 Valid Other IRR onlyRADB 671 100% 68
203.214.202.0/23 Valid Other IRR onlyRADB 671 100% 68
202.14.24.0/21 Valid RIR databaseAPNIC, RADB 672 100% 68
202.50.100.0/24 Valid RIR databaseAPNIC 672 100% 68
103.20.136.0/22 Valid RIR databaseAPNIC, RADB 671 100% 68
103.224.107.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
202.14.20.0/22 Valid RIR databaseAPNIC, RADB 671 100% 68
202.27.76.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
202.36.8.0/22 Valid RIR databaseAPNIC, RADB 671 100% 68
202.36.199.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
202.36.233.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
202.175.128.0/21 Valid RIR databaseAPNIC, RADB 671 100% 68
202.175.137.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
202.175.138.0/23 Valid RIR databaseAPNIC, RADB 671 100% 68
203.176.116.0/23 Valid RIR databaseAPNIC, RADB 671 100% 68
203.176.118.0/23 Valid RIR databaseAPNIC, RADB 671 100% 68
203.176.119.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
192.188.185.0/24 Valid RIR databaseAPNIC, RADB 670 100% 69
192.203.216.0/24 Valid RIR databaseAPNIC, RADB 670 100% 69
202.27.77.0/24 Valid RIR databaseAPNIC, RADB 670 100% 69
202.175.140.0/24 Valid RIR databaseAPNIC, RADB 670 100% 69
202.175.141.0/24 Valid RIR databaseAPNIC, RADB 670 100% 69
202.175.142.0/24 Valid RIR databaseAPNIC, RADB 670 100% 69
202.175.143.0/24 Valid RIR databaseAPNIC, RADB 670 100% 69
203.176.117.0/24 Valid RIR databaseAPNIC 670 100% 67

AS-SET

AS10022's PeeringDB record names no 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 34 are in fix.csv.

  • ROA: none7
  • Route object: RIR9
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
ROA: none103.88.230.0/24No ROA covers it. Add a ROA for AS10022, maxLength 24.671 of 673
Route object: RIR103.88.230.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.88.231.0/24No ROA covers it. Add a ROA for AS10022, maxLength 24.671 of 673
Route object: RIR103.88.231.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.27.64.0/24No ROA covers it. Add a ROA for AS10022, maxLength 24.671 of 673
Route object: RIR202.27.64.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.27.65.0/24No ROA covers it. Add a ROA for AS10022, maxLength 24.671 of 673
Route object: RIR202.27.65.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.37.23.0/24No ROA covers it. Add a ROA for AS10022, maxLength 24.671 of 673
Route object: RIR202.37.23.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none210.55.5.0/24No ROA covers it. Add a ROA for AS10022, maxLength 24.671 of 673
Route object: RIR210.55.5.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none192.188.71.0/24No ROA covers it. Add a ROA for AS10022, maxLength 24.670 of 673
Route object: RIR192.188.71.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR203.214.200.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR203.214.202.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

192.88.190.0/24RADBNo ROA
202.27.76.0/23RADBNo ROA
202.36.8.0/21RADBNo ROA
202.36.8.0/24APNIC, RADBValid
202.36.9.0/24APNIC, RADBValid
202.36.10.0/24APNIC, RADBValid
202.36.11.0/24APNIC, RADBValid
202.36.12.0/24APNICValid
202.36.198.0/23RADBNo ROA
202.36.198.0/24RADBNo ROA
202.49.216.0/24RADBNo ROA
202.175.142.0/23RADBNo ROA
203.176.116.0/24APNICValid
203.176.118.0/24APNICValid
2405:ac00::/36APNIC, RADBValid
2405:ac00:2000::/36APNIC, RADBValid
2405:ac00:4000::/36APNICValid
2405:ac00:6000::/36APNICValid

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.