asn.dev

Observed topology

AS5430 FREENETDE freenet Datenkommunikations GmbH

Hosting RIPE

Upstreams 21 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 21
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 21

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 IPv666
AS6939Hurricane Electric LLCTransitIPv4 IPv664
AS3320Deutsche Telekom AGMobileIPv4 IPv610
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv610
AS24482SG.GSHostingIPv4 IPv64
AS29632Netassist International EOODUnclassifiedIPv64
AS33891Core-Backbone GmbHHostingIPv44
AS42708Glesys ABUnclassifiedIPv4 IPv64
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64

All 21 upstreams →

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 IPv6184
AS62086VIA-ONLINE GmbHHostingIPv4 IPv696

Adjacency

Adjacent networks

All 24

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6230
AS60175Wortmann AGUnclassifiedIPv4 IPv6184
AS13335Cloudflare, Inc.HostingIPv4130
AS6939Hurricane Electric LLCTransitIPv4 IPv6122
AS62086VIA-ONLINE GmbHHostingIPv4 IPv696
AS3320Deutsche Telekom AGMobileIPv4 IPv622
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv614
AS29632Netassist International EOODUnclassifiedIPv68
AS33891Core-Backbone GmbHHostingIPv48
AS212024Marc SchmittUnclassifiedIPv4 IPv68

All 24 adjacent →

Provenance

Where this comes from

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