Observed topology
AS39238 OKBPROGRESS OKB PROGRESS LLC
Hosting RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS39238: 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 |
|---|---|---|---|---|
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 7,882 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 IPv6 | 1,075 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 IPv6 | 592 |
| AS24482 | SG.GS | Hosting | IPv4 | 146 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 146 |
| AS34602 | MEGASVYAZ LLC | Unclassified | IPv4 | 45 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 10 |
Transit
Downstream networks
Networks for which AS39238 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS39238 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 8,858 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 IPv6 | 1,208 |
| AS49392 | LLC Baxet | Unclassified | IPv4 IPv6 | 713 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 IPv6 | 681 |
| AS51408 | OOO Sirius-Project | Unclassified | IPv4 IPv6 | 299 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 166 |
| AS24482 | SG.GS | Hosting | IPv4 | 165 |
| AS50409 | GK Osnova JSC | Unclassified | IPv4 | 65 |
| AS61141 | OST JSC | Unclassified | IPv4 | 65 |
| AS51578 | Limited Liabillity Company 'IT-VEGA' | Unclassified | IPv4 | 48 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-02 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.44M 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.