asn.dev

Observed topology

AS9036 NEURONNEXION-AS Neuronnexion SCOP

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 27

Networks observed carrying traffic for AS9036: 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
AS6830Liberty Global Europe Holding B.V.ResidentialIPv4 IPv634
AS6939Hurricane Electric LLCTransitIPv4 IPv634
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv625
AS34549meerfarbig GmbH & Co. KGHostingIPv46
AS44530HOPUS SASUnclassifiedIPv46
AS9002RETN LimitedUnclassifiedIPv64
AS50304Blix Solutions ASUnclassifiedIPv44
AS24482SG.GSHostingIPv4 IPv63
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv63
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv63

All 27 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS47413Teleric SASUnclassifiedIPv460

Adjacency

Adjacent networks

All 28

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

ASNetworkTypeFamiliesPaths seen
AS47413Teleric SASUnclassifiedIPv460
AS6830Liberty Global Europe Holding B.V.ResidentialIPv4 IPv646
AS6939Hurricane Electric LLCTransitIPv4 IPv644
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv637
AS34549meerfarbig GmbH & Co. KGHostingIPv49
AS44530HOPUS SASUnclassifiedIPv49
AS50304Blix Solutions ASUnclassifiedIPv46
AS9002RETN LimitedUnclassifiedIPv64
AS24482SG.GSHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64

All 28 adjacent →

Provenance

Where this comes from

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