bgpreport

Network · data from 2026-11-12

AS9303 KCCS

Registry name: TDL2L-AS-AP - The Digital Lab 2007 Limited, NZ · PeeringDB

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

Announced routes

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

202.27.192.0/21 No ROA Other IRR onlyRADB 673 100% 69
202.27.200.0/22 No ROA Other IRR onlyRADB 672 100% 67
202.27.216.0/22 No ROA Other IRR onlyRADB 672 100% 67
103.49.172.0/24 No ROA Other IRR onlyRADB 671 100% 68
103.24.136.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.24.137.0/24 Valid RIR databaseAPNIC 673 100% 68
103.24.138.0/24 Valid RIR databaseAPNIC 673 100% 68
103.24.139.0/24 Valid RIR databaseAPNIC 673 100% 68
202.14.102.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
202.27.209.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
202.27.217.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
202.37.70.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
202.37.71.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
203.9.216.0/23 Valid RIR databaseAPNIC 673 100% 68
202.20.65.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.20.92.0/24 Valid RIR databaseAPNIC 672 100% 67
202.21.157.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.27.210.0/24 Valid RIR databaseAPNIC 672 100% 67
202.27.211.0/24 Valid RIR databaseAPNIC 672 100% 67
202.27.213.0/24 Valid RIR databaseAPNIC 672 100% 67
202.27.214.0/24 Valid RIR databaseAPNIC 672 100% 67
202.27.215.0/24 Valid RIR databaseAPNIC 672 100% 67
202.27.216.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.27.218.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.27.219.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.27.222.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.27.236.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.27.251.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.37.117.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.37.118.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.49.141.0/24 Valid RIR databaseAPNIC 672 100% 67
202.49.189.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.50.95.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
2404:bf00::/40 Valid RIR databaseAPNIC, RADB 636 100% 69
2404:bf00:800::/40 Valid RIR databaseAPNIC, RADB 636 100% 69
2404:bf00:8000::/40 Valid RIR databaseAPNIC, RADB 636 100% 69
2404:bf00:8800::/40 Valid RIR databaseAPNIC, RADB 636 100% 69
202.36.43.0/24 Valid RIR databaseAPNIC, RADB 117 17% 37

AS-SET

AS9303'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 21 are in fix.csv.

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none202.27.192.0/21No ROA covers it. Add a ROA for AS9303, maxLength 21.673 of 673
Route object: RIR202.27.192.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.27.200.0/22No ROA covers it. Add a ROA for AS9303, maxLength 22.672 of 673
Route object: RIR202.27.200.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none202.27.216.0/22No ROA covers it. Add a ROA for AS9303, maxLength 22.672 of 673
Route object: RIR202.27.216.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.49.172.0/24No ROA covers it. Add a ROA for AS9303, maxLength 24.671 of 673
Route object: RIR103.49.172.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

103.24.136.0/22RADBNo ROA
103.209.224.0/22APNICValid
202.27.83.0/24RADBNo ROA
202.27.210.0/23RADBNo ROA
202.27.212.0/22RADBNo ROA
202.27.212.0/24APNICValid
202.27.247.0/24APNIC, RADBValid
202.37.70.0/23RADBNo ROA
202.49.183.0/24APNIC, RADBValid
203.18.59.0/24APNIC, RADBValid
203.25.187.0/24APNIC, RADBValid
203.189.24.0/24APNICValid
203.190.217.0/24APNICValid

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.