bgpreport

Network · data from 2026-11-12

AS59339 BLACKBIRDIT-AS-AP - BLACKBIRD IT PTY LTD

Registry name: BLACKBIRDIT-AS-AP - BLACKBIRD IT PTY LTD, AU · not in PeeringDB

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

Announced routes

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

103.93.24.0/23 Valid Other IRR onlyRADB 673 100% 68
103.197.186.0/23 Valid Other IRR onlyRADB 673 100% 68
103.93.25.0/24 Valid Other IRR onlyRADB 173 26% 52
160.250.244.0/23 Valid RIR databaseAPNIC 673 100% 68

AS-SET

AS59339 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 6 are in fix.csv.

  • Route object: RIR3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: RIR103.93.24.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.197.186.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.93.25.0/24Route object only in RADB. Add it in the RIR database for the space.173 of 673

Route objects not announced

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

103.93.24.0/24RADBValid
103.197.186.0/24RADBValid
103.197.187.0/24RADBValid

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.