Observed topology
AS14618 AMAZON-AES
Hosting ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS14618: 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 |
|---|---|---|---|---|
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 IPv6 | 115,333 |
Transit
Downstream networks
Networks for which AS14618 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8011 | MongoDB, Inc. | Unclassified | IPv4 | 305 |
| AS399805 | Goliad Technologies | Unclassified | IPv4 IPv6 | 190 |
| AS23280 | Venn Technology Corp | Unclassified | IPv4 | 183 |
| AS54790 | Sharecare, Inc. | Unclassified | IPv4 | 183 |
| AS61162 | Klarna Bank AB | Unclassified | IPv4 | 183 |
| AS398378 | Boost Mobile | Unclassified | IPv4 | 183 |
| AS922 | GoCodeIT Inc | Unclassified | IPv4 IPv6 | 156 |
| AS16766 | Island Technology, Inc. | Unclassified | IPv4 IPv6 | 129 |
| AS401587 | TextNow Inc. | Unclassified | IPv4 IPv6 | 129 |
| AS36692 | Cisco OpenDNS, LLC | Hosting | IPv4 | 122 |
Adjacency
Adjacent networks
Every AS seen directly next to AS14618 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 IPv6 | 120,048 |
| AS8011 | MongoDB, Inc. | Unclassified | IPv4 | 305 |
| AS399805 | Goliad Technologies | Unclassified | IPv4 IPv6 | 190 |
| AS23280 | Venn Technology Corp | Unclassified | IPv4 | 183 |
| AS54790 | Sharecare, Inc. | Unclassified | IPv4 | 183 |
| AS61162 | Klarna Bank AB | Unclassified | IPv4 | 183 |
| AS398378 | Boost Mobile | Unclassified | IPv4 | 183 |
| AS922 | GoCodeIT Inc | Unclassified | IPv4 IPv6 | 156 |
| AS16766 | Island Technology, Inc. | Unclassified | IPv4 IPv6 | 129 |
| AS401587 | TextNow Inc. | Unclassified | IPv4 IPv6 | 129 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.25M 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.