Skip to main content

AS264838

264838

Autonomous System AS264838 from CL-IMLT11-LACNIC

Registry

Authoritative registration data

AS number
264838
Name
264838
Organisation
Autonomous System AS264838 from CL-IMLT11-LACNIC
Country
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

1

Total announced

8

Announced prefixes

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

Prefixes announced by AS264838
45.227.50.0/23 IPv4 /23 not checked
170.239.188.0/24 IPv4 /24 not checked
170.239.189.0/24 IPv4 /24 not checked
170.239.190.0/24 IPv4 /24 not checked
170.239.191.0/24 IPv4 /24 not checked
45.227.50.0/24 IPv4 /24 not checked
45.227.51.0/24 IPv4 /24 not checked
2803:3cc0::/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 AS264838
Address families
PIT Santiago - PIT Chile: LAN 80,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 AS264838 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS264838 in AS paths

Observed upstreams
Families
AS3356 LEVEL3 506 2,225
v4
AS6939 HURRICANE 132 253
v4 v6
AS6057 6057 2 10
v4 v6
AS3549 3 6
v4
AS7195 7195 1 1
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS264838 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS36236 NETACTUATE 2 7
v4 v6
AS49544 i3Dnet 1 5
v4 v6
AS269956 1 5
v4 v6
AS270014 270014 1 5
v4 v6
AS51185 MAINSTREAMING-AS 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.