Network · data from 2026-11-12
AS394475 MCECFIBER-A01 - MCEC Fiber, Inc.
Registry name: MCECFIBER-A01 - MCEC Fiber, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS394475, 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.35.176.0/21 | No ROA | RIR databaseARIN | 671 100% |
| 216.185.200.0/24 | Valid | Nonecovered by 216.185.192.0/20 | 673 100% |
| 204.246.32.0/22 | Valid | Other IRR onlyRADB | 671 100% |
| 204.246.36.0/22 | Valid | Other IRR onlyRADB | 671 100% |
| 204.246.32.0/24 | Valid | RIR databaseARIN | 671 100% |
| 204.246.33.0/24 | Valid | RIR databaseARIN | 671 100% |
| 204.246.34.0/24 | Valid | RIR databaseARIN | 671 100% |
| 204.246.35.0/24 | Valid | RIR databaseARIN | 671 100% |
| 204.246.36.0/24 | Valid | RIR databaseARIN | 671 100% |
| 204.246.37.0/24 | Valid | RIR databaseARIN | 671 100% |
| 204.246.38.0/24 | Valid | RIR databaseARIN | 671 100% |
| 204.246.39.0/24 | Valid | RIR databaseARIN | 671 100% |
| 209.35.176.0/24 | Valid | RIR databaseARIN | 671 100% |
| 209.35.177.0/24 | Valid | RIR databaseARIN | 671 100% |
| 209.35.179.0/24 | Valid | RIR databaseARIN | 671 100% |
| 209.35.180.0/24 | Valid | RIR databaseARIN | 671 100% |
| 209.35.183.0/24 | Valid | RIR databaseARIN | 671 100% |
| 216.185.192.0/20 | Valid | RIR databaseARIN | 671 100% |
| 216.185.193.0/24 | Valid | RIR databaseARIN | 671 100% |
| 216.185.194.0/24 | Valid | RIR databaseARIN | 671 100% |
| 216.185.195.0/24 | Valid | RIR databaseARIN | 671 100% |
| 216.185.196.0/24 | Valid | RIR databaseARIN | 671 100% |
| 216.185.197.0/24 | Valid | RIR databaseARIN | 671 100% |
| 216.185.198.0/24 | Valid | RIR databaseARIN | 671 100% |
| 216.185.199.0/24 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS394475 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 6 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 209.35.176.0/21 | No ROA covers it. Add a ROA for AS394475, maxLength 21. |
| Route object: none | 216.185.200.0/24 | No route object for it. A route object for 216.185.192.0/20 with origin AS394475 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394475 in the RIR database for the space. |
| Route object: RIR | 204.246.32.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 204.246.36.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS394475 whose prefix no peer sees AS394475 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 204.246.32.0/21 | ARIN | Valid |
| 2605:bf40::/32 | ARIN | 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.