Skip to main content

AS266844

266844

Autonomous System AS266844 from CL-MTSP-LACNIC

Registry

Authoritative registration data

AS number
266844
Name
266844
Organisation
Autonomous System AS266844 from CL-MTSP-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

0

Total announced

3

Announced prefixes

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

Prefixes announced by AS266844
45.238.152.0/22 IPv4 /22 not checked
45.238.152.0/23 IPv4 /23 not checked
45.238.154.0/23 IPv4 /23 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 AS266844
Address families
PIT Santiago - PIT Chile: LAN 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 AS266844 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS266844 in AS paths

Observed upstreams
Families
AS265662 265662 205 254
v4
AS263237 263237 75 139
v4
AS6057 6057 2 8
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS266844 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS36236 NETACTUATE 1 4
v4
AS49544 i3Dnet 1 4
v4
AS51185 MAINSTREAMING-AS 1 4
v4
AS269956 269956 1 4
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.