Skip to main content

AS22975

22975

Autonomous System AS22975 from CL-BACH-LACNIC

Registry

Authoritative registration data

AS number
22975
Name
22975
Organisation
Autonomous System AS22975 from CL-BACH-LACNIC
Country
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

0

Total announced

9

Announced prefixes

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

Prefixes announced by AS22975
200.14.130.0/24 IPv4 /24 not checked
200.14.132.0/24 IPv4 /24 not checked
200.14.133.0/24 IPv4 /24 not checked
200.14.135.0/24 IPv4 /24 not checked
200.14.140.0/24 IPv4 /24 not checked
200.14.156.0/24 IPv4 /24 not checked
200.14.160.0/24 IPv4 /24 not checked
200.14.176.0/24 IPv4 /24 not checked
200.14.177.0/24 IPv4 /24 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 AS22975
Address families
PIT Santiago - PIT Chile: LAN 20,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 AS22975 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS22975 in AS paths

Observed upstreams
Families
AS19551 INCAPSULA 286 1,998
v4
AS22850 PIT-US 254 650
v4
AS6471 266 337
v4
AS6057 6057 2 4
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS22975 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 1 2
v4
AS49544 i3Dnet 1 2
v4
AS51185 MAINSTREAMING-AS 1 2
v4
AS269956 1 2
v4
AS270014 270014 1 2
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.