asn.dev

Observed topology

AS263599 Globo Net Informatica

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263599: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6738
AS262865Ired Internet LtdaResidentialIPv4 IPv6570
AS262355VSX NetworksUnclassifiedIPv4 IPv6244
AS24482SG.GSHostingIPv4 IPv649
AS35280F5 Networks SARLHostingIPv4 IPv627
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv627
AS14282ONN MULTIMIDIA LTDAResidentialIPv4 IPv616

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267640DIEGO JOSE MAUSSON - MEUnclassifiedIPv4 IPv6117

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6747
AS262865Ired Internet LtdaResidentialIPv4 IPv6576
AS262355VSX NetworksUnclassifiedIPv4 IPv6345
AS267640DIEGO JOSE MAUSSON - MEUnclassifiedIPv4 IPv6117
AS24482SG.GSHostingIPv4 IPv650
AS35280F5 Networks SARLHostingIPv4 IPv627
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv627
AS14282ONN MULTIMIDIA LTDAResidentialIPv4 IPv616

Provenance

Where this comes from

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