Observed topology
AS51776 SPORTRADAR-AS Sportradar AG
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS51776: 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 |
|---|---|---|---|---|
| AS32787 | Akamai Technologies, Inc. | Hosting | IPv4 | 152 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 135 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 79 |
| AS8447 | A1 Telekom Austria AG | Residential | IPv4 | 71 |
| AS8220 | COLT Technology Services Group Limited | Hosting | IPv4 | 32 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 27 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 12 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 | 5 |
| AS6797 | GlobalConnect AB | Unclassified | IPv4 | 4 |
| AS8551 | Bezeq International Ltd. | Unclassified | IPv4 | 4 |
Transit
Downstream networks
Networks for which AS51776 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS60385 | Sportradar AG | Unclassified | IPv4 | 137 |
Adjacency
Adjacent networks
Every AS seen directly next to AS51776 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS32787 | Akamai Technologies, Inc. | Hosting | IPv4 | 276 |
| AS60385 | Sportradar AG | Unclassified | IPv4 | 137 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 135 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 79 |
| AS8447 | A1 Telekom Austria AG | Residential | IPv4 | 71 |
| AS8220 | COLT Technology Services Group Limited | Hosting | IPv4 | 32 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 31 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 15 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 | 6 |
| AS6797 | GlobalConnect AB | Unclassified | IPv4 | 5 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.