asn.dev

Observed topology

AS28326 AS28326 - Total Telecom Ltda

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28326: 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
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6286
AS28329SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv4 IPv642

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268335ORACLON TELECOMUnclassifiedIPv668
AS265314Toolsoft Tecnologia LtdaUnclassifiedIPv4 IPv663
AS61603Goias Telecomunicacoes SA. - GOIAS TELECOMUnclassifiedIPv418
AS273547ST INFORMATICA E TELECOM LTDAUnclassifiedIPv415

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6375
AS28329SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv4 IPv6181
AS265314Toolsoft Tecnologia LtdaUnclassifiedIPv4 IPv671
AS273547ST INFORMATICA E TELECOM LTDAUnclassifiedIPv471
AS268335ORACLON TELECOMUnclassifiedIPv668
AS61603Goias Telecomunicacoes SA. - GOIAS TELECOMUnclassifiedIPv418

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.