asn.dev

Observed topology

AS28604 Globo Comunicacao e Participacoes SA

Hosting APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28604: 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
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6898
AS6939Hurricane Electric LLCTransitIPv4 IPv6350
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6311
AS2914NTT America, Inc.TransitIPv4 IPv6239
AS3549Level 3 Parent, LLCTransitIPv4119
AS3356Level 3 Parent, LLCTransitIPv4 IPv647
AS24482SG.GSHostingIPv4 IPv633
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv614
AS4230CLARO S.A.ResidentialIPv4 IPv65

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6898
AS6939Hurricane Electric LLCTransitIPv4 IPv6350
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6311
AS2914NTT America, Inc.TransitIPv4 IPv6239
AS3549Level 3 Parent, LLCTransitIPv4119
AS3356Level 3 Parent, LLCTransitIPv4 IPv647
AS24482SG.GSHostingIPv4 IPv633
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv614
AS4230CLARO S.A.ResidentialIPv4 IPv65

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-18 10: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.