Network · data from 2026-11-12
AS57025 MoNetworks MonoCloud Pty Ltd
Registry name: MoNetworks MonoCloud Pty Ltd, AU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS57025, 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.
| 45.8.204.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 103.181.1.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 160.250.13.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 2400:56a0:200::/40 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:56a0:900::/40 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:56a0:dc02::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2a13:db01:1000::/36 | Valid | RIR databaseRIPE | 632 99% |
AS-SET
AS57025 isn't in PeeringDB, where networks name their 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 2 are in fix.csv.
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 45.8.204.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS57025 whose prefix no peer sees AS57025 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a13:db00::/30 | 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.