asn.dev

Observed topology

AS28613 HUGHES TELECOMUNICACOES DO BRASIL LTDA.

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28613: 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
AS6621Hughes Network Systems, LLCResidentialIPv4 IPv6786
AS3356Level 3 Parent, LLCTransitIPv4 IPv6424
AS812Rogers Communications Canada Inc.MobileIPv4 IPv6381
AS52320GlobeNet Cabos Submarinos Colombia, S.A.S.UnclassifiedIPv4360
AS32098Transtelco IncUnclassifiedIPv4 IPv684
AS6327Shaw CommunicationsResidentialIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS266417HUGHES TELECOMUNICACOES DO BRASIL LTDA.UnclassifiedIPv4117

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6621Hughes Network Systems, LLCResidentialIPv4 IPv6786
AS3356Level 3 Parent, LLCTransitIPv4 IPv6424
AS812Rogers Communications Canada Inc.MobileIPv4 IPv6381
AS52320GlobeNet Cabos Submarinos Colombia, S.A.S.UnclassifiedIPv4360
AS266417HUGHES TELECOMUNICACOES DO BRASIL LTDA.UnclassifiedIPv4117
AS32098Transtelco IncUnclassifiedIPv4 IPv684
AS4230CLARO S.A.ResidentialIPv458
AS6461Zayo BandwidthTransitIPv448
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv411
AS6327Shaw CommunicationsResidentialIPv48

Provenance

Where this comes from

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