Observed topology
AS18914 ETS-TELCO
Hosting ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS18914: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 693 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 104 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 58 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 52 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 29 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 16 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 16 |
| AS3130 | RGnet OU | Unclassified | IPv4 | 14 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 12 |
Transit
Downstream networks
Networks for which AS18914 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS36303 | Vickery Internet | Unclassified | IPv4 IPv6 | 166 |
| AS399525 | Rimrock Wireless | Unclassified | IPv4 IPv6 | 166 |
| AS402443 | SimpliFiber | Unclassified | IPv4 | 130 |
| AS402019 | Jerome County Idaho | Unclassified | IPv4 IPv6 | 101 |
| AS400647 | Cassia County | Unclassified | IPv4 IPv6 | 100 |
| AS53654 | TJF HOLDINGS | Unclassified | IPv4 IPv6 | 44 |
| AS25855 | ETS TELECOM | Unclassified | IPv4 | 6 |
Adjacency
Adjacent networks
Every AS seen directly next to AS18914 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,139 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 185 |
| AS36303 | Vickery Internet | Unclassified | IPv4 IPv6 | 166 |
| AS399525 | Rimrock Wireless | Unclassified | IPv4 IPv6 | 166 |
| AS402443 | SimpliFiber | Unclassified | IPv4 | 130 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 113 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 102 |
| AS402019 | Jerome County Idaho | Unclassified | IPv4 IPv6 | 101 |
| AS400647 | Cassia County | Unclassified | IPv4 IPv6 | 100 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 57 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-16 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.23M 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.