bgpreport

Network · data from 2026-11-12

AS17668 SPTEL-AP - Soul Pattinson Telecommunications Pty Ltd

Registry name: SPTEL-AP - Soul Pattinson Telecommunications Pty Ltd, AU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17668, 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.220.10.0/24 No ROA Other IRR onlyRADB 667 99% 67
203.220.18.0/24 No ROA Other IRR onlyRADB 667 99% 67
203.221.255.0/24 No ROA Other IRR onlyRADB 667 99% 67
125.254.32.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
125.254.34.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
202.59.16.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
202.59.17.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
202.59.18.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
202.59.19.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
202.59.20.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
202.59.21.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
202.59.24.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
202.59.25.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
202.59.26.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
202.59.27.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
202.59.28.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
202.59.31.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
202.59.22.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 67
202.59.23.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 67
202.59.29.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 67

AS-SET

AS17668 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 90 are in fix.csv.

  • ROA: none20
  • Route object: RIR17
  • Route object: not announced53
ChangePrefix or setDetailFull-table peers
ROA: none203.220.10.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.667 of 673
Route object: RIR203.220.10.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none203.220.18.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.667 of 673
Route object: RIR203.220.18.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none203.221.255.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.667 of 673
Route object: RIR203.221.255.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none125.254.32.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.2 of 673
Route object: RIR125.254.32.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none125.254.34.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.2 of 673
Route object: RIR125.254.34.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.59.16.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.2 of 673
Route object: RIR202.59.16.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.59.17.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.2 of 673
Route object: RIR202.59.17.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.59.18.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.2 of 673
Route object: RIR202.59.18.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.59.19.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.2 of 673
Route object: RIR202.59.19.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.59.20.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.2 of 673
Route object: RIR202.59.20.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.59.21.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.2 of 673
Route object: RIR202.59.21.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.59.24.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.2 of 673
Route object: RIR202.59.24.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.59.25.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.2 of 673
Route object: RIR202.59.25.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.59.26.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.2 of 673
Route object: RIR202.59.26.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.59.27.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.2 of 673
Route object: RIR202.59.27.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.59.28.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.2 of 673
Route object: RIR202.59.28.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.59.31.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.2 of 673
Route object: RIR202.59.31.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.59.22.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.671 of 673
ROA: none202.59.23.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.671 of 673
ROA: none202.59.29.0/24No ROA covers it. Add a ROA for AS17668, maxLength 24.671 of 673

Route objects not announced

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

148.145.48.0/24RADBNo ROA
202.168.31.0/24RADBNo ROA
203.1.16.0/24RADBNo ROA
203.3.192.0/24RADBNo ROA
203.3.193.0/24RADBNo ROA
203.3.194.0/24RADBNo ROA
203.3.195.0/24RADBNo ROA
203.3.196.0/24RADBNo ROA
203.3.200.0/24RADBNo ROA
203.3.224.0/24RADBNo ROA
203.3.225.0/24RADBNo ROA
203.3.226.0/24RADBNo ROA
203.3.227.0/24RADBNo ROA
203.3.254.0/24RADBNo ROA
203.5.106.0/24RADBNo ROA
203.15.72.0/22RADBNo ROA
203.21.150.0/24RADBNo ROA
203.21.151.0/24RADBNo ROA
203.21.192.0/23RADBNo ROA
203.21.194.0/24RADBNo ROA
203.21.195.0/24RADBNo ROA
203.22.168.0/24RADBNo ROA
203.23.90.0/24APNICInvalid: origin
203.25.149.0/24RADBNo ROA
203.27.239.0/24RADBNo ROA
203.32.245.0/24RADBNo ROA
203.32.247.0/24RADBNo ROA
203.57.8.0/24RADBNo ROA
203.220.11.0/24APNIC, RADBNo ROA
203.220.136.0/23RADBNo ROA
203.220.140.0/23RADBNo ROA
203.220.142.0/23RADBNo ROA
203.220.144.0/23RADBNo ROA
203.220.146.0/23RADBNo ROA
203.220.148.0/23RADBNo ROA
203.220.150.0/23RADBNo ROA
203.220.152.0/23RADBNo ROA
203.220.156.0/23RADBNo ROA
203.220.162.0/23RADBNo ROA
203.220.200.0/23RADBNo ROA
203.220.220.0/23RADBNo ROA
203.220.222.0/23RADBNo ROA
203.221.12.0/23RADBNo ROA
203.221.38.0/23RADBNo ROA
203.221.72.0/23RADBNo ROA
203.221.131.0/24RADBNo ROA
203.221.150.0/23RADBNo ROA
203.221.160.0/23RADBNo ROA
203.221.210.0/23RADBNo ROA
203.221.242.0/23RADBNo ROA
203.223.184.0/23RADBNo ROA
203.223.184.0/24RADBNo ROA
203.223.185.0/24RADBNo 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.