bgpreport

Network · data from 2026-11-12

AS9544 Preferred Internet Provider

Registry name: PIP-AS-AP - Clarenston T/A Preferred Internet Provider, AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9544, 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.23.121.0/24 No ROA Other origin only 670 100% 67
203.23.120.0/24 No ROA Other IRR onlyRADB 670 100% 67
203.24.52.0/24 No ROA Other IRR onlyRADB 670 100% 67
203.24.53.0/24 No ROA Other IRR onlyRADB 670 100% 67
203.27.90.0/24 No ROA Other IRR onlyRADB 670 100% 67
203.27.91.0/24 No ROA Other IRR onlyRADB 670 100% 67
203.34.24.0/24 No ROA Other IRR onlyRADB 670 100% 67
203.34.25.0/24 No ROA Other IRR onlyRADB 670 100% 67

AS-SET

AS9544'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 16 are in fix.csv.

  • ROA: none8
  • Route object: none1
  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
ROA: none203.23.121.0/24No ROA covers it. Add a ROA for AS9544, maxLength 24.670 of 673
Route object: none203.23.121.0/24Route objects for it name AS10143. Add a route object with origin AS9544 in the RIR database for the space.670 of 673
ROA: none203.23.120.0/24No ROA covers it. Add a ROA for AS9544, maxLength 24.670 of 673
Route object: RIR203.23.120.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none203.24.52.0/24No ROA covers it. Add a ROA for AS9544, maxLength 24.670 of 673
Route object: RIR203.24.52.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none203.24.53.0/24No ROA covers it. Add a ROA for AS9544, maxLength 24.670 of 673
Route object: RIR203.24.53.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none203.27.90.0/24No ROA covers it. Add a ROA for AS9544, maxLength 24.670 of 673
Route object: RIR203.27.90.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none203.27.91.0/24No ROA covers it. Add a ROA for AS9544, maxLength 24.670 of 673
Route object: RIR203.27.91.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none203.34.24.0/24No ROA covers it. Add a ROA for AS9544, maxLength 24.670 of 673
Route object: RIR203.34.24.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none203.34.25.0/24No ROA covers it. Add a ROA for AS9544, maxLength 24.670 of 673
Route object: RIR203.34.25.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

Every route object with origin AS9544 is announced.

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.