asn.dev

Observed topology

AS265407 AS265407 - TMK NET LTDA

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265407: 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
AS265023TMK NET LTDAUnclassifiedIPv4 IPv6336

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271503PROVEDOR SUPERCELL NETUnclassifiedIPv4 IPv6212
AS263941MegaNET Servicos de Comunicacao Multimidia LtdaUnclassifiedIPv4 IPv692
AS262727AtualNet Provedor de Internet LtdaResidentialIPv460
AS274608ULTRANET TELECOMUNICACOES LTDAUnclassifiedIPv632
AS274333BIRA NET LTDAUnclassifiedIPv620

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS265023TMK NET LTDAUnclassifiedIPv4 IPv6752
AS271503PROVEDOR SUPERCELL NETUnclassifiedIPv4 IPv6212
AS263941MegaNET Servicos de Comunicacao Multimidia LtdaUnclassifiedIPv4 IPv692
AS262727AtualNet Provedor de Internet LtdaResidentialIPv460
AS274608ULTRANET TELECOMUNICACOES LTDAUnclassifiedIPv632
AS274333BIRA NET LTDAUnclassifiedIPv620

Provenance

Where this comes from

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