Network · data from 2026-11-12
AS62821 MNX.io
Registry name: AS-MNX - MNX Solutions LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS62821, 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.
| 8.36.12.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 8.225.232.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 67.158.54.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 140.235.240.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
| 142.147.2.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 192.207.255.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 198.62.109.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 204.8.232.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 4.39.99.0/24 | No ROA | Other IRR onlyRADB | 658 98% |
AS-SET
PeeringDB's irr_as_set for AS62821: AS-MNX. 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 (AS62821 isn't in the set, or no route object for AS62821 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 | AS62821 in it | Not covered |
|---|---|---|---|---|---|
| AS-MNX | RIPE | 1 | 1 | No | 9 |
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 20 are in fix.csv.
- ROA: none9
- Route object: RIR9
- AS-SET: own ASN1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 8.36.12.0/24 | No ROA covers it. Add a ROA for AS62821, maxLength 24. |
| Route object: RIR | 8.36.12.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 8.225.232.0/24 | No ROA covers it. Add a ROA for AS62821, maxLength 24. |
| Route object: RIR | 8.225.232.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 67.158.54.0/24 | No ROA covers it. Add a ROA for AS62821, maxLength 24. |
| Route object: RIR | 67.158.54.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 140.235.240.0/22 | No ROA covers it. Add a ROA for AS62821, maxLength 22. |
| Route object: RIR | 140.235.240.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 142.147.2.0/24 | No ROA covers it. Add a ROA for AS62821, maxLength 24. |
| Route object: RIR | 142.147.2.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.207.255.0/24 | No ROA covers it. Add a ROA for AS62821, maxLength 24. |
| Route object: RIR | 192.207.255.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 198.62.109.0/24 | No ROA covers it. Add a ROA for AS62821, maxLength 24. |
| Route object: RIR | 198.62.109.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 204.8.232.0/24 | No ROA covers it. Add a ROA for AS62821, maxLength 24. |
| Route object: RIR | 204.8.232.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 4.39.99.0/24 | No ROA covers it. Add a ROA for AS62821, maxLength 24. |
| Route object: RIR | 4.39.99.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS-MNX | AS62821 isn't in AS-MNX (RIPE) once expanded. Add AS62821 to it. |
Route objects not announced
Route objects with origin AS62821 whose prefix no peer sees AS62821 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2620:53:c000::/48 | RADB | 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.