asn.dev

Observed topology

AS44964 DAPL DATAPLANET Ltd.

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS44964: 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
AS50509Transroute Telecom LTDUnclassifiedIPv4312
AS57304JSC "RetnNet"UnclassifiedIPv487
AS6939Hurricane Electric LLCTransitIPv632
AS29226JSC MastertelUnclassifiedIPv4 IPv631
AS24482SG.GSHostingIPv4 IPv68
AS9002RETN LimitedUnclassifiedIPv47
AS37721Virtual Technologies & SolutionsResidentialIPv47
AS49673Truenetwork LLCUnclassifiedIPv47
AS25091IP-Max SAUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS59906JSC "ICC MILANDR"UnclassifiedIPv465
AS199430Limited Liability Company GOODWOODUnclassifiedIPv465
AS206213Zhuchkov MikhailUnclassifiedIPv465
AS205978JSC LONMADIUnclassifiedIPv448

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS50509Transroute Telecom LTDUnclassifiedIPv4481
AS57304JSC "RetnNet"UnclassifiedIPv4127
AS59906JSC "ICC MILANDR"UnclassifiedIPv465
AS199430Limited Liability Company GOODWOODUnclassifiedIPv465
AS206213Zhuchkov MikhailUnclassifiedIPv465
AS29226JSC MastertelUnclassifiedIPv4 IPv652
AS205978JSC LONMADIUnclassifiedIPv448
AS6939Hurricane Electric LLCTransitIPv632
AS24482SG.GSHostingIPv4 IPv611
AS49673Truenetwork LLCUnclassifiedIPv411

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.