asn.dev

Observed topology

AS263585 AS263585 - DIGITAL NET RJ TELECOM EIRELI

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263585: 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
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv61,080
AS263009FORTE TELECOM LTDA.HostingIPv4 IPv691
AS6939Hurricane Electric LLCTransitIPv635
AS24482SG.GSHostingIPv65

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267565MEGABYTE SERVICOS DE TELECOMUNICACAO LTDA - MEUnclassifiedIPv4187
AS52567NEXNET FIBRA INTERNETUnclassifiedIPv4 IPv65

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv61,248
AS267565MEGABYTE SERVICOS DE TELECOMUNICACAO LTDA - MEUnclassifiedIPv4187
AS263009FORTE TELECOM LTDA.HostingIPv4 IPv6110
AS6939Hurricane Electric LLCTransitIPv636
AS24482SG.GSHostingIPv65
AS52567NEXNET FIBRA INTERNETUnclassifiedIPv4 IPv65
AS35280F5 Networks SARLHostingIPv44

Provenance

Where this comes from

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