asn.dev

Observed topology

AS24592 NEXICA-AS

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS24592: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6252
AS2914NTT America, Inc.TransitIPv4 IPv6119
AS6939Hurricane Electric LLCTransitIPv4 IPv699
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv626
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4 IPv620
AS24482SG.GSHostingIPv4 IPv69
AS33891Core-Backbone GmbHHostingIPv49
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv69
AS25091IP-Max SAUnclassifiedIPv62
AS29632Netassist International EOODUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49008Elstir S.L.UnclassifiedIPv460

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6280
AS2914NTT America, Inc.TransitIPv4 IPv6134
AS6939Hurricane Electric LLCTransitIPv4 IPv6108
AS49008Elstir S.L.UnclassifiedIPv460
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv629
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4 IPv622
AS24482SG.GSHostingIPv4 IPv610
AS33891Core-Backbone GmbHHostingIPv410
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv610
AS25091IP-Max SAUnclassifiedIPv62

Provenance

Where this comes from

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