bgpreport

Network · data from 2026-11-12

AS23913 BluePackets

Registry name: BLUEPACKETS-AU - Blue Packets Trust, AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS23913, 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.
113.20.24.0/22 No ROA RIR databaseAPNIC, RADB 671 100% 67
103.69.198.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 670 100% 67

AS-SET

AS23913'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 4 are in fix.csv.

  • ROA: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none113.20.24.0/22No ROA covers it. Add a ROA for AS23913, maxLength 22.671 of 673
ROA: none103.69.198.0/24No ROA covers it. Add a ROA for AS23913, maxLength 24.670 of 673

Route objects not announced

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

192.190.66.0/24NTTCOMNo ROA
202.21.129.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.