Network · data from 2026-11-12
AS28394 Bicentel SA de CV (C3ntro Telecom)
Registry name: AS28394 - Bicentel SA de CV, MX · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS28394, 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.77.68.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 38.147.148.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 187.102.224.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 38.77.71.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 45.168.232.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 45.168.234.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 138.255.60.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 138.255.61.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 138.255.62.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 170.245.189.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 170.245.190.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 187.62.120.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 187.62.123.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 45.235.174.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 200.0.90.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 200.0.92.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
| 200.0.93.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
| 2806:217:201::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 2806:217:301::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 2806:217:401::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 2806:217:601::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 45.168.232.0/22 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 45.235.172.0/22 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 138.255.60.0/22 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 170.245.188.0/22 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 187.62.120.0/22 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 200.0.90.0/23 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 200.0.92.0/23 | Valid | RIR databaseLACNIC | 671 100% |
| 2806:217::/32 | Valid | RIR databaseLACNIC, RADB | 636 100% |
AS-SET
AS28394's PeeringDB record names no 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 39 are in fix.csv.
- ROA: none4
- Route object: RIR21
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.77.68.0/22 | No ROA covers it. Add a ROA for AS28394, maxLength 22. |
| Route object: RIR | 38.77.68.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.147.148.0/22 | No ROA covers it. Add a ROA for AS28394, maxLength 22. |
| Route object: RIR | 38.147.148.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 187.102.224.0/22 | No ROA covers it. Add a ROA for AS28394, maxLength 22. |
| Route object: RIR | 187.102.224.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.77.71.0/24 | No ROA covers it. Add a ROA for AS28394, maxLength 24. |
| Route object: RIR | 38.77.71.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.168.232.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.168.234.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.255.60.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 138.255.61.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.255.62.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 170.245.189.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.245.190.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 187.62.120.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 187.62.123.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.235.174.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.0.90.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.0.92.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 200.0.93.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 2806:217:201::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2806:217:301::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2806:217:401::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2806:217:601::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS28394 whose prefix no peer sees AS28394 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 138.255.63.0/24 | NTTCOM | Valid |
| 170.245.188.0/24 | RADB | Valid |
| 170.245.191.0/24 | RADB | Valid |
| 187.102.224.0/23 | LACNIC | Valid |
| 187.102.226.0/24 | RADB | No ROA |
| 200.0.1.0/24 | RADB | No ROA |
| 200.0.91.0/24 | NTTCOM, RADB | Valid |
| 200.38.99.0/24 | RADB | No ROA |
| 200.38.100.0/24 | RADB | No ROA |
| 200.38.121.0/24 | RADB | No ROA |
| 2604:980:e000::/48 | RADB | No ROA |
| 2806:31a::/32 | LACNIC | Valid |
| 2806:3a1::/32 | LACNIC, RADB | Valid |
| 2806:3b6::/32 | LACNIC, RADB | 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.