Skip to main content

AS51776

SPORTRADAR-AS

Sportradar AG

Registry

Authoritative registration data

AS number
51776
Name
SPORTRADAR-AS
Organisation
Sportradar AG
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

0

Total announced

9

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS51776
185.132.128.0/24 IPv4 /24 not checked
185.188.52.0/24 IPv4 /24 RPKI valid
185.188.53.0/24 IPv4 /24 RPKI valid
185.188.54.0/24 IPv4 /24 RPKI valid
185.188.55.0/24 IPv4 /24 RPKI valid
87.238.137.0/24 IPv4 /24 RPKI valid
87.238.141.0/24 IPv4 /24 RPKI valid
87.238.142.0/24 IPv4 /24 RPKI valid
91.199.175.0/24 IPv4 /24 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS51776
Address families
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 10,000 Mbps IPv4 · IPv6
VIX 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS51776 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

24 networks seen before AS51776 in AS paths

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS51776 in AS paths

Observed downstreams
Families
AS60385 ES_OPTIMA 138 475
v4

No rows match “”.

Showing – of

Uncertain adjacencies

39 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.