Skip to main content

AS267890

267890

Autonomous System AS267890 from CO-WALI-LACNIC

Registry

Authoritative registration data

AS number
267890
Name
267890
Organisation
Autonomous System AS267890 from CO-WALI-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS267890
45.178.12.0/22 IPv4 /22 not checked
2803:da60::/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 AS267890
Address families
Equinix Bogota: Equinix IX - BG Metro 10,000 Mbps IPv4 · IPv6
PIT - Colombia - Bogota 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 AS267890 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS267890 in AS paths

Observed upstreams
Families
AS3356 LEVEL3 212 409
v4 v6
AS23520 LIBERTY-NETWORKS 128 257
v4 v6
AS6057 6057 3 5
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS267890 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS36236 NETACTUATE 1 2
v4 v6
AS52320 52320 1 2
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.