asn.dev

Observed topology

AS266470 GSM BAHIA PROVEDOR DE INTERNET LTDA

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266470: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv690
AS52873Softdados TelecomunicacoesUnclassifiedIPv4 IPv655
AS52720WEBFOCO TELECOMUNICACOES LTDAUnclassifiedIPv632
AS24482SG.GSHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv65
AS35280F5 Networks SARLHostingIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271013MP NET TELECOMUnclassifiedIPv4 IPv6125
AS271428EMISSON SOUSA SILVAUnclassifiedIPv4 IPv6102
AS265499GS Telecomunicacoes LtdaUnclassifiedIPv481

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52873Softdados TelecomunicacoesUnclassifiedIPv4 IPv6222
AS6939Hurricane Electric LLCTransitIPv4 IPv6137
AS271013MP NET TELECOMUnclassifiedIPv4 IPv6125
AS52720WEBFOCO TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6115
AS271428EMISSON SOUSA SILVAUnclassifiedIPv4 IPv6102
AS265499GS Telecomunicacoes LtdaUnclassifiedIPv481
AS24482SG.GSHostingIPv4 IPv611
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv69
AS35280F5 Networks SARLHostingIPv44

Provenance

Where this comes from

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