asn.dev

Observed topology

AS21396 NETCONNEX NetConnex Broadband Ltd.

Hosting RIPE

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS21396: 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
AS2914NTT America, Inc.TransitIPv4 IPv6186
AS6939Hurricane Electric LLCTransitIPv4 IPv6148
AS41230ASK4 LimitedResidentialIPv4 IPv688
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv673
AS33891Core-Backbone GmbHHostingIPv416
AS29169GANDI SASHostingIPv4 IPv612
AS42708Glesys ABUnclassifiedIPv4 IPv612
AS48185team.blue NVUnclassifiedIPv4 IPv612
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv612
AS3741Dimension DataUnclassifiedIPv48

All 16 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS12775JPC Infonet LtdUnclassifiedIPv61

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv6186
AS6939Hurricane Electric LLCTransitIPv4 IPv6148
AS41230ASK4 LimitedResidentialIPv4 IPv688
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv674
AS33891Core-Backbone GmbHHostingIPv416
AS29169GANDI SASHostingIPv4 IPv612
AS42708Glesys ABUnclassifiedIPv4 IPv612
AS48185team.blue NVUnclassifiedIPv4 IPv612
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv612
AS3741Dimension DataUnclassifiedIPv48

All 17 adjacent →

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.