bgpreport

Network · data from 2026-11-12

AS270200 AS270200 - MEGABIT TELECOMUNICACIONES SA DE CV

Registry name: AS270200 - MEGABIT TELECOMUNICACIONES SA DE CV, MX · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270200, 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.

190.9.108.0/24 No ROA Nonecovered by 190.9.108.0/22 671 100% 67
190.9.109.0/24 No ROA Nonecovered by 190.9.108.0/22 671 100% 67
190.9.110.0/24 No ROA Nonecovered by 190.9.108.0/22 671 100% 67
190.9.111.0/24 No ROA Nonecovered by 190.9.108.0/22 671 100% 67
2806:3f7:3000::/36 No ROA Other IRR onlyRADB 635 100% 67
2806:3f7:4000::/36 No ROA Other IRR onlyRADB 635 100% 67
2806:3f7:5000::/36 No ROA Other IRR onlyRADB 635 100% 67
2806:3f7:6000::/36 No ROA Other IRR onlyRADB 635 100% 67
2806:3f7:c000::/36 No ROA Other IRR onlyRADB 635 100% 68
2806:3f7:d000::/36 No ROA Other IRR onlyRADB 635 100% 68

AS-SET

AS270200 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 48 are in fix.csv.

  • ROA: none10
  • Route object: none4
  • Route object: RIR6
  • Route object: not announced28
ChangePrefix or setDetailFull-table peers
ROA: none190.9.108.0/24No ROA covers it. Add a ROA for AS270200, maxLength 24.671 of 673
Route object: none190.9.108.0/24No route object for it. A route object for 190.9.108.0/22 with origin AS270200 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270200 in the RIR database for the space.671 of 673
ROA: none190.9.109.0/24No ROA covers it. Add a ROA for AS270200, maxLength 24.671 of 673
Route object: none190.9.109.0/24No route object for it. A route object for 190.9.108.0/22 with origin AS270200 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270200 in the RIR database for the space.671 of 673
ROA: none190.9.110.0/24No ROA covers it. Add a ROA for AS270200, maxLength 24.671 of 673
Route object: none190.9.110.0/24No route object for it. A route object for 190.9.108.0/22 with origin AS270200 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270200 in the RIR database for the space.671 of 673
ROA: none190.9.111.0/24No ROA covers it. Add a ROA for AS270200, maxLength 24.671 of 673
Route object: none190.9.111.0/24No route object for it. A route object for 190.9.108.0/22 with origin AS270200 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270200 in the RIR database for the space.671 of 673
ROA: none2806:3f7:3000::/36No ROA covers it. Add a ROA for AS270200, maxLength 36.635 of 636
Route object: RIR2806:3f7:3000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2806:3f7:4000::/36No ROA covers it. Add a ROA for AS270200, maxLength 36.635 of 636
Route object: RIR2806:3f7:4000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2806:3f7:5000::/36No ROA covers it. Add a ROA for AS270200, maxLength 36.635 of 636
Route object: RIR2806:3f7:5000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2806:3f7:6000::/36No ROA covers it. Add a ROA for AS270200, maxLength 36.635 of 636
Route object: RIR2806:3f7:6000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2806:3f7:c000::/36No ROA covers it. Add a ROA for AS270200, maxLength 36.635 of 636
Route object: RIR2806:3f7:c000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2806:3f7:d000::/36No ROA covers it. Add a ROA for AS270200, maxLength 36.635 of 636
Route object: RIR2806:3f7:d000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Route objects with origin AS270200 whose prefix no peer sees AS270200 announce. Many are kept on purpose (backup routes, space announced only in some places).

190.9.108.0/22RADBNo ROA
200.32.75.0/24RADBNo ROA
2806:3f7::/32RADBNo ROA
2806:3f7::/33RADBNo ROA
2806:3f7::/34RADBNo ROA
2806:3f7::/35RADBNo ROA
2806:3f7::/36RADBNo ROA
2806:3f7::/37RADBNo ROA
2806:3f7::/38RADBNo ROA
2806:3f7::/39RADBNo ROA
2806:3f7::/40RADBNo ROA
2806:3f7::/41RADBNo ROA
2806:3f7::/42RADBNo ROA
2806:3f7::/43RADBNo ROA
2806:3f7::/44RADBNo ROA
2806:3f7::/45RADBNo ROA
2806:3f7::/46RADBNo ROA
2806:3f7::/47RADBNo ROA
2806:3f7::/48RADBNo ROA
2806:3f7:1000::/36RADBNo ROA
2806:3f7:2000::/36RADBNo ROA
2806:3f7:7000::/36RADBNo ROA
2806:3f7:8000::/36RADBNo ROA
2806:3f7:9000::/36RADBNo ROA
2806:3f7:a000::/36RADBNo ROA
2806:3f7:b000::/36RADBNo ROA
2806:3f7:e000::/36RADBNo ROA
2806:3f7:f000::/36RADBNo 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.