Skip to main content

AS264827

264827

Autonomous System AS264827 from CL-WTSP-LACNIC

Registry

Authoritative registration data

AS number
264827
Name
264827
Organisation
Autonomous System AS264827 from CL-WTSP-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

3

Total announced

6

Announced prefixes

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

Prefixes announced by AS264827
170.247.204.0/22 IPv4 /22 not checked
187.102.192.0/23 IPv4 /23 not checked
187.102.195.0/24 IPv4 /24 not checked
2803:36c0::/32 IPv6 /32 not checked
2803:79e0::/32 IPv6 /32 RPKI valid
2803:36c0:e807::/48 IPv6 /48 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 AS264827
Address families
PIT Santiago - PIT Chile: LAN 200,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 AS264827 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS264827 in AS paths

Observed upstreams
Families
AS7195 7195 2,795 7,733
v4 v6
AS6057 6057 14 60
v4 v6

No rows match “”.

Showing – of

Observed downstreams

7 networks seen after AS264827 in AS paths

Observed downstreams
Families
AS273953 273953 547 2,417
v4 v6
AS270065 270065 300 1,114
v4
AS263728 263728 274 822
v4
AS266891 266891 285 373
v4
AS271778 271778 271 372
v4
AS269942 269942 265 347
v4
AS274940 274940 254 347
v6

No rows match “”.

Showing – of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 7 32
v4 v6
AS269956 269956 7 32
v4 v6
AS36236 NETACTUATE 7 30
v4 v6
AS51185 MAINSTREAMING-AS 7 28
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.