bgpreport

Network · data from 2026-11-12

AS9913 IIG-AS-AP - Internet Information Group

Registry name: IIG-AS-AP - Internet Information Group, AU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9913, 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.
2400:9c20::/32 No ROA RIR databaseAPNIC, RADB 635 100% 67
202.14.148.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
203.1.68.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
203.1.69.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
203.31.110.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
203.31.111.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
203.57.23.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.233.208.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.233.209.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.233.210.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.233.211.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67

AS-SET

AS9913 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 8 are in fix.csv.

  • ROA: none1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none2400:9c20::/32No ROA covers it. Add a ROA for AS9913, maxLength 32.635 of 636

Route objects not announced

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

203.0.80.0/24APNIC, RADBValid
203.1.68.0/23RADBNo ROA
203.31.110.0/23RADBNo ROA
203.56.78.0/24RADBNo ROA
203.57.10.0/24RADBNo ROA
203.61.192.0/24RADBNo ROA
210.8.240.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.