Observed topology
AS214205 ZVSHOSTING
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS214205: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 58 |
| AS214762 | Sebastian Stefanek trading as MatHost.eu | Hosting | IPv6 | 37 |
| AS34927 | iFog GmbH | Hosting | IPv6 | 36 |
| AS208453 | Johan Karlsson trading as SweHosting | Hosting | IPv6 | 33 |
| AS44324 | MoeDove LLC | Residential | IPv6 | 32 |
| AS199829 | Akronic Network LTDA | Unclassified | IPv6 | 19 |
| AS214331 | TESKE VIRTUAL SYSTEM LTDA | Unclassified | IPv6 | 18 |
| AS214757 | Jakub Krsa | Unclassified | IPv6 | 6 |
| AS215638 | Cilix Limited | Residential | IPv6 | 5 |
| AS24482 | SG.GS | Hosting | IPv6 | 2 |
Transit
Downstream networks
Networks for which AS214205 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS219412 | Lewis Brown | Unclassified | IPv6 | 189 |
| AS218569 | Viktor Nesmeianov | Unclassified | IPv4 IPv6 | 53 |
| AS57330 | Sichuan Giraffe Technology Co., Ltd. | Residential | IPv6 | 43 |
| AS219123 | Oleg Mironov | Unclassified | IPv6 | 40 |
| AS201421 | Daniel Muehlbachler-Pietrzykowski | Unclassified | IPv6 | 4 |
| AS39753 | Kai Liu | Unclassified | IPv6 | 2 |
| AS208733 | Erick Hoffmann | Unclassified | IPv6 | 2 |
| AS214508 | Manu Braibant | Unclassified | IPv6 | 1 |
| AS218830 | Dmitrii Pimkin | Unclassified | IPv6 | 1 |
| AS270765 | VIVA PIXEL AGENCIA DIGITAL | Unclassified | IPv6 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS214205 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 444 |
| AS219412 | Lewis Brown | Unclassified | IPv6 | 363 |
| AS218569 | Viktor Nesmeianov | Unclassified | IPv4 IPv6 | 75 |
| AS214757 | Jakub Krsa | Unclassified | IPv4 IPv6 | 59 |
| AS57330 | Sichuan Giraffe Technology Co., Ltd. | Residential | IPv6 | 43 |
| AS215638 | Cilix Limited | Residential | IPv6 | 41 |
| AS219123 | Oleg Mironov | Unclassified | IPv6 | 40 |
| AS214762 | Sebastian Stefanek trading as MatHost.eu | Hosting | IPv6 | 37 |
| AS34927 | iFog GmbH | Hosting | IPv6 | 36 |
| AS208453 | Johan Karlsson trading as SweHosting | Hosting | IPv6 | 33 |
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.