bgpreport

Network · data from 2026-11-12

AS136013 NGA-AS-AP - National Gallery of Australia

Registry name: NGA-AS-AP - National Gallery of Australia, AU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136013, 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.20.18.0/24 No ROA Other origin onlycovered by 203.20.18.0/23 673 100% 69

AS-SET

AS136013 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 3 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none203.20.18.0/24No ROA covers it. Add a ROA for AS136013, maxLength 24.673 of 673
Route object: none203.20.18.0/24Route objects for it name AS7575, AS18111. A route object for 203.20.18.0/23 with origin AS136013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136013 in the RIR database for the space.673 of 673

Route objects not announced

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

203.20.18.0/23RADBNo 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.