Observed topology
AS41722 MIRAN-AS Miran Ltd.
Hosting RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS41722: 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 |
|---|---|---|---|---|
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 907 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 842 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 639 |
| AS201706 | SERVICEPIPE LLC | Unclassified | IPv4 | 60 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 42 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 40 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 40 |
Transit
Downstream networks
Networks for which AS41722 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS201738 | UFO TECHNOLOGIES LIMITED | Unclassified | IPv4 | 178 |
| AS212165 | Alex Group LLC | Unclassified | IPv4 IPv6 | 157 |
| AS205864 | Ediweb LLC | Unclassified | IPv4 | 104 |
| AS214367 | JSC "Pay Engine" | Unclassified | IPv4 | 61 |
| AS43951 | LLC "Lanit-Tercom" | Unclassified | IPv4 | 60 |
| AS57596 | ITH Ltd. | Unclassified | IPv4 | 60 |
| AS218988 | Lisitsina Elena Yurievna | Unclassified | IPv4 | 60 |
| AS56846 | JSC National satellite company | Unclassified | IPv4 | 43 |
| AS202989 | Ofis24 OOO | Unclassified | IPv4 | 8 |
| AS12654 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 6 |
Adjacency
Adjacent networks
Every AS seen directly next to AS41722 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 1,177 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 1,084 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 825 |
| AS201738 | UFO TECHNOLOGIES LIMITED | Unclassified | IPv4 | 178 |
| AS212165 | Alex Group LLC | Unclassified | IPv4 IPv6 | 157 |
| AS205864 | Ediweb LLC | Unclassified | IPv4 | 104 |
| AS214367 | JSC "Pay Engine" | Unclassified | IPv4 | 61 |
| AS43951 | LLC "Lanit-Tercom" | Unclassified | IPv4 | 60 |
| AS57596 | ITH Ltd. | Unclassified | IPv4 | 60 |
| AS201706 | SERVICEPIPE LLC | Unclassified | IPv4 | 60 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.