Observed topology
AS8218 NEO-ASN Zayo Europe
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS8218: 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 |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 465 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 180 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 84 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 58 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 57 |
| AS1836 | green.ch AG | Residential | IPv4 IPv6 | 23 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 23 |
| AS8280 | SYNAPSECOM S.A. Provider of Telecommunications and Internet Services | Hosting | IPv4 IPv6 | 23 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 23 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 23 |
Transit
Downstream networks
Networks for which AS8218 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS31367 | Zayo Infrastructure France SA | Unclassified | IPv4 | 854 |
| AS213466 | BPCE S.A. | Unclassified | IPv4 | 743 |
| AS29605 | APX Integration SASU | Unclassified | IPv4 IPv6 | 601 |
| AS198551 | REZOCEAN SAS | Unclassified | IPv4 IPv6 | 599 |
| AS204273 | SPIE ICS | Unclassified | IPv4 IPv6 | 598 |
| AS31167 | AXIONE S.A.S. | Unclassified | IPv4 IPv6 | 514 |
| AS15695 | Expereo International BV | Unclassified | IPv4 IPv6 | 459 |
| AS34391 | PARITEL OPERATEUR SAS | Unclassified | IPv4 IPv6 | 451 |
| AS44902 | Covage Infra SASU | Unclassified | IPv4 | 444 |
| AS29513 | Foliateam Operateur SAS | Hosting | IPv4 IPv6 | 392 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8218 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 13,694 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 11,403 |
| AS47957 | Worldline IGSA SA | Unclassified | IPv4 | 3,357 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,184 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 1,682 |
| AS8280 | SYNAPSECOM S.A. Provider of Telecommunications and Internet Services | Hosting | IPv4 IPv6 | 1,167 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 1,101 |
| AS59919 | Brainbox S.r.l. | Residential | IPv4 | 1,056 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 1,014 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 1,006 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-15 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.09M 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.