Observed topology
AS201776 MIRANDA-AS Miranda-Media LLC
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS201776: 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 |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 5,490 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 IPv6 | 56 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 29 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 28 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 28 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 27 |
| AS25091 | IP-Max SA | Unclassified | IPv6 | 1 |
| AS56655 | Gigahost AS | Unclassified | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS201776 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS28761 | CrimeaCom South LLC | Unclassified | IPv4 | 1,334 |
| AS25591 | BCLan LLC | Unclassified | IPv4 | 988 |
| AS44539 | Redi LLC | Unclassified | IPv4 | 947 |
| AS42238 | Bospor-Telecom LLC | Unclassified | IPv4 | 806 |
| AS204144 | Comfort XXI Century Ltd. | Unclassified | IPv4 | 745 |
| AS20590 | Donbass Electronic Communications Ltd. | Unclassified | IPv4 | 715 |
| AS57164 | Viacheslav Fitiunin | Residential | IPv4 | 662 |
| AS35816 | Lancom Ltd. | Unclassified | IPv4 IPv6 | 658 |
| AS29031 | Lugansk Telephone Company LLC | Unclassified | IPv4 | 616 |
| AS59815 | Trinity Ltd | Unclassified | IPv4 | 615 |
Adjacency
Adjacent networks
Every AS seen directly next to AS201776 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 31,050 |
| AS28761 | CrimeaCom South LLC | Unclassified | IPv4 | 4,725 |
| AS44539 | Redi LLC | Unclassified | IPv4 | 4,340 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 2,384 |
| AS41039 | Timer, LLC | Unclassified | IPv4 | 2,123 |
| AS29031 | Lugansk Telephone Company LLC | Unclassified | IPv4 | 1,172 |
| AS25591 | BCLan LLC | Unclassified | IPv4 | 988 |
| AS12773 | Meshnet ltd. | Unclassified | IPv4 | 955 |
| AS59815 | Trinity Ltd | Unclassified | IPv4 | 814 |
| AS42238 | Bospor-Telecom LLC | Unclassified | IPv4 | 806 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.