asn.dev

Observed topology

AS5430 FREENETDE Wortmann AG

Hosting RIPE NSP

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

Transit

Upstream networks

All 23

Networks observed carrying traffic for AS5430: 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
AS13335Cloudflare, Inc.HostingIPv4130
AS1299Arelion Sweden ABTransitIPv4 IPv662
AS6939Hurricane Electric LLCTransitIPv4 IPv662
AS3320Deutsche Telekom AGMobileIPv4 IPv612
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv64
AS33891Core-Backbone GmbHHostingIPv44
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv64
AS212024Marc SchmittUnclassifiedIPv4 IPv64
AS213241TECHIT.BE SRLResidentialIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS60175Wortmann AGUnclassifiedIPv4 IPv6229
AS62086VIA-ONLINE GmbHHostingIPv4 IPv695

Adjacency

Adjacent networks

All 25

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

ASNetworkTypeFamiliesPaths seen
AS60175Wortmann AGUnclassifiedIPv4 IPv6229
AS1299Arelion Sweden ABTransitIPv4 IPv6222
AS13335Cloudflare, Inc.HostingIPv4130
AS6939Hurricane Electric LLCTransitIPv4 IPv6121
AS62086VIA-ONLINE GmbHHostingIPv4 IPv695
AS3320Deutsche Telekom AGMobileIPv4 IPv625
AS212024Marc SchmittUnclassifiedIPv4 IPv617
AS213241TECHIT.BE SRLResidentialIPv4 IPv617
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv614
AS20485Joint Stock Company TransTeleComUnclassifiedIPv413

Provenance

Where this comes from

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