Network · data from 2026-11-12
AS138637 VOCPHONE
Registry name: VOCPHONE-AS-AP - VOCPHONE PTY LTD, AU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS138637, 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.
| 2404:77c0::/32 | Valid | Other IRR onlyRADB | 635 100% |
| 103.135.87.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.135.84.0/22 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.135.84.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.135.85.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.135.86.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.248.188.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 180.94.238.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 180.94.239.0/24 | Valid | RIR databaseAPNIC | 672 100% |
AS-SET
AS138637's PeeringDB record names no 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 4 are in fix.csv.
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 2404:77c0::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS138637 whose prefix no peer sees AS138637 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.135.84.0/23 | APNIC | Valid |
| 103.135.86.0/23 | APNIC | Valid |
| 180.94.238.0/23 | APNIC | 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.