Network · data from 2026-11-12
AS133192 Ultimate Mobile
Registry name: UBB-AS-AP - Ultimate Mobile limited, NZ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS133192, 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.255.24.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.255.25.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.255.26.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.255.27.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 163.47.164.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 163.47.165.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 163.47.166.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 163.47.167.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
AS-SET
AS133192's PeeringDB record names no AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS133192 is announced.
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.