Skip to main content

AS265662

265662

Autonomous System AS265662 from CL-TLSP-LACNIC

Registry

Authoritative registration data

AS number
265662
Name
265662
Organisation
Autonomous System AS265662 from CL-TLSP-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS265662
38.250.104.0/22 IPv4 /22 not checked
45.4.0.0/22 IPv4 /22 not checked
2803:ec0::/32 IPv6 /32 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 AS265662
Address families
PIT Santiago - PIT Chile: LAN 40,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 AS265662 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS265662 in AS paths

Observed upstreams
Families
AS263702 263702 1,107 2,936
v4 v6
AS174 COGENT-174 560 1,453
v4 v6
AS12956 TELXIUS 245 602
v4 v6
AS6057 6057 2 18
v4 v6

No rows match “”.

Showing – of

Observed downstreams

5 networks seen after AS265662 in AS paths

Observed downstreams
Families
AS269988 269988 515 2,275
v4
AS64131 64131 350 851
v4 v6
AS267733 266 348
v4
AS266844 266844 240 316
v4
AS266776 266776 87 126
v4

No rows match “”.

Showing – of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 4 13
v4 v6
AS36236 NETACTUATE 2 10
v4 v6
AS269956 269956 1 9
v4 v6
AS51185 MAINSTREAMING-AS 1 8
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. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.