asn.dev

Observed topology

AS266371 R7R - ME

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266371: 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 IPv6150
AS28186ITS TELECOMUNICACOES LTDAUnclassifiedIPv459

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS266554QST Telecom LTDA - MEUnclassifiedIPv4 IPv6453
AS267052SHIFT TELECOMUNICACOES E MULTIMIDIA LTDAUnclassifiedIPv4 IPv6186
AS269698INTERCLUB FIBRA TELECOM LTDAUnclassifiedIPv4 IPv692
AS271352Starsat Telecom Comercio e Servicos LTDAUnclassifiedIPv4 IPv645
AS61919AR3 Servicos EIRELI MEHostingIPv433

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6615
AS266554QST Telecom LTDA - MEUnclassifiedIPv4 IPv6453
AS28186ITS TELECOMUNICACOES LTDAUnclassifiedIPv4403
AS267052SHIFT TELECOMUNICACOES E MULTIMIDIA LTDAUnclassifiedIPv4 IPv6186
AS269698INTERCLUB FIBRA TELECOM LTDAUnclassifiedIPv4 IPv692
AS271352Starsat Telecom Comercio e Servicos LTDAUnclassifiedIPv4 IPv645
AS61919AR3 Servicos EIRELI MEHostingIPv433

Provenance

Where this comes from

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