Skip to main content

AS27672

27672

Autonomous System AS27672 from MX-SYEE-LACNIC

Registry

Authoritative registration data

AS number
27672
Name
27672
Organisation
Autonomous System AS27672 from MX-SYEE-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

17

IPv6 prefixes

4

Total announced

21

Announced prefixes

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

Prefixes announced by AS27672
177.240.128.0/19 IPv4 /19 not checked
189.199.128.0/19 IPv4 /19 not checked
177.224.176.0/21 IPv4 /21 not checked
189.199.88.0/22 IPv4 /22 not checked
189.199.92.0/22 IPv4 /22 not checked
200.77.124.0/22 IPv4 /22 not checked
200.77.144.0/22 IPv4 /22 not checked
189.195.160.0/23 IPv4 /23 not checked
200.77.138.0/23 IPv4 /23 not checked
187.244.25.0/24 IPv4 /24 not checked
189.199.2.0/24 IPv4 /24 not checked
189.199.3.0/24 IPv4 /24 not checked
189.199.6.0/24 IPv4 /24 not checked
189.199.90.0/24 IPv4 /24 not checked
189.199.91.0/24 IPv4 /24 not checked
189.199.95.0/24 IPv4 /24 not checked
200.77.139.0/24 IPv4 /24 not checked
2806:266:300::/40 IPv6 /40 not checked
2806:266:400::/40 IPv6 /40 not checked
2806:260:1009::/48 IPv6 /48 not checked
2806:266:501::/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

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

Source:ripestat:asn-neighbours observed

Observed upstreams

1 networks seen before AS27672 in AS paths

Observed upstreams
Families
AS13999 13999 592 6,932
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS27672 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

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.