Skip to main content

AS8763

DENIC-AS

Theodor-Stern-Kai 1

Registry

Authoritative registration data

AS number
8763
Name
DENIC-AS
Organisation
Theodor-Stern-Kai 1
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS8763
81.91.160.0/20 IPv4 /20 not checked
81.91.170.0/24 IPv4 /24 not checked
81.91.172.0/24 IPv4 /24 not checked
81.91.173.0/24 IPv4 /24 not checked
2a02:568::/32 IPv6 /32 not checked

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 AS8763
Address families
AMS-IX 10,000 Mbps IPv4 · IPv6
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 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 AS8763 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

37 networks seen before AS8763 in AS paths

No rows match “”.

Showing – of

Observed downstreams

5 networks seen after AS8763 in AS paths

Observed downstreams
Families
AS31529 DENIC-ANYCAST-AS 468 1,046
v4 v6
AS12136 ASN12136 221 885
v4 v6
AS23600 GDNSKR-KR-KR 303 506
v4 v6
AS42385 RIPN-RU 261 336
v4 v6
AS35052 AS_AT_TLD_SERVICES 52 80
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

43 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.