Observed topology
AS8455 ATOM86-AS ATOM86
Hosting RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS8455: 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 | 301 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 276 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 245 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 210 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 65 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 45 |
| AS1764 | Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH | Unclassified | IPv4 IPv6 | 35 |
| AS1836 | green.ch AG | Residential | IPv4 IPv6 | 35 |
| AS9304 | HGC Global Communications Limited | Hosting | IPv4 IPv6 | 35 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 35 |
Transit
Downstream networks
Networks for which AS8455 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS51088 | A2B IP B.V. | Unclassified | IPv4 IPv6 | 1,836 |
| AS12041 | Afilias, Inc. | Hosting | IPv4 IPv6 | 826 |
| AS41960 | Nextpertise B.V. | Unclassified | IPv4 IPv6 | 756 |
| AS47543 | atom86 BV | Unclassified | IPv4 IPv6 | 737 |
| AS57795 | NG-BLU Networks B.V. | Unclassified | IPv4 IPv6 | 608 |
| AS49685 | Signet B.V. | Unclassified | IPv4 IPv6 | 601 |
| AS16003 | Fornex Hosting S.L. | Unclassified | IPv4 IPv6 | 561 |
| AS29028 | DirectVPS B.V. | Hosting | IPv4 IPv6 | 535 |
| AS31251 | Falco IPR BV | Unclassified | IPv4 IPv6 | 472 |
| AS34373 | XXLnet B.V. | Unclassified | IPv4 IPv6 | 425 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8455 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS51088 | A2B IP B.V. | Unclassified | IPv4 IPv6 | 9,674 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 6,528 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 5,474 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 4,190 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 3,566 |
| AS49685 | Signet B.V. | Unclassified | IPv4 IPv6 | 2,951 |
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 IPv6 | 1,665 |
| AS41960 | Nextpertise B.V. | Unclassified | IPv4 IPv6 | 1,146 |
| AS42708 | Glesys AB | Unclassified | IPv4 IPv6 | 1,146 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 1,116 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.22M 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.