Observed topology
AS8860 DELTA-BG-AS
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS8860: 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 |
|---|---|---|---|---|
| AS57463 | NetIX Communications JSC | Unclassified | IPv4 IPv6 | 541 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 500 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 483 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 285 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 187 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 158 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 90 |
| AS8280 | SYNAPSECOM S.A. Provider of Telecommunications and Internet Services | Hosting | IPv4 IPv6 | 46 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 46 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 46 |
Transit
Downstream networks
Networks for which AS8860 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS200418 | Victor Connect Ltd. | Unclassified | IPv4 | 236 |
| AS203918 | Securax Ltd. | Unclassified | IPv4 IPv6 | 86 |
| AS31522 | BTV MEDIA GROUP EAD | Unclassified | IPv4 | 59 |
| AS60200 | Victor Connect Ltd. | Unclassified | IPv4 | 59 |
| AS202357 | Sopharma Trading Jsc | Unclassified | IPv4 | 50 |
| AS200533 | Civil association Init Lab | Hosting | IPv4 IPv6 | 44 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8860 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS57463 | NetIX Communications JSC | Unclassified | IPv4 IPv6 | 655 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 601 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 573 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 325 |
| AS200418 | Victor Connect Ltd. | Unclassified | IPv4 | 236 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 217 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 198 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 112 |
| AS203918 | Securax Ltd. | Unclassified | IPv4 IPv6 | 86 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 60 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-20 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.16M 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.