Skip to main content

AS30766

GGEWNET-AS

Dammstrasse 68

Registry

Authoritative registration data

AS number
30766
Name
GGEWNET-AS
Organisation
Dammstrasse 68
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

1

Total announced

13

Announced prefixes

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

Prefixes announced by AS30766
217.113.176.0/20 IPv4 /20 RPKI valid
31.99.208.0/21 IPv4 /21 not checked
185.101.172.0/22 IPv4 /22 RPKI valid
213.232.100.0/22 IPv4 /22 not checked
86.62.8.0/22 IPv4 /22 RPKI valid
91.132.220.0/22 IPv4 /22 not checked
178.132.68.0/23 IPv4 /23 not checked
45.148.218.0/23 IPv4 /23 RPKI valid
192.109.71.0/24 IPv4 /24 not checked
192.109.74.0/24 IPv4 /24 RPKI valid
192.109.77.0/24 IPv4 /24 RPKI valid
192.109.79.0/24 IPv4 /24 RPKI valid
2a05:e2c0::/29 IPv6 /29 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 AS30766
Address families
DE-CIX Dusseldorf: DE-CIX Dusseldorf Peering LAN 10,000 Mbps IPv4 · IPv6
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 200,000 Mbps IPv4 · IPv6
DE-CIX Hamburg: DE-CIX Hamburg Peering LAN 10,000 Mbps IPv4 · IPv6
DE-CIX Munich: DE-CIX Munich Peering LAN 10,000 Mbps IPv4 · IPv6
ERA-IX Frankfurt 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 AS30766 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

25 networks seen before AS30766 in AS paths

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS30766 in AS paths

Observed downstreams
Families
AS201155 EMBEDD-AS 184 851
v4 v6
AS207776 ednt 139 488
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

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