Skip to main content

AS270126

270126

Autonomous System AS270126 from MX-NENE-LACNIC

Registry

Authoritative registration data

AS number
270126
Name
270126
Organisation
Autonomous System AS270126 from MX-NENE-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

5

Total announced

13

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS270126
190.171.68.0/22 IPv4 /22 not checked
38.58.144.0/23 IPv4 /23 not checked
190.171.68.0/24 IPv4 /24 not checked
190.171.69.0/24 IPv4 /24 not checked
190.171.70.0/24 IPv4 /24 not checked
190.171.71.0/24 IPv4 /24 not checked
38.58.146.0/24 IPv4 /24 not checked
38.58.147.0/24 IPv4 /24 not checked
2806:3cf::/32 IPv6 /32 not checked
2806:3cf:1::/48 IPv6 /48 not checked
2806:3cf:8000::/48 IPv6 /48 RPKI valid
2806:3cf:8001::/48 IPv6 /48 RPKI valid
2806:402:4000::/48 IPv6 /48 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS270126
Address families
NIX Monterrey 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS270126 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS270126 in AS paths

Observed upstreams
Families
AS1299 TWELVE99 1,354 4,897
v4 v6
AS174 COGENT-174 1,041 3,111
v4 v6

No rows match “”.

Showing – of

Observed downstreams

7 networks seen after AS270126 in AS paths

Observed downstreams
Families
AS28409 28409 502 1,285
v4
AS265574 265574 330 720
v4 v6
AS270215 270215 480 680
v4 v6
AS270156 270156 246 658
v4
AS28428 28428 239 315
v4 v6
AS265518 265518 16 40
v4
AS40345 IP-COM 25 33
v4

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual.