bgpreport

Network · data from 2026-11-12

AS270176 wifimax connection

Registry name: AS270176 - WIFIMAX CONNECTION S.A.S DE C.V, MX · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
8IPv6 routes 37.5% RPKI valid · 12.5% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No ROA 7 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS270176, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS270176, 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.
2806:3f0::/40 No ROA Nonecovered by 2806:3f0::/32 634 100% 67
2806:3f0:100::/40 No ROA Nonecovered by 2806:3f0::/32 634 100% 67
2806:3f0:200::/40 No ROA Nonecovered by 2806:3f0::/32 634 100% 67
2806:3f0:2000::/40 No ROA Nonecovered by 2806:3f0::/32 634 100% 67
2806:3f0:3000::/40 No ROA Nonecovered by 2806:3f0::/32 634 100% 67
2806:3f0:1000::/48 Valid Nonecovered by 2806:3f0:1000::/40 2 0%low visibility 2
2806:3f0:1001::/48 Valid Nonecovered by 2806:3f0:1000::/40 2 0%low visibility 2
192.81.249.0/24 Valid Other IRR onlyRADB 673 100% 66
192.81.250.0/24 Valid Other IRR onlyRADB 673 100% 66
89.213.106.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
148.224.32.0/24 Valid RIR databaseLACNIC 673 100% 66
148.224.33.0/24 Valid RIR databaseLACNIC 673 100% 66
148.224.35.0/24 Valid RIR databaseLACNIC 673 100% 66
168.121.242.0/24 Valid RIR databaseLACNIC, RADB 673 100% 66
2806:3f0:1000::/40 Valid RIR databaseLACNIC 633 100% 67

AS-SET

AS270176'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 16 are in fix.csv.

  • ROA: none5
  • Route object: none7
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2806:3f0::/40No ROA covers it. Add a ROA for AS270176, maxLength 40.634 of 636
Route object: none2806:3f0::/40No route object for it. A route object for 2806:3f0::/32 with origin AS270176 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270176 in the RIR database for the space.634 of 636
ROA: none2806:3f0:100::/40No ROA covers it. Add a ROA for AS270176, maxLength 40.634 of 636
Route object: none2806:3f0:100::/40No route object for it. A route object for 2806:3f0::/32 with origin AS270176 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270176 in the RIR database for the space.634 of 636
ROA: none2806:3f0:200::/40No ROA covers it. Add a ROA for AS270176, maxLength 40.634 of 636
Route object: none2806:3f0:200::/40No route object for it. A route object for 2806:3f0::/32 with origin AS270176 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270176 in the RIR database for the space.634 of 636
ROA: none2806:3f0:2000::/40No ROA covers it. Add a ROA for AS270176, maxLength 40.634 of 636
Route object: none2806:3f0:2000::/40No route object for it. A route object for 2806:3f0::/32 with origin AS270176 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270176 in the RIR database for the space.634 of 636
ROA: none2806:3f0:3000::/40No ROA covers it. Add a ROA for AS270176, maxLength 40.634 of 636
Route object: none2806:3f0:3000::/40No route object for it. A route object for 2806:3f0::/32 with origin AS270176 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270176 in the RIR database for the space.634 of 636
Route object: none2806:3f0:1000::/48No route object for it. A route object for 2806:3f0:1000::/40 with origin AS270176 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270176 in the RIR database for the space.2 of 636
Route object: none2806:3f0:1001::/48No route object for it. A route object for 2806:3f0:1000::/40 with origin AS270176 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270176 in the RIR database for the space.2 of 636
Route object: RIR192.81.249.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR192.81.250.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

148.224.34.0/24LACNICValid
2806:3f0::/32RADBNo 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.