Observed topology
AS41009 VIZITNETUA-AS Oleksandr Melnyk
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS41009: 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 |
|---|---|---|---|---|
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 263 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 81 |
| AS35297 | Dataline LLC | Unclassified | IPv4 | 66 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 19 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 IPv6 | 13 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 7 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS41009 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS205127 | PP "Euronet" | Unclassified | IPv4 IPv6 | 206 |
| AS201094 | Mulgin Alexander Sergeevich | Unclassified | IPv4 IPv6 | 192 |
| AS210555 | D2CLOUD NETWORK SERVICES (PTY) LTD | Unclassified | IPv4 IPv6 | 90 |
| AS211947 | PP Vizit-Service | Unclassified | IPv4 IPv6 | 90 |
| AS41229 | Lushchan Evgenij Ivanovich | Unclassified | IPv4 | 59 |
| AS43744 | Orion City LLC | Unclassified | IPv4 | 59 |
| AS39822 | Center for Information Technologies "Fobos" Ltd. | Unclassified | IPv4 IPv6 | 14 |
| AS50576 | FREEWAY Plus LLC | Residential | IPv4 IPv6 | 9 |
| AS47283 | FOP Koval Dmitro Orestovich | Unclassified | IPv4 | 4 |
Adjacency
Adjacent networks
Every AS seen directly next to AS41009 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 672 |
| AS201094 | Mulgin Alexander Sergeevich | Unclassified | IPv4 IPv6 | 226 |
| AS205127 | PP "Euronet" | Unclassified | IPv4 IPv6 | 206 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 166 |
| AS35297 | Dataline LLC | Unclassified | IPv4 | 149 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 124 |
| AS210555 | D2CLOUD NETWORK SERVICES (PTY) LTD | Unclassified | IPv4 IPv6 | 90 |
| AS211947 | PP Vizit-Service | Unclassified | IPv4 IPv6 | 90 |
| AS43744 | Orion City LLC | Unclassified | IPv4 | 66 |
| AS41229 | Lushchan Evgenij Ivanovich | Unclassified | IPv4 | 59 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.