asn.dev

Observed topology

AS44700 HAENDLEKORTE-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS44700: 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
AS50629LWLcom GmbHUnclassifiedIPv4 IPv6252
AS1299Arelion Sweden ABTransitIPv4 IPv696
AS33891Core-Backbone GmbHHostingIPv4 IPv674
AS3320Deutsche Telekom AGMobileIPv4 IPv614

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44180ETN Internet GmbH & Co. KGUnclassifiedIPv4 IPv6269
AS207686Martin MoutardeUnclassifiedIPv4 IPv678
AS60789QITS GmbHUnclassifiedIPv455
AS9135ITEMAX GmbHUnclassifiedIPv428

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS50629LWLcom GmbHUnclassifiedIPv4 IPv6515
AS44180ETN Internet GmbH & Co. KGUnclassifiedIPv4 IPv6269
AS33891Core-Backbone GmbHHostingIPv4 IPv6193
AS1299Arelion Sweden ABTransitIPv4 IPv6124
AS207686Martin MoutardeUnclassifiedIPv4 IPv678
AS60789QITS GmbHUnclassifiedIPv455
AS9135ITEMAX GmbHUnclassifiedIPv428
AS3320Deutsche Telekom AGMobileIPv4 IPv624
AS35548smartTERRA GmbHHostingIPv410

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-26 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.