Network · data from 2026-11-12
AS18885 M2NGAGE2 - M2ngage Telecommunications II Corp.
Registry name: M2NGAGE2 - M2ngage Telecommunications II Corp., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18885, 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.
| 209.178.206.0/24 | No ROA | None | 3 0%low visibility |
| 160.79.0.0/21 | No ROA | None | 2 0%low visibility |
| 160.79.8.0/22 | No ROA | None | 2 0%low visibility |
| 160.79.10.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 160.79.2.0/24 | Valid | RIR databaseARIN | 670 100% |
| 160.79.4.0/22 | Valid | RIR databaseARIN | 670 100% |
| 160.79.7.0/24 | Valid | RIR databaseARIN | 670 100% |
| 160.79.8.0/24 | Valid | RIR databaseARIN | 670 100% |
| 160.79.11.0/24 | Valid | RIR databaseARIN | 670 100% |
| 160.79.126.0/24 | Valid | RIR databaseARIN | 670 100% |
| 209.178.207.0/24 | Valid | RIR databaseARIN | 670 100% |
| 209.178.224.0/21 | Valid | RIR databaseARIN | 670 100% |
AS-SET
AS18885 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 9 are in fix.csv.
- ROA: none4
- Route object: none3
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 209.178.206.0/24 | No ROA covers it. Add a ROA for AS18885, maxLength 24. |
| Route object: none | 209.178.206.0/24 | No route object for it. Add a route object with origin AS18885 in the RIR database for the space. |
| ROA: none | 160.79.0.0/21 | No ROA covers it. Add a ROA for AS18885, maxLength 21. |
| Route object: none | 160.79.0.0/21 | No route object for it. Add a route object with origin AS18885 in the RIR database for the space. |
| ROA: none | 160.79.8.0/22 | No ROA covers it. Add a ROA for AS18885, maxLength 22. |
| Route object: none | 160.79.8.0/22 | No route object for it. Add a route object with origin AS18885 in the RIR database for the space. |
| ROA: none | 160.79.10.0/24 | No ROA covers it. Add a ROA for AS18885, maxLength 24. |
| Route object: RIR | 160.79.10.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18885 whose prefix no peer sees AS18885 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:470:29d::/48 | ARIN | Invalid: origin |
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.