Observed topology
AS199961 MTLS-AS Multitelesystems LLC
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS199961: 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 |
|---|---|---|---|---|
| AS48084 | Uzhnie Magistraljnie Linii Svyazi LLC | Unclassified | IPv4 IPv6 | 144 |
| AS43201 | Telematika LLC | Unclassified | IPv4 | 36 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 27 |
| AS24482 | SG.GS | Hosting | IPv4 | 3 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 3 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 3 |
| AS56655 | Gigahost AS | Unclassified | IPv4 | 3 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 3 |
Transit
Downstream networks
Networks for which AS199961 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS197129 | FOP Kopilov Sergey | Unclassified | IPv4 | 930 |
| AS49444 | Lutacom LLC | Unclassified | IPv4 | 681 |
| AS47550 | Bratinov Oleg Vyacheslavovich | Unclassified | IPv4 | 140 |
| AS39558 | IP Resurs Ltd. | Unclassified | IPv4 | 126 |
| AS201414 | OOO "DELTA-ELECTRONICS" | Unclassified | IPv4 | 126 |
| AS209720 | LLC "Multinet-Lugan" | Unclassified | IPv4 | 126 |
| AS50015 | Aleksandr Butenko | Unclassified | IPv4 | 119 |
| AS215882 | HiperLine LTD | Unclassified | IPv4 | 65 |
| AS43972 | Sergey Olenich | Unclassified | IPv4 | 20 |
| AS202619 | Dovecom LLC | Unclassified | IPv4 IPv6 | 15 |
Adjacency
Adjacent networks
Every AS seen directly next to AS199961 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS48084 | Uzhnie Magistraljnie Linii Svyazi LLC | Unclassified | IPv4 IPv6 | 1,605 |
| AS197129 | FOP Kopilov Sergey | Unclassified | IPv4 | 930 |
| AS49444 | Lutacom LLC | Unclassified | IPv4 | 681 |
| AS43201 | Telematika LLC | Unclassified | IPv4 | 431 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 379 |
| AS47550 | Bratinov Oleg Vyacheslavovich | Unclassified | IPv4 | 140 |
| AS39558 | IP Resurs Ltd. | Unclassified | IPv4 | 126 |
| AS201414 | OOO "DELTA-ELECTRONICS" | Unclassified | IPv4 | 126 |
| AS209720 | LLC "Multinet-Lugan" | Unclassified | IPv4 | 126 |
| AS50015 | Aleksandr Butenko | Unclassified | IPv4 | 119 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.