Observed topology
AS9145 EWETEL
Residential APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS9145: 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 | 783 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 493 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 377 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 305 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 179 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 113 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 62 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 62 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 62 |
| AS42708 | Glesys AB | Unclassified | IPv4 IPv6 | 62 |
Transit
Downstream networks
Networks for which AS9145 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50621 | OMG.de GmbH | Unclassified | IPv4 IPv6 | 534 |
| AS31055 | Consultix GmbH | Unclassified | IPv4 | 363 |
| AS12460 | mandala IT GmbH | Unclassified | IPv4 IPv6 | 360 |
| AS21032 | TELTA Citynetz GmbH | Unclassified | IPv4 IPv6 | 238 |
| AS9066 | EWE TEL GmbH | Residential | IPv4 | 232 |
| AS34372 | VegaSystems GmbH & Co. KG | Hosting | IPv4 IPv6 | 206 |
| AS49957 | HQS High Quality Software GmbH | Unclassified | IPv4 | 174 |
| AS62291 | esacom GmbH | Unclassified | IPv4 | 162 |
| AS9099 | Finanz Informatik GmbH & Co. KG | Unclassified | IPv4 IPv6 | 158 |
| AS35242 | Thorsten Vogelsang trading as CGI Deutschland B.V. & Co. KG | Unclassified | IPv4 IPv6 | 150 |
Adjacency
Adjacent networks
Every AS seen directly next to AS9145 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 2,201 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 1,628 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 945 |
| AS9099 | Finanz Informatik GmbH & Co. KG | Unclassified | IPv4 IPv6 | 897 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 687 |
| AS50621 | OMG.de GmbH | Unclassified | IPv4 IPv6 | 534 |
| AS21032 | TELTA Citynetz GmbH | Unclassified | IPv4 IPv6 | 533 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 458 |
| AS34372 | VegaSystems GmbH & Co. KG | Hosting | IPv4 IPv6 | 428 |
| AS12460 | mandala IT GmbH | Unclassified | IPv4 IPv6 | 427 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.