bgpreport

Network · data from 2026-11-12

AS270126 Neutral Networks_MX

Registry name: AS270126 - NEUTRAL NETWORKS, S de RL de CV, MX · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270126, 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.58.144.0/23 No ROA Other IRR onlyRADB 673 100% 67
38.58.146.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.58.147.0/24 No ROA Other IRR onlyRADB 672 100% 67
2806:3cf:1::/48 Valid Nonecovered by 2806:3cf::/32 635 100% 67
2806:3cf:8000::/48 Valid Nonecovered by 2806:3cf::/32 635 100% 67
2806:3cf:8001::/48 Valid Nonecovered by 2806:3cf::/32 635 100% 67
190.171.68.0/24 Valid Other IRR onlyRADB 672 100% 67
190.171.69.0/24 Valid Other IRR onlyRADB 672 100% 67
190.171.70.0/24 Valid Other IRR onlyRADB 672 100% 67
190.171.71.0/24 Valid Other IRR onlyRADB 672 100% 67
190.171.68.0/22 Valid RIR databaseLACNIC 672 100% 67
2806:3cf::/32 Valid RIR databaseLACNIC, RADB 635 100% 67
2806:402:4000::/48 Valid RIR databaseLACNIC, RADB 634 100% 67

AS-SET

AS270126'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 15 are in fix.csv.

  • ROA: none3
  • Route object: none3
  • Route object: RIR7
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none38.58.144.0/23No ROA covers it. Add a ROA for AS270126, maxLength 23.673 of 673
Route object: RIR38.58.144.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.58.146.0/24No ROA covers it. Add a ROA for AS270126, maxLength 24.672 of 673
Route object: RIR38.58.146.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.58.147.0/24No ROA covers it. Add a ROA for AS270126, maxLength 24.672 of 673
Route object: RIR38.58.147.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none2806:3cf:1::/48No route object for it. A route object for 2806:3cf::/32 with origin AS270126 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270126 in the RIR database for the space.635 of 636
Route object: none2806:3cf:8000::/48No route object for it. A route object for 2806:3cf::/32 with origin AS270126 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270126 in the RIR database for the space.635 of 636
Route object: none2806:3cf:8001::/48No route object for it. A route object for 2806:3cf::/32 with origin AS270126 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270126 in the RIR database for the space.635 of 636
Route object: RIR190.171.68.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR190.171.69.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR190.171.70.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR190.171.71.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

38.58.144.0/24RADBNo ROA
38.58.145.0/24RADBNo 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.