asn.dev

Observed topology

AS266471 Silva Oliveira Servicos de Informatica Ltda ME

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266471: 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 IPv6115
AS263877rede banda largaResidentialIPv4 IPv645
AS268452FLASH + TELECOMUnclassifiedIPv4 IPv642
AS24482SG.GSHostingIPv4 IPv68
AS35280F5 Networks SARLHostingIPv4 IPv67
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv67

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS274511IPNETWORK TELECOMUNICACOES E SOLUCOES LTDAUnclassifiedIPv6131
AS268452FLASH + TELECOMUnclassifiedIPv4 IPv671

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6279
AS274511IPNETWORK TELECOMUNICACOES E SOLUCOES LTDAUnclassifiedIPv4 IPv6190
AS268452FLASH + TELECOMUnclassifiedIPv4 IPv6140
AS263877rede banda largaResidentialIPv4 IPv6135
AS24482SG.GSHostingIPv4 IPv617
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv614
AS35280F5 Networks SARLHostingIPv4 IPv613

Provenance

Where this comes from

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