bgpreport

Network · data from 2026-11-12

AS133480 Intergrid

Registry name: INT-5GN-AS-AP - 5G NETWORK OPERATIONS PTY LTD, AU · PeeringDB

35IPv4 routes 88.6% RPKI valid · 100.0% with a route object
10IPv6 routes 90.0% RPKI valid · 100.0% with a route object
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
41Route objects not announced registered with origin AS133480, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS133480, 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.137.56.0/24 No ROA Other IRR onlyRADB 671 100% 67
202.50.84.0/24 No ROA Other IRR onlyRADB 671 100% 67
2607:6b80:5e::/48 No ROA Other IRR onlyRADB 635 100% 69
103.137.119.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 67
103.140.134.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 67
45.125.125.0/24 Valid RIR databaseAPNIC 672 100% 67
103.194.4.0/24 Valid RIR databaseAPNIC 672 100% 67
43.245.160.0/24 Valid RIR databaseAPNIC 671 100% 67
43.245.161.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
43.245.162.0/24 Valid RIR databaseAPNIC 671 100% 67
43.245.163.0/24 Valid RIR databaseAPNIC 671 100% 67
103.76.164.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.76.165.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.77.232.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.77.233.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.77.234.0/24 Valid RIR databaseAPNIC 671 100% 67
103.77.235.0/24 Valid RIR databaseAPNIC 671 100% 67
103.108.92.0/24 Valid RIR databaseAPNIC 671 100% 67
103.108.93.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.108.94.0/24 Valid RIR databaseAPNIC 671 100% 67
103.108.95.0/24 Valid RIR databaseAPNIC 671 100% 67
103.192.173.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.231.88.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.231.89.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.231.90.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.231.91.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
116.206.228.0/24 Valid RIR databaseAPNIC 671 100% 67
116.206.229.0/24 Valid RIR databaseAPNIC 671 100% 67
116.206.230.0/24 Valid RIR databaseAPNIC 671 100% 67
116.206.231.0/24 Valid RIR databaseAPNIC 671 100% 67
203.18.16.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
203.18.17.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
203.209.209.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
203.209.212.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
203.209.217.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
203.209.219.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
2407:a080::/48 Valid RIR databaseAPNIC, RADB 635 100% 69
2407:a080:7000::/36 Valid RIR databaseAPNIC, RADB 635 100% 69
2400:fa80:1::/48 Valid RIR databaseAPNIC, NTTCOM 634 100% 69
2400:fa80:4::/48 Valid RIR databaseAPNIC 634 100% 69
2400:fa80:5::/48 Valid RIR databaseAPNIC 634 100% 69
2400:fa80:6::/48 Valid RIR databaseAPNIC 634 100% 69
2407:a080::/32 Valid RIR databaseAPNIC, NTTCOM 634 100% 69
2407:a080:2000::/48 Valid RIR databaseAPNIC 634 100% 69
2407:a080:5000::/36 Valid RIR databaseAPNIC 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS133480: AS-INTERGRID. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS133480 isn't in the set, or no route object for AS133480 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS133480 in itNot covered
AS-INTERGRID APNIC 42275 Yes 0

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

  • ROA: none5
  • Route object: RIR3
  • Route object: not announced41
ChangePrefix or setDetailFull-table peers
ROA: none103.137.56.0/24No ROA covers it. Add a ROA for AS133480, maxLength 24.671 of 673
Route object: RIR103.137.56.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.50.84.0/24No ROA covers it. Add a ROA for AS133480, maxLength 24.671 of 673
Route object: RIR202.50.84.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2607:6b80:5e::/48No ROA covers it. Add a ROA for AS133480, maxLength 48.635 of 636
Route object: RIR2607:6b80:5e::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none103.137.119.0/24No ROA covers it. Add a ROA for AS133480, maxLength 24.671 of 673
ROA: none103.140.134.0/24No ROA covers it. Add a ROA for AS133480, maxLength 24.671 of 673

Route objects not announced

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

43.228.159.0/24RADBNo ROA
43.245.160.0/23APNIC, RADBNo ROA
43.245.162.0/23APNIC, RADBNo ROA
45.54.84.0/23RADBNo ROA
103.77.232.0/22NTTCOMNo ROA
103.77.232.0/23APNIC, RADBNo ROA
103.77.234.0/23APNIC, RADBNo ROA
103.108.92.0/22APNIC, RADBValid
103.108.92.0/23APNICValid
103.108.94.0/23APNICValid
103.191.36.0/23RADBNo ROA
103.231.88.0/22NTTCOM, RADBNo ROA
103.231.88.0/23NTTCOMNo ROA
103.231.90.0/23NTTCOMNo ROA
116.206.228.0/22RADBNo ROA
116.206.228.0/23RADBNo ROA
116.206.230.0/23RADBNo ROA
168.1.133.0/24RADBNo ROA
185.190.83.0/24RADBValid
193.180.80.0/24RADBNo ROA
194.110.172.0/23RADBNo ROA
202.47.81.0/24RADBNo ROA
203.17.122.0/24APNICValid
2400:fa80::/32APNIC, NTTCOMNo ROA
2400:fa80:3::/48APNICValid
2402:1b80:3002::/48APNICValid
2407:a080:2000::/36APNICInvalid: maxLength
2407:a080:3000::/36APNICInvalid: maxLength
2407:a080:4000::/36APNICInvalid: maxLength
2407:c280:8005::/48RADBNo ROA
2407:c280:8006::/48RADBNo ROA
2407:c280:8007::/48RADBNo ROA
2407:c280:8008::/48RADBNo ROA
2407:c280:8009::/48RADBNo ROA
2407:c280:80ee::/48RADBNo ROA
2607:740:41::/48ARIN, RADBValid
2607:6b80:5f::/48RADBNo ROA
2607:6b80:60::/48RADBValid
2607:6b80:61::/48RADBNo ROA
2607:6b80:62::/48RADBNo ROA
2a0e:1cc0:2::/48RIPEValid

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.