Observed topology
AS48882 OPTIMA-SHID-AS Optima-Shid LLC
Unclassified ARIN NSP
Transit
Upstream networks
Networks observed carrying traffic for AS48882: 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 |
|---|---|---|---|---|
| AS47502 | Optima-Telecom LLC | Unclassified | IPv4 | 501 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 88 |
| AS201776 | Miranda-Media Ltd | Unclassified | IPv4 | 47 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 45 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 11 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 11 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 11 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 11 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 9 |
| AS24482 | SG.GS | Hosting | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS48882 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS29128 | Digital Service Ltd. | Unclassified | IPv4 | 315 |
| AS34047 | LLC Internet-Service | Unclassified | IPv4 | 252 |
| AS208978 | Zinchenko Sergey Olegovich | Unclassified | IPv4 | 189 |
| AS215623 | OOO "LUGALINK" | Unclassified | IPv4 | 122 |
| AS47550 | Bratinov Oleg Vyacheslavovich | Unclassified | IPv4 | 106 |
| AS50942 | TK Zenit LLC | Unclassified | IPv4 | 61 |
| AS56416 | Solop Vyacheslav | Unclassified | IPv4 | 61 |
| AS213191 | Osipenko Alexander Nikolaevich | Unclassified | IPv4 | 48 |
| AS43972 | Sergey Olenich | Unclassified | IPv4 | 40 |
Adjacency
Adjacent networks
Every AS seen directly next to AS48882 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS47502 | Optima-Telecom LLC | Unclassified | IPv4 | 1,286 |
| AS29128 | Digital Service Ltd. | Unclassified | IPv4 | 315 |
| AS201776 | Miranda-Media Ltd | Unclassified | IPv4 | 287 |
| AS34047 | LLC Internet-Service | Unclassified | IPv4 | 252 |
| AS208978 | Zinchenko Sergey Olegovich | Unclassified | IPv4 | 189 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 164 |
| AS215623 | OOO "LUGALINK" | Unclassified | IPv4 | 122 |
| AS47550 | Bratinov Oleg Vyacheslavovich | Unclassified | IPv4 | 106 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 83 |
| AS50942 | TK Zenit LLC | Unclassified | IPv4 | 61 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.