Observed topology
AS44684 MYTHIC Mythic Beasts Ltd
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS44684: 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 | 133 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 89 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 59 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 25 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 14 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 9 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 9 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 9 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 9 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 9 |
Transit
Downstream networks
Networks for which AS44684 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS58101 | Gladserv Limited | Unclassified | IPv4 IPv6 | 306 |
| AS206924 | Ben Cartwright-Cox | Unclassified | IPv4 IPv6 | 160 |
| AS45034 | Michael Stenz | Unclassified | IPv4 | 120 |
| AS212240 | RIK Networks Ltd | Unclassified | IPv4 | 98 |
| AS213185 | Eta Heese | Unclassified | IPv4 IPv6 | 93 |
| AS57483 | Ian Chilton | Unclassified | IPv4 IPv6 | 88 |
| AS198219 | Charlie Camilleri | Unclassified | IPv6 | 73 |
| AS47426 | Advitel Ltd | Unclassified | IPv4 IPv6 | 70 |
| AS219494 | Hackworth Ltd | Unclassified | IPv6 | 66 |
| AS213831 | Toby Dixon | Unclassified | IPv4 | 60 |
Adjacency
Adjacent networks
Every AS seen directly next to AS44684 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 520 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 333 |
| AS58101 | Gladserv Limited | Unclassified | IPv4 IPv6 | 306 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 242 |
| AS206924 | Ben Cartwright-Cox | Unclassified | IPv4 IPv6 | 160 |
| AS45034 | Michael Stenz | Unclassified | IPv4 | 120 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 110 |
| AS212240 | RIK Networks Ltd | Unclassified | IPv4 | 98 |
| AS213185 | Eta Heese | Unclassified | IPv4 IPv6 | 93 |
| AS57483 | Ian Chilton | Unclassified | IPv4 IPv6 | 88 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-28 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.