Network · data from 2026-11-12
AS133480 Intergrid
Registry name: INT-5GN-AS-AP - 5G NETWORK OPERATIONS PTY LTD, AU · PeeringDB
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% |
| 202.50.84.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 2607:6b80:5e::/48 | No ROA | Other IRR onlyRADB | 635 100% |
| 103.137.119.0/24 | No ROA | RIR databaseAPNIC, RADB | 671 100% |
| 103.140.134.0/24 | No ROA | RIR databaseAPNIC, RADB | 671 100% |
| 45.125.125.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.194.4.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 43.245.160.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 43.245.161.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 43.245.162.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 43.245.163.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.76.164.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.76.165.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.77.232.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 103.77.233.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 103.77.234.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.77.235.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.108.92.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.108.93.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.108.94.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.108.95.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.192.173.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.231.88.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 103.231.89.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 103.231.90.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 103.231.91.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 116.206.228.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 116.206.229.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 116.206.230.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 116.206.231.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 203.18.16.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.18.17.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.209.209.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.209.212.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.209.217.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.209.219.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 2407:a080::/48 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2407:a080:7000::/36 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2400:fa80:1::/48 | Valid | RIR databaseAPNIC, NTTCOM | 634 100% |
| 2400:fa80:4::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:fa80:5::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:fa80:6::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2407:a080::/32 | Valid | RIR databaseAPNIC, NTTCOM | 634 100% |
| 2407:a080:2000::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2407:a080:5000::/36 | Valid | RIR databaseAPNIC | 634 100% |
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.
| Name | Database | ASNs | Sets | AS133480 in it | Not covered |
|---|---|---|---|---|---|
| AS-INTERGRID | APNIC | 4 | 2 | 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
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.137.56.0/24 | No ROA covers it. Add a ROA for AS133480, maxLength 24. |
| Route object: RIR | 103.137.56.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 202.50.84.0/24 | No ROA covers it. Add a ROA for AS133480, maxLength 24. |
| Route object: RIR | 202.50.84.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2607:6b80:5e::/48 | No ROA covers it. Add a ROA for AS133480, maxLength 48. |
| Route object: RIR | 2607:6b80:5e::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.137.119.0/24 | No ROA covers it. Add a ROA for AS133480, maxLength 24. |
| ROA: none | 103.140.134.0/24 | No ROA covers it. Add a ROA for AS133480, maxLength 24. |
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/24 | RADB | No ROA |
| 43.245.160.0/23 | APNIC, RADB | No ROA |
| 43.245.162.0/23 | APNIC, RADB | No ROA |
| 45.54.84.0/23 | RADB | No ROA |
| 103.77.232.0/22 | NTTCOM | No ROA |
| 103.77.232.0/23 | APNIC, RADB | No ROA |
| 103.77.234.0/23 | APNIC, RADB | No ROA |
| 103.108.92.0/22 | APNIC, RADB | Valid |
| 103.108.92.0/23 | APNIC | Valid |
| 103.108.94.0/23 | APNIC | Valid |
| 103.191.36.0/23 | RADB | No ROA |
| 103.231.88.0/22 | NTTCOM, RADB | No ROA |
| 103.231.88.0/23 | NTTCOM | No ROA |
| 103.231.90.0/23 | NTTCOM | No ROA |
| 116.206.228.0/22 | RADB | No ROA |
| 116.206.228.0/23 | RADB | No ROA |
| 116.206.230.0/23 | RADB | No ROA |
| 168.1.133.0/24 | RADB | No ROA |
| 185.190.83.0/24 | RADB | Valid |
| 193.180.80.0/24 | RADB | No ROA |
| 194.110.172.0/23 | RADB | No ROA |
| 202.47.81.0/24 | RADB | No ROA |
| 203.17.122.0/24 | APNIC | Valid |
| 2400:fa80::/32 | APNIC, NTTCOM | No ROA |
| 2400:fa80:3::/48 | APNIC | Valid |
| 2402:1b80:3002::/48 | APNIC | Valid |
| 2407:a080:2000::/36 | APNIC | Invalid: maxLength |
| 2407:a080:3000::/36 | APNIC | Invalid: maxLength |
| 2407:a080:4000::/36 | APNIC | Invalid: maxLength |
| 2407:c280:8005::/48 | RADB | No ROA |
| 2407:c280:8006::/48 | RADB | No ROA |
| 2407:c280:8007::/48 | RADB | No ROA |
| 2407:c280:8008::/48 | RADB | No ROA |
| 2407:c280:8009::/48 | RADB | No ROA |
| 2407:c280:80ee::/48 | RADB | No ROA |
| 2607:740:41::/48 | ARIN, RADB | Valid |
| 2607:6b80:5f::/48 | RADB | No ROA |
| 2607:6b80:60::/48 | RADB | Valid |
| 2607:6b80:61::/48 | RADB | No ROA |
| 2607:6b80:62::/48 | RADB | No ROA |
| 2a0e:1cc0:2::/48 | RIPE | Valid |
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.