Network · data from 2026-11-12
AS149485 MonoCloud
Registry name: MONOCLOUDPTYLTD-AS-AP - MonoCloud Pty Ltd, AU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS149485, 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.
| 38.83.62.0/24 | Valid | Nonecovered by 38.83.62.0/23 | 668 99% |
| 45.138.210.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 45.138.211.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 103.230.68.0/24 | Valid | RIR databaseAPNIC, RADB | 668 99% |
| 2400:56a0:100::/40 | Valid | RIR databaseAPNIC | 636 100% |
| 2400:56a0:800::/40 | Valid | RIR databaseAPNIC | 636 100% |
| 2400:56a0:dc01::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2400:56a0:300::/40 | Valid | RIR databaseAPNIC | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS149485: AS149485:AS-MONONET. 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 (AS149485 isn't in the set, or no route object for AS149485 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 | AS149485 in it | Not covered |
|---|---|---|---|---|---|
| AS149485:AS-MONONET | APNIC | 0 | 2 | No | 8 |
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 9 are in fix.csv.
- Route object: none1
- AS-SET: own ASN1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 38.83.62.0/24 | No route object for it. A route object for 38.83.62.0/23 with origin AS149485 covers it (filters allowing more-specifics accept it). Add a route object with origin AS149485 in the RIR database for the space. |
| AS-SET: own ASN | AS149485:AS-MONONET | AS149485 isn't in AS149485:AS-MONONET (APNIC) once expanded. Add AS149485 to it. |
Route objects not announced
Route objects with origin AS149485 whose prefix no peer sees AS149485 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.83.62.0/23 | ARIN | Valid |
| 45.138.210.0/23 | RIPE | Invalid: origin |
| 103.181.0.0/23 | APNIC | Valid |
| 103.181.0.0/24 | APNIC | Valid |
| 103.181.1.0/24 | APNIC | Valid |
| 160.250.12.0/24 | APNIC | Valid |
| 2400:56a0:200::/40 | 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.