asn.dev

Observed topology

AS265462 W.E. SPEEDFIBRA LTDA

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265462: 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
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6120
AS264996SERVLINK TELECOM LTDA - MEResidentialIPv4 IPv637
AS6939Hurricane Electric LLCTransitIPv49
AS263276BBG TELECOM LTDAResidentialIPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS266093ARENA HI-TECH TECNOLOGIA LTDAUnclassifiedIPv4 IPv697
AS266322E. SILVA AZEDO EIRELI - MEUnclassifiedIPv4 IPv611

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6177
AS266093ARENA HI-TECH TECNOLOGIA LTDAUnclassifiedIPv4 IPv697
AS264996SERVLINK TELECOM LTDA - MEResidentialIPv4 IPv679
AS6939Hurricane Electric LLCTransitIPv418
AS266322E. SILVA AZEDO EIRELI - MEUnclassifiedIPv4 IPv611
AS263276BBG TELECOM LTDAResidentialIPv63

Provenance

Where this comes from

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