Observed topology
AS50020 RACCOM-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS50020: 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 |
|---|---|---|---|---|
| AS9002 | RETN Limited | Unclassified | IPv4 | 72 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 39 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 24 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 9 |
| AS8262 | Evolink EAD | Unclassified | IPv4 | 6 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 6 |
| AS6797 | GlobalConnect AB | Unclassified | IPv4 | 3 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 3 |
| AS24482 | SG.GS | Hosting | IPv4 | 3 |
| AS34019 | Hivane Association | Unclassified | IPv4 | 3 |
Transit
Downstream networks
Networks for which AS50020 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS29171 | N.C. NET-CONNECT (CY) LTD | Unclassified | IPv4 | 120 |
| AS57622 | AUTO PLUS BULGARIA JSC | Unclassified | IPv4 | 60 |
| AS209841 | MANAGEMENT SERVICES CORPORATION EAD | Unclassified | IPv4 | 60 |
| AS210299 | ART-BUILD-UP | Unclassified | IPv4 | 60 |
| AS202864 | COMAC MEDICAL | Unclassified | IPv4 | 10 |
| AS203578 | Euromaster Import Export Ltd | Unclassified | IPv4 | 9 |
| AS59746 | ABRITES LTD. | Unclassified | IPv4 | 6 |
Adjacency
Adjacent networks
Every AS seen directly next to AS50020 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9002 | RETN Limited | Unclassified | IPv4 | 223 |
| AS29171 | N.C. NET-CONNECT (CY) LTD | Unclassified | IPv4 | 120 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 83 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 64 |
| AS57622 | AUTO PLUS BULGARIA JSC | Unclassified | IPv4 | 60 |
| AS209841 | MANAGEMENT SERVICES CORPORATION EAD | Unclassified | IPv4 | 60 |
| AS210299 | ART-BUILD-UP | Unclassified | IPv4 | 60 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 24 |
| AS8262 | Evolink EAD | Unclassified | IPv4 | 16 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 16 |
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.