Skip to main content

AS270075

270075

Autonomous System AS270075 from CO-SRSA4-LACNIC

Registry

Authoritative registration data

AS number
270075
Name
270075
Organisation
Autonomous System AS270075 from CO-SRSA4-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

1

Total announced

7

Announced prefixes

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

Prefixes announced by AS270075
200.10.28.0/22 IPv4 /22 not checked
38.19.40.0/22 IPv4 /22 not checked
38.253.116.0/22 IPv4 /22 not checked
38.19.42.0/23 IPv4 /23 not checked
181.214.105.0/24 IPv4 /24 not checked
216.28.215.0/24 IPv4 /24 not checked
2803:c3e0::/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 AS270075
Address families
Equinix Bogota: Equinix IX - BG Metro 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 AS270075 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS270075 in AS paths

Observed upstreams
Families
AS7195 7195 2,557 4,677
v4 v6
AS174 COGENT-174 959 1,608
v4
AS18678 18678 174 366
v4
AS265688 265688 4 26
v4
AS262589 ASN262589 2 6
v4

No rows match “”.

Showing – of

Observed downstreams

6 networks seen after AS270075 in AS paths

Observed downstreams
Families
AS265693 265693 596 1,385
v4 v6
AS271947 271947 523 695
v4 v6
AS274200 274200 521 693
v4 v6
AS273821 273821 505 675
v4 v6
AS267757 267757 509 674
v4 v6
AS272086 272086 136 185
v4

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS36236 NETACTUATE 8 53
v4 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.