Observed topology
AS50928 SYNTSIB-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS50928: 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 |
|---|---|---|---|---|
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 2,640 |
Transit
Downstream networks
Networks for which AS50928 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS39785 | Axioma, LLC | Residential | IPv4 | 1,140 |
| AS41311 | Center of Connection, Informatic and Telecommunication LLC | Unclassified | IPv4 | 318 |
| AS29071 | Sputnikovaya svyaz LLC | Unclassified | IPv4 | 221 |
| AS47117 | Sibline Ltd. | Unclassified | IPv4 | 124 |
| AS51067 | Sibinfosoft LLC | Unclassified | IPv4 IPv6 | 100 |
| AS48316 | Regional State Institution "Regional Center of automated information resource of Tomsk Region" | Unclassified | IPv4 | 79 |
| AS5567 | National Research Tomsk Polytechnic University | Education | IPv4 | 66 |
| AS8279 | Novaya Strategia Ltd. | Unclassified | IPv4 | 61 |
| AS9078 | Sibirskie Innovacionnye Sistemy Ltd | Unclassified | IPv4 | 61 |
| AS42048 | Siberian Federal University | Unclassified | IPv4 | 61 |
Adjacency
Adjacent networks
Every AS seen directly next to AS50928 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 5,637 |
| AS39785 | Axioma, LLC | Residential | IPv4 | 1,609 |
| AS41311 | Center of Connection, Informatic and Telecommunication LLC | Unclassified | IPv4 | 318 |
| AS29071 | Sputnikovaya svyaz LLC | Unclassified | IPv4 | 221 |
| AS47117 | Sibline Ltd. | Unclassified | IPv4 | 124 |
| AS51067 | Sibinfosoft LLC | Unclassified | IPv4 IPv6 | 100 |
| AS48316 | Regional State Institution "Regional Center of automated information resource of Tomsk Region" | Unclassified | IPv4 | 79 |
| AS5567 | National Research Tomsk Polytechnic University | Education | IPv4 | 66 |
| AS8279 | Novaya Strategia Ltd. | Unclassified | IPv4 | 61 |
| AS9078 | Sibirskie Innovacionnye Sistemy Ltd | Unclassified | IPv4 | 61 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-19 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.