asn.dev

Observed topology

AS60294 DE-DGW Deutsche Glasfaser Wholesale Internet

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS60294: 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
AS8899inexio Informationstechnologie und Telekommunikation GmbhResidentialIPv4 IPv61,272

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS204296VEKA AGUnclassifiedIPv4 IPv6126
AS44819LB GmbHUnclassifiedIPv4112
AS205487DGN Deutsches Gesundheitsnetz Service GmbHUnclassifiedIPv472
AS9135ITEMAX GmbHUnclassifiedIPv4 IPv664
AS204672stadtwerker Versorgungs GmbHUnclassifiedIPv444
AS205542Datahaus GmbHUnclassifiedIPv437
AS62291esacom GmbHUnclassifiedIPv412
AS200846d.velop AGUnclassifiedIPv44

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8899inexio Informationstechnologie und Telekommunikation GmbhResidentialIPv4 IPv61,765
AS204296VEKA AGUnclassifiedIPv4 IPv6126
AS44819LB GmbHUnclassifiedIPv4112
AS205487DGN Deutsches Gesundheitsnetz Service GmbHUnclassifiedIPv472
AS204672stadtwerker Versorgungs GmbHUnclassifiedIPv466
AS9135ITEMAX GmbHUnclassifiedIPv4 IPv664
AS205542Datahaus GmbHUnclassifiedIPv437
AS62291esacom GmbHUnclassifiedIPv412
AS200846d.velop AGUnclassifiedIPv44

Provenance

Where this comes from

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