asn.dev

Observed topology

AS267641 AS267641 - TN PROVEDOR

Unclassified ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267641: 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
AS262740VELOO NET LTDAResidentialIPv4 IPv6263
AS268314EWERTON DA SILVA LOPES TELECOMUNICACOESUnclassifiedIPv4 IPv692
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv650
AS6939Hurricane Electric LLCTransitIPv440
AS24482SG.GSHostingIPv4 IPv65

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271528GIGA FIBRAUnclassifiedIPv4232
AS268515SANTOS FERREIRA S F LTDAUnclassifiedIPv4118
AS269536jairo de f santos - meUnclassifiedIPv4 IPv664
AS269030TOPSAPP SOLUCOES EM TELECOMUNICACOES E REDES AVANCUnclassifiedIPv458

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS262740VELOO NET LTDAResidentialIPv4 IPv6541
AS271528GIGA FIBRAUnclassifiedIPv4232
AS6939Hurricane Electric LLCTransitIPv4 IPv6142
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6139
AS268515SANTOS FERREIRA S F LTDAUnclassifiedIPv4118
AS268314EWERTON DA SILVA LOPES TELECOMUNICACOESUnclassifiedIPv4 IPv692
AS269536jairo de f santos - meUnclassifiedIPv4 IPv664
AS269030TOPSAPP SOLUCOES EM TELECOMUNICACOES E REDES AVANCUnclassifiedIPv458
AS24482SG.GSHostingIPv4 IPv68

Provenance

Where this comes from

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