Observed topology
AS40994 Alwyzon Hohl IT e.U.
Hosting RIPE Content
Transit
Upstream networks
Networks observed carrying traffic for AS40994: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 623 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 266 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 243 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 118 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 25 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 24 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 24 |
| AS202297 | Skylon Solutions Limited | Unclassified | IPv4 | 23 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 17 |
| AS9002 | RETN Limited | Unclassified | IPv6 | 2 |
Transit
Downstream networks
Networks for which AS40994 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS198510 | XTDEF-Limited | Unclassified | IPv4 IPv6 | 270 |
| AS203997 | XTDef Limited | Unclassified | IPv4 IPv6 | 265 |
| AS212085 | Alexander Bruegmann | Unclassified | IPv4 IPv6 | 100 |
| AS204136 | Kevin Holly | Unclassified | IPv4 IPv6 | 90 |
| AS205563 | Marc Gomez | Unclassified | IPv6 | 65 |
| AS218897 | Grachev Andrey Vladimirovich | Unclassified | IPv4 | 58 |
| AS215472 | Jan Ferme | Unclassified | IPv6 | 32 |
| AS216321 | Zero Attack Vector LLC | Unclassified | IPv6 | 32 |
| AS203391 | Cloud DNS Ltd | Hosting | IPv4 IPv6 | 16 |
| AS29997 | Vitalwerks Internet Solutions, LLC | Unclassified | IPv4 IPv6 | 12 |
Adjacency
Adjacent networks
Every AS seen directly next to AS40994 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 920 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 472 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 390 |
| AS198510 | XTDEF-Limited | Unclassified | IPv4 IPv6 | 270 |
| AS203997 | XTDef Limited | Unclassified | IPv4 IPv6 | 265 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 219 |
| AS212085 | Alexander Bruegmann | Unclassified | IPv4 IPv6 | 100 |
| AS204136 | Kevin Holly | Unclassified | IPv4 IPv6 | 90 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 88 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 69 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-06 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.