Observed topology
AS50113 SuperServersDatacenter FIRST SERVER LIMITED
Unclassified DROP-listed space RIPE Enterprise
Transit
Upstream networks
Networks observed carrying traffic for AS50113: 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 |
|---|---|---|---|---|
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 848 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 180 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv6 | 177 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 130 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 86 |
| AS56630 | Melbikomas UAB | Hosting | IPv4 | 84 |
| AS202984 | Chernyshov Aleksandr Aleksandrovich | Unclassified | IPv4 | 47 |
| AS29076 | Citytelecom LLC | Hosting | IPv4 | 39 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 35 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 28 |
Transit
Downstream networks
Networks for which AS50113 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS204997 | FIRST SERVER LIMITED | Unclassified | IPv4 IPv6 | 4,764 |
| AS207569 | IHOR HOSTING LTD | Unclassified | IPv4 | 524 |
| AS205090 | FIRST SERVER LIMITED | Unclassified | IPv4 | 320 |
| AS204339 | FIRST SERVER LIMITED | Unclassified | IPv4 | 137 |
| AS205125 | FZCO | Unclassified | IPv6 | 108 |
| AS35196 | FIRST SERVER LIMITED | Hosting | IPv4 | 23 |
| AS200740 | FIRST SERVER LIMITED | Unclassified | IPv4 | 18 |
| AS202306 | HOSTGLOBAL.PLUS LTD | Hosting | IPv6 | 2 |
Adjacency
Adjacent networks
Every AS seen directly next to AS50113 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS204997 | FIRST SERVER LIMITED | Unclassified | IPv4 IPv6 | 4,764 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 4,400 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 930 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 560 |
| AS207569 | IHOR HOSTING LTD | Unclassified | IPv4 | 524 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 IPv6 | 356 |
| AS205090 | FIRST SERVER LIMITED | Unclassified | IPv4 | 320 |
| AS29076 | Citytelecom LLC | Hosting | IPv4 | 250 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 247 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 227 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-05 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 73.57M 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.