asn.dev

Observed topology

AS267700 GUESTCHOICE TV RD, S.R.L

Unclassified LACNIC

Upstreams 2 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 5
Adjacent (IPv6) 5
Upstream graph Who carries AS267700, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS267700 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267700: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS23379Blackburn Technologies II, LLCUnclassifiedIPv4176
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4 IPv6150

Transit

Downstream networks

inferred

Networks for which AS267700 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS269965LIGHTWAVE S.R.LUnclassifiedIPv4 IPv6812
AS274267FIBEX TELECOM SRLUnclassifiedIPv4 IPv6214

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS267700 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4 IPv64,728
AS271945AZTECA TELECOM S.R.L.UnclassifiedIPv4 IPv62,981
AS269965LIGHTWAVE S.R.LUnclassifiedIPv4 IPv61,595
AS23379Blackburn Technologies II, LLCUnclassifiedIPv4 IPv6388
AS274267FIBEX TELECOM SRLUnclassifiedIPv4 IPv6214

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.