bgpreport

Network · data from 2026-11-12

AS24015 SPINETWORKS-AS-AP - SPI Networks, Electricity Distribution, Victoria

Registry name: SPINETWORKS-AS-AP - SPI Networks, Electricity Distribution, Victoria, AU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS24015, 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.14.65.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
203.14.70.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
203.14.71.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
203.14.72.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
203.14.73.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67

AS-SET

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

  • ROA: none5
  • Route object: RIR5
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none203.14.65.0/24No ROA covers it. Add a ROA for AS24015, maxLength 24.672 of 673
Route object: RIR203.14.65.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none203.14.70.0/24No ROA covers it. Add a ROA for AS24015, maxLength 24.672 of 673
Route object: RIR203.14.70.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none203.14.71.0/24No ROA covers it. Add a ROA for AS24015, maxLength 24.672 of 673
Route object: RIR203.14.71.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none203.14.72.0/24No ROA covers it. Add a ROA for AS24015, maxLength 24.672 of 673
Route object: RIR203.14.72.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.14.73.0/24No ROA covers it. Add a ROA for AS24015, maxLength 24.672 of 673
Route object: RIR203.14.73.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

203.14.64.0/24NTTCOM, RADBNo ROA
203.14.66.0/24NTTCOM, RADBNo ROA
203.14.67.0/24NTTCOM, RADBNo ROA
203.14.68.0/24NTTCOM, RADBNo ROA
203.14.69.0/24NTTCOMNo ROA
203.14.74.0/24NTTCOM, RADBNo ROA
203.14.75.0/24NTTCOM, RADBNo ROA
203.14.76.0/24NTTCOM, RADBNo ROA
203.14.77.0/24NTTCOM, RADBNo ROA
203.14.78.0/24NTTCOM, RADBNo ROA
203.14.79.0/24NTTCOM, RADBNo 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.