asn.dev

Observed topology

AS273339 AS273339 - Su@net Provedor Ltda

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS273339: 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
AS266196BRASCOM SOLUCOES E TECNOLOGIA LTDA MEUnclassifiedIPv4 IPv697
AS61697AIRCONECT_COMUNICACOES LTDA-MEUnclassifiedIPv447
AS272545ULTRA NETWORK TELECOMUNICACOES LTDAUnclassifiedIPv66
AS6939Hurricane Electric LLCTransitIPv43
AS52468UFINET PANAMA S.A.UnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267961FRAGA SOFTWARE E TELECOMUNICACAOUnclassifiedIPv460
AS266196BRASCOM SOLUCOES E TECNOLOGIA LTDA MEUnclassifiedIPv425

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS266196BRASCOM SOLUCOES E TECNOLOGIA LTDA MEUnclassifiedIPv4 IPv6151
AS61697AIRCONECT_COMUNICACOES LTDA-MEUnclassifiedIPv498
AS267961FRAGA SOFTWARE E TELECOMUNICACAOUnclassifiedIPv460
AS6939Hurricane Electric LLCTransitIPv46
AS272545ULTRA NETWORK TELECOMUNICACOES LTDAUnclassifiedIPv66
AS52468UFINET PANAMA S.A.UnclassifiedIPv45

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.