Observed topology
AS50923 METRO-SET-AS Metroset Autonomous System
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS50923: 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 |
|---|---|---|---|---|
| AS31500 | Global Network Management Inc | Unclassified | IPv4 IPv6 | 97 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 61 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 41 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 36 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 | 30 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 IPv6 | 28 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 22 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 17 |
| AS51028 | Zummer LLC | Unclassified | IPv4 | 14 |
| AS25091 | IP-Max SA | Unclassified | IPv4 | 10 |
Transit
Downstream networks
Networks for which AS50923 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS48873 | LLC "Proxicom" | Unclassified | IPv4 | 514 |
| AS39735 | "Permtelecom" Ltd | Unclassified | IPv4 | 286 |
| AS44627 | Link LLC | Unclassified | IPv4 | 120 |
| AS57363 | CDNvideo LLC | Hosting | IPv4 | 60 |
| AS15493 | "Russian company" LLC | Unclassified | IPv4 IPv6 | 48 |
| AS202136 | "A-Siti" Limited Liability Company | Unclassified | IPv4 IPv6 | 43 |
| AS207353 | Ruform LLC | Hosting | IPv4 | 2 |
Adjacency
Adjacent networks
Every AS seen directly next to AS50923 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS48873 | LLC "Proxicom" | Unclassified | IPv4 | 514 |
| AS39735 | "Permtelecom" Ltd | Unclassified | IPv4 | 286 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 IPv6 | 230 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 IPv6 | 203 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 201 |
| AS15493 | "Russian company" LLC | Unclassified | IPv4 IPv6 | 197 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 196 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 153 |
| AS44627 | Link LLC | Unclassified | IPv4 | 120 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 119 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-18 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.