Skip to main content

AS264814

264814

Autonomous System AS264814 from CL-BGSP-LACNIC

Registry

Authoritative registration data

AS number
264814
Name
264814
Organisation
Autonomous System AS264814 from CL-BGSP-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

4

Total announced

8

Announced prefixes

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

Prefixes announced by AS264814
170.238.200.0/22 IPv4 /22 not checked
38.250.96.0/22 IPv4 /22 RPKI valid
170.238.200.0/23 IPv4 /23 RPKI valid
170.238.202.0/23 IPv4 /23 RPKI valid
2803:ecc0::/32 IPv6 /32 RPKI valid
2803:ecc0:100::/40 IPv6 /40 not checked
2803:ecc0:400::/40 IPv6 /40 not checked
2803:ecc0:700::/40 IPv6 /40 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 AS264814
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 AS264814 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS264814 in AS paths

Observed upstreams
Families
AS7195 7195 260 1,236
v4 v6
AS6939 HURRICANE 123 558
v6
AS174 COGENT-174 72 337
v4
AS263237 263237 16 59
v4 v6
AS6057 6057 2 18
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS264814 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 9
v4 v6
AS269956 269956 1 9
v4 v6
AS51185 MAINSTREAMING-AS 1 3
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.