Observed topology
AS12773 MM-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS12773: 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 |
|---|---|---|---|---|
| AS39089 | STATE UNITARY ENTERPRISE OF THE DONETSK PEOPLE'S REPUBLIC "UGLETELECOM" | Unclassified | IPv4 | 295 |
| AS48084 | Uzhnie Magistraljnie Linii Svyazi LLC | Unclassified | IPv4 | 60 |
| AS206810 | GUP DNR "UGLETELECOM" | Unclassified | IPv4 | 28 |
| AS44539 | Redi LLC | Unclassified | IPv4 | 27 |
| AS24482 | SG.GS | Hosting | IPv4 | 7 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 7 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 7 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 7 |
Transit
Downstream networks
Networks for which AS12773 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS34786 | OOO NPO Intermet | Unclassified | IPv4 | 314 |
| AS60839 | Vid Media Ltd. | Unclassified | IPv4 | 256 |
| AS25141 | Teleradiocompany Soniko-Svyaz Ltd | Unclassified | IPv4 | 248 |
| AS49757 | Igor Uspenskyy | Unclassified | IPv4 | 244 |
| AS57005 | PE Homich Nataliya G. | Unclassified | IPv4 | 86 |
| AS44884 | Regional Online Systems Ltd. | Unclassified | IPv4 | 68 |
| AS44710 | TRK Sirius LTD | Unclassified | IPv4 | 63 |
| AS31113 | Artkomm LLC | Unclassified | IPv4 | 61 |
| AS52213 | LLC DONETSK FIBER-OPTICAL NETWORK | Unclassified | IPv4 | 32 |
| AS211692 | Level-Donetsk Ltd. | Unclassified | IPv4 | 26 |
Adjacency
Adjacent networks
Every AS seen directly next to AS12773 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS201776 | Miranda-Media Ltd | Unclassified | IPv4 | 918 |
| AS39089 | STATE UNITARY ENTERPRISE OF THE DONETSK PEOPLE'S REPUBLIC "UGLETELECOM" | Unclassified | IPv4 | 499 |
| AS34786 | OOO NPO Intermet | Unclassified | IPv4 | 367 |
| AS47809 | Private Enterprise Matsak Ivan Anatolievich | Unclassified | IPv4 | 345 |
| AS48084 | Uzhnie Magistraljnie Linii Svyazi LLC | Unclassified | IPv4 | 314 |
| AS206810 | GUP DNR "UGLETELECOM" | Unclassified | IPv4 | 283 |
| AS44539 | Redi LLC | Unclassified | IPv4 | 265 |
| AS60839 | Vid Media Ltd. | Unclassified | IPv4 | 256 |
| AS25141 | Teleradiocompany Soniko-Svyaz Ltd | Unclassified | IPv4 | 248 |
| AS49757 | Igor Uspenskyy | Unclassified | IPv4 | 244 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.