Network · data from 2026-11-12
AS54809 MCMSYS - MCM Systems, LLC
Registry name: MCMSYS - MCM Systems, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS54809, 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.
| 162.244.216.0/22 | No ROA | Other IRR onlyRADB | 670 100% |
| 206.166.199.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 207.140.115.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
AS-SET
AS54809 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 11 are in fix.csv.
- ROA: none3
- Route object: RIR3
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 162.244.216.0/22 | No ROA covers it. Add a ROA for AS54809, maxLength 22. |
| Route object: RIR | 162.244.216.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.166.199.0/24 | No ROA covers it. Add a ROA for AS54809, maxLength 24. |
| Route object: RIR | 206.166.199.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 207.140.115.0/24 | No ROA covers it. Add a ROA for AS54809, maxLength 24. |
| Route object: RIR | 207.140.115.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS54809 whose prefix no peer sees AS54809 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 12.14.209.0/24 | RADB | No ROA |
| 12.22.188.0/22 | RADB | No ROA |
| 12.105.156.0/22 | RADB | No ROA |
| 207.243.167.0/24 | RADB | No ROA |
| 209.64.119.0/24 | 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.