Observed topology
AS48293 UNIONTEL-RU-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS48293: 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 |
|---|---|---|---|---|
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 | 212 |
| AS47122 | CYBERFIRST LLC | Unclassified | IPv4 | 58 |
| AS29076 | Citytelecom LLC | Hosting | IPv4 IPv6 | 36 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 24 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 23 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 22 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 18 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 12 |
| AS20764 | CJSC RASCOM | Unclassified | IPv6 | 8 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 | 8 |
Transit
Downstream networks
Networks for which AS48293 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS205784 | NV Telecom LLC | Residential | IPv4 | 240 |
| AS60986 | ZagorodTelecom LLC | Unclassified | IPv4 | 229 |
| AS64419 | Ecotel, Ltd. | Unclassified | IPv4 | 154 |
| AS59665 | Ultra-Telecom LLC | Unclassified | IPv4 | 130 |
| AS44342 | NetComLine LLC | Unclassified | IPv4 | 65 |
| AS57375 | VillaNet LLC | Unclassified | IPv4 | 65 |
| AS208936 | PE Dmitry Filonenko | Unclassified | IPv4 | 65 |
| AS56493 | Dream Line OOO | Unclassified | IPv4 | 47 |
| AS43595 | Ugresha Network Ltd. | Unclassified | IPv6 | 22 |
| AS211134 | Intersys Ltd | Unclassified | IPv4 | 14 |
Adjacency
Adjacent networks
Every AS seen directly next to AS48293 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 | 1,036 |
| AS205784 | NV Telecom LLC | Residential | IPv4 | 240 |
| AS60986 | ZagorodTelecom LLC | Unclassified | IPv4 | 229 |
| AS64419 | Ecotel, Ltd. | Unclassified | IPv4 | 154 |
| AS59665 | Ultra-Telecom LLC | Unclassified | IPv4 | 130 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 68 |
| AS44342 | NetComLine LLC | Unclassified | IPv4 | 65 |
| AS57375 | VillaNet LLC | Unclassified | IPv4 | 65 |
| AS208936 | PE Dmitry Filonenko | Unclassified | IPv4 | 65 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 60 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-22 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.12M 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.