Network · data from 2026-11-12
AS24322 infininet (prev. HostLink)
Registry name: INFININET-AS-AP - Infininet Global Pty Ltd, AU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24322, 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.248.51.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 2401:2060:2000::/48 | No ROA | RIR databaseAPNIC | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS24322: AS-INFININET-AU. 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 (AS24322 isn't in the set, or no route object for AS24322 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 | AS24322 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-INFININET-AU | In no IRR database read today. | |||||
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 35 are in fix.csv.
- ROA: none2
- AS-SET: not found1
- Route object: not announced32
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.248.51.0/24 | No ROA covers it. Add a ROA for AS24322, maxLength 24. |
| ROA: none | 2401:2060:2000::/48 | No ROA covers it. Add a ROA for AS24322, maxLength 48. |
| AS-SET: not found | AS-INFININET-AU | PeeringDB names AS-INFININET-AU; no IRR database read has it. |
Route objects not announced
Route objects with origin AS24322 whose prefix no peer sees AS24322 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 82.115.0.0/22 | NTTCOM | No ROA |
| 103.76.164.0/23 | RADB | No ROA |
| 103.77.68.0/23 | RADB | No ROA |
| 103.77.68.0/24 | RADB | No ROA |
| 103.77.69.0/24 | RADB | No ROA |
| 116.206.128.0/23 | RADB | No ROA |
| 2001:df5:8600::/48 | RADB | No ROA |
| 2401:2060:2fff::/48 | APNIC | No ROA |
| 2407:c280::/32 | NTTCOM, RADB | No ROA |
| 2407:c280:999::/48 | RADB | No ROA |
| 2407:c280:3000::/45 | RADB | No ROA |
| 2407:c280:3000::/46 | RADB | No ROA |
| 2407:c280:3000::/47 | RADB | No ROA |
| 2407:c280:3000::/48 | RADB | No ROA |
| 2407:c280:3001::/48 | RADB | No ROA |
| 2407:c280:3002::/47 | RADB | No ROA |
| 2407:c280:3002::/48 | RADB | No ROA |
| 2407:c280:3003::/48 | RADB | No ROA |
| 2407:c280:3004::/46 | RADB | No ROA |
| 2407:c280:3004::/47 | RADB | No ROA |
| 2407:c280:3004::/48 | RADB | No ROA |
| 2407:c280:3005::/48 | RADB | No ROA |
| 2407:c280:30ff::/48 | RADB | No ROA |
| 2407:c280:7101::/48 | RADB | No ROA |
| 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 |
| 2407:c280:ffff::/48 | RADB | No ROA |
| 2a0e:b107:310::/44 | NTTCOM | No 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.