Observed topology
AS50867 ORG-LVA15-AS
Hosting DROP-listed space RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS50867: 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 |
|---|---|---|---|---|
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 1,414 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 1,039 |
| AS29076 | Citytelecom LLC | Hosting | IPv4 | 659 |
| AS202984 | Chernyshov Aleksandr Aleksandrovich | Unclassified | IPv4 | 659 |
| AS59692 | IQWeb FZ-LLC | Unclassified | IPv4 | 593 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 336 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 108 |
| AS24482 | SG.GS | Hosting | IPv4 | 78 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 78 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 78 |
Transit
Downstream networks
Networks for which AS50867 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS209588 | Flyservers S.A. | Hosting | IPv4 | 119 |
| AS207704 | APEIRON GLOBAL Pvt. Ltd. | Unclassified | IPv4 | 61 |
| AS200313 | IT WEB LTD | Unclassified | IPv4 | 59 |
| AS214872 | Umnov Aleksandr Valerevich | Unclassified | IPv4 | 59 |
| AS25534 | 10G.KZ LLC | Unclassified | IPv4 | 39 |
| AS62316 | OOO "Contact-center GRAN" | Unclassified | IPv4 | 12 |
| AS200662 | LLC "Beta Voip" | Unclassified | IPv4 | 11 |
Adjacency
Adjacent networks
Every AS seen directly next to AS50867 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 1,523 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 1,121 |
| AS29076 | Citytelecom LLC | Hosting | IPv4 | 702 |
| AS202984 | Chernyshov Aleksandr Aleksandrovich | Unclassified | IPv4 | 690 |
| AS59692 | IQWeb FZ-LLC | Unclassified | IPv4 | 625 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 364 |
| AS209588 | Flyservers S.A. | Hosting | IPv4 | 119 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 115 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 88 |
| AS24482 | SG.GS | Hosting | IPv4 | 83 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-21 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.