Skip to main content

AS265615

265615

Autonomous System AS265615 from MX-ASCV78-LACNIC

Registry

Authoritative registration data

AS number
265615
Name
265615
Organisation
Autonomous System AS265615 from MX-ASCV78-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

18

IPv6 prefixes

1

Total announced

19

Announced prefixes

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

Prefixes announced by AS265615
45.190.240.0/22 IPv4 /22 RPKI valid
189.201.178.0/24 IPv4 /24 not checked
189.206.22.0/24 IPv4 /24 not checked
201.151.150.0/24 IPv4 /24 not checked
201.151.151.0/24 IPv4 /24 RPKI valid
201.151.156.0/24 IPv4 /24 not checked
201.151.177.0/24 IPv4 /24 not checked
201.151.178.0/24 IPv4 /24 RPKI valid
201.163.96.0/24 IPv4 /24 RPKI valid
38.19.92.0/24 IPv4 /24 RPKI valid
38.19.93.0/24 IPv4 /24 not checked
38.19.94.0/24 IPv4 /24 not checked
38.22.172.0/24 IPv4 /24 not checked
38.22.187.0/24 IPv4 /24 not checked
45.190.240.0/24 IPv4 /24 RPKI valid
45.190.241.0/24 IPv4 /24 not checked
45.190.242.0/24 IPv4 /24 RPKI valid
45.190.243.0/24 IPv4 /24 RPKI valid
2806:36c::/32 IPv6 /32 RPKI valid

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

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS265615 in AS paths

Observed upstreams
Families
AS174 COGENT-174 310 2,566
v4
AS32098 TRANSTELCO-INC 649 2,083
v4 v6
AS11172 11172 568 1,618
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS265615 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.