bgpreport

Network · data from 2026-11-12

AS28394 Bicentel SA de CV (C3ntro Telecom)

Registry name: AS28394 - Bicentel SA de CV, MX · PeeringDB

24IPv4 routes 83.3% RPKI valid · 100.0% with a route object
5IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS28394, seen from no peer

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% 66
38.147.148.0/22 No ROA Other IRR onlyRADB 672 100% 66
187.102.224.0/22 No ROA Other IRR onlyRADB 672 100% 66
38.77.71.0/24 No ROA Other IRR onlyRADB 671 100% 66
45.168.232.0/24 Valid Other IRR onlyRADB 672 100% 66
45.168.234.0/24 Valid Other IRR onlyRADB 672 100% 66
138.255.60.0/24 Valid Other IRR onlyNTTCOM 672 100% 66
138.255.61.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 66
138.255.62.0/24 Valid Other IRR onlyNTTCOM 672 100% 66
170.245.189.0/24 Valid Other IRR onlyRADB 672 100% 66
170.245.190.0/24 Valid Other IRR onlyRADB 672 100% 66
187.62.120.0/24 Valid Other IRR onlyRADB 672 100% 66
187.62.123.0/24 Valid Other IRR onlyRADB 672 100% 66
45.235.174.0/24 Valid Other IRR onlyRADB 671 100% 66
200.0.90.0/24 Valid Other IRR onlyRADB 671 100% 66
200.0.92.0/24 Valid Other IRR onlyNTTCOM 671 100% 67
200.0.93.0/24 Valid Other IRR onlyNTTCOM 671 100% 67
2806:217:201::/48 Valid Other IRR onlyRADB 636 100% 68
2806:217:301::/48 Valid Other IRR onlyRADB 636 100% 68
2806:217:401::/48 Valid Other IRR onlyRADB 636 100% 68
2806:217:601::/48 Valid Other IRR onlyRADB 636 100% 68
45.168.232.0/22 Valid RIR databaseLACNIC, RADB 672 100% 66
45.235.172.0/22 Valid RIR databaseLACNIC, RADB 672 100% 66
138.255.60.0/22 Valid RIR databaseLACNIC, RADB 672 100% 66
170.245.188.0/22 Valid RIR databaseLACNIC, RADB 672 100% 66
187.62.120.0/22 Valid RIR databaseLACNIC, RADB 672 100% 66
200.0.90.0/23 Valid RIR databaseLACNIC, RADB 671 100% 66
200.0.92.0/23 Valid RIR databaseLACNIC 671 100% 66
2806:217::/32 Valid RIR databaseLACNIC, RADB 636 100% 67

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
ChangePrefix or setDetailFull-table peers
ROA: none38.77.68.0/22No ROA covers it. Add a ROA for AS28394, maxLength 22.672 of 673
Route object: RIR38.77.68.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.147.148.0/22No ROA covers it. Add a ROA for AS28394, maxLength 22.672 of 673
Route object: RIR38.147.148.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none187.102.224.0/22No ROA covers it. Add a ROA for AS28394, maxLength 22.672 of 673
Route object: RIR187.102.224.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.77.71.0/24No ROA covers it. Add a ROA for AS28394, maxLength 24.671 of 673
Route object: RIR38.77.71.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.168.232.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.168.234.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR138.255.60.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR138.255.61.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR138.255.62.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR170.245.189.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR170.245.190.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.62.120.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.62.123.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.235.174.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.0.90.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.0.92.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR200.0.93.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR2806:217:201::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2806:217:301::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2806:217:401::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2806:217:601::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

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/24NTTCOMValid
170.245.188.0/24RADBValid
170.245.191.0/24RADBValid
187.102.224.0/23LACNICValid
187.102.226.0/24RADBNo ROA
200.0.1.0/24RADBNo ROA
200.0.91.0/24NTTCOM, RADBValid
200.38.99.0/24RADBNo ROA
200.38.100.0/24RADBNo ROA
200.38.121.0/24RADBNo ROA
2604:980:e000::/48RADBNo ROA
2806:31a::/32LACNICValid
2806:3a1::/32LACNIC, RADBValid
2806:3b6::/32LACNIC, RADBValid

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.