asn.dev

Observed topology

AS263922 AS263922 - SPEED TURBO TELECOM

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263922: 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
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv6577
AS6939Hurricane Electric LLCTransitIPv473
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv660
AS24482SG.GSHostingIPv47
AS35280F5 Networks SARLHostingIPv41
AS37721Virtual Technologies & SolutionsResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267519CONEXAO INFORMATICA SILVA LTDAUnclassifiedIPv4 IPv6511
AS267625LD PRODUTOS DE INFORMATICA EIRELI - MEUnclassifiedIPv4 IPv6251
AS274617RAFAEL RIBEIRO DE SOUZAUnclassifiedIPv4 IPv692

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv6821
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6794
AS267625LD PRODUTOS DE INFORMATICA EIRELI - MEUnclassifiedIPv4 IPv6536
AS267519CONEXAO INFORMATICA SILVA LTDAUnclassifiedIPv4 IPv6511
AS6939Hurricane Electric LLCTransitIPv4 IPv6212
AS274617RAFAEL RIBEIRO DE SOUZAUnclassifiedIPv4 IPv692
AS24482SG.GSHostingIPv4 IPv621
AS35280F5 Networks SARLHostingIPv4 IPv65
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv65

Provenance

Where this comes from

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