Observed topology
AS48084 UMLC
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS48084: 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 |
|---|---|---|---|---|
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 51 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 22 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 IPv6 | 12 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 8 |
| AS8447 | A1 Telekom Austria AG | Residential | IPv4 | 1 |
| AS24482 | SG.GS | Hosting | IPv4 | 1 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 1 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 1 |
| AS56655 | Gigahost AS | Unclassified | IPv4 | 1 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS48084 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS47939 | TDV "Teleradio company "Yalta" LLC | Unclassified | IPv4 | 939 |
| AS25591 | BCLan LLC | Unclassified | IPv4 | 785 |
| AS203451 | K-telekom LLC | Unclassified | IPv4 | 514 |
| AS59833 | JSC Sevastopol Telekom | Unclassified | IPv4 IPv6 | 491 |
| AS35816 | Lancom Ltd. | Unclassified | IPv4 IPv6 | 272 |
| AS48004 | PE Tsibrankov Konstantin Igorevich | Unclassified | IPv4 | 120 |
| AS47349 | Teleradiocompany Bytradiotehnika Ltd. | Unclassified | IPv4 | 118 |
| AS41039 | Timer, LLC | Unclassified | IPv4 | 112 |
| AS199961 | Multitelesystems LLC | Unclassified | IPv4 IPv6 | 100 |
| AS203561 | KTK TELECOM LLC | Unclassified | IPv4 | 100 |
Adjacency
Adjacent networks
Every AS seen directly next to AS48084 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 1,554 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 1,320 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 1,186 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 IPv6 | 1,077 |
| AS199961 | Multitelesystems LLC | Unclassified | IPv4 IPv6 | 1,015 |
| AS47939 | TDV "Teleradio company "Yalta" LLC | Unclassified | IPv4 | 939 |
| AS25591 | BCLan LLC | Unclassified | IPv4 | 785 |
| AS203451 | K-telekom LLC | Unclassified | IPv4 | 514 |
| AS59833 | JSC Sevastopol Telekom | Unclassified | IPv4 IPv6 | 491 |
| AS12773 | Meshnet ltd. | Unclassified | IPv4 | 384 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-18 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.