asn.dev

Observed topology

AS266934 AS266934 - G5 TELECOM

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266934: 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
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6162
AS264300INFOPOINTNET FibraUnclassifiedIPv460
AS265194REDE IDEIA TELECOMUnclassifiedIPv460
AS264288GNET PROVEDORResidentialIPv4 IPv649

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS264201INFORNETFIBRA INTERNET LTDAUnclassifiedIPv4 IPv6275
AS266979CARUARU_ONLINE LTDAUnclassifiedIPv4 IPv6210
AS266310HECHO VIA INTERNET LTDAUnclassifiedIPv4 IPv6138
AS264300INFOPOINTNET FibraUnclassifiedIPv4 IPv643

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6450
AS264288GNET PROVEDORResidentialIPv4 IPv6435
AS264201INFORNETFIBRA INTERNET LTDAUnclassifiedIPv4 IPv6275
AS266979CARUARU_ONLINE LTDAUnclassifiedIPv4 IPv6210
AS266310HECHO VIA INTERNET LTDAUnclassifiedIPv4 IPv6138
AS264300INFOPOINTNET FibraUnclassifiedIPv4 IPv6111
AS265194REDE IDEIA TELECOMUnclassifiedIPv460

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.97M 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.