Skip to main content

AS274000

274000

Autonomous System AS274000 from CL-CCSP7-LACNIC

Registry

Authoritative registration data

AS number
274000
Name
274000
Organisation
Autonomous System AS274000 from CL-CCSP7-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

2

Total announced

3

Announced prefixes

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

Prefixes announced by AS274000
217.179.231.0/24 IPv4 /24 not checked
2803:78d0::/32 IPv6 /32 not checked
2803:78d0::/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 AS274000
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 AS274000 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS274000 in AS paths

Observed upstreams
Families
AS49121 INFTELE-AS 242 471
v4 v6
AS14259 14259 37 59
v4 v6
AS6057 6057 2 6
v4 v6
AS7195 7195 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS274000 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 3
v4 v6
AS269956 269956 1 3
v4 v6
AS270014 270014 1 2
v6

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.