Skip to main content

AS270172

270172

Autonomous System AS270172 from MX-GURO-LACNIC

Registry

Authoritative registration data

AS number
270172
Name
270172
Organisation
Autonomous System AS270172 from MX-GURO-LACNIC
Country
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

8

Total announced

19

Announced prefixes

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

Prefixes announced by AS270172
104.234.241.0/24 IPv4 /24 not checked
148.224.46.0/24 IPv4 /24 not checked
148.224.58.0/24 IPv4 /24 not checked
148.224.59.0/24 IPv4 /24 not checked
38.94.72.0/24 IPv4 /24 not checked
38.94.73.0/24 IPv4 /24 not checked
38.94.75.0/24 IPv4 /24 not checked
5.102.108.0/24 IPv4 /24 not checked
5.102.109.0/24 IPv4 /24 not checked
5.102.110.0/24 IPv4 /24 not checked
5.102.111.0/24 IPv4 /24 not checked
2001:1203:1000::/36 IPv6 /36 not checked
2001:1203::/36 IPv6 /36 not checked
2001:1203:a000::/36 IPv6 /36 not checked
2001:1203:a300::/40 IPv6 /40 not checked
2001:1203:a400::/40 IPv6 /40 not checked
2001:1203:a500::/40 IPv6 /40 not checked
2001:1203:a600::/40 IPv6 /40 not checked
2001:1203:a700::/40 IPv6 /40 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS270172 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS270172 in AS paths

Observed upstreams
Families
AS270158 270158 932 4,235
v4 v6
AS28458 28458 388 2,536
v4 v6

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS270172 in AS paths

Observed downstreams
Families
AS272391 256 338
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.