Observed topology
AS216078 KREMER-AS
Hosting Spamhaus ASN-DROP ARIN Network Services
Transit
Upstream networks
Networks observed carrying traffic for AS216078: 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 |
|---|---|---|---|---|
| AS50917 | Diederik Focko de Zee | Unclassified | IPv4 IPv6 | 324 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 220 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 92 |
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv6 | 34 |
| AS213622 | Falcon FZE LLC | Unclassified | IPv6 | 19 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 18 |
| AS213753 | InterEdge B.V. | Unclassified | IPv6 | 18 |
| AS12859 | BIT BV | Hosting | IPv4 IPv6 | 9 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 9 |
| AS401753 | BIXCE Inc | Unclassified | IPv4 IPv6 | 9 |
Transit
Downstream networks
Networks for which AS216078 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS211507 | Julian Achter | Unclassified | IPv4 IPv6 | 746 |
| AS200912 | Joel Krause | Hosting | IPv4 IPv6 | 194 |
| AS218713 | NETCENSUS LTD | Unclassified | IPv4 IPv6 | 131 |
| AS218986 | Snowcore Inc | Unclassified | IPv4 | 120 |
| AS214556 | Vexura UG (Haftungsbeschraenkt) | Unclassified | IPv4 IPv6 | 92 |
| AS402933 | Vosmet | Unclassified | IPv6 | 72 |
| AS151331 | Sora You | Unclassified | IPv6 | 37 |
| AS199436 | BangLong Yang | Unclassified | IPv6 | 37 |
| AS206540 | BEANSUMMERHOST NEXTGEN SHED HOSTING SOLUTIONS LLC | Unclassified | IPv6 | 37 |
| AS213501 | Ramil Rinatovich Kurmaev | Unclassified | IPv6 | 37 |
Adjacency
Adjacent networks
Every AS seen directly next to AS216078 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50917 | Diederik Focko de Zee | Unclassified | IPv4 IPv6 | 902 |
| AS211507 | Julian Achter | Unclassified | IPv4 IPv6 | 746 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 734 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 469 |
| AS200912 | Joel Krause | Hosting | IPv4 IPv6 | 194 |
| AS218713 | NETCENSUS LTD | Unclassified | IPv4 IPv6 | 131 |
| AS218986 | Snowcore Inc | Unclassified | IPv4 | 120 |
| AS214556 | Vexura UG (Haftungsbeschraenkt) | Unclassified | IPv4 IPv6 | 92 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 74 |
| AS402933 | Vosmet | Unclassified | IPv6 | 72 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.