@leinir: Who is responsible for the name server? Who can help me?

In T9768#161941, @ronaldv wrote:

@leinir: Who is responsible for the name server? Who can help me?

That, i expect, would be the sysadmin team... which doesn't have a catch-all account that i can find, but perhaps @bshah or @bcooksley might be able to help there? :)

KDE Sysadmin doesn't run the backend server, that is an Incapsula message informing you that it can't talk to the backend server (which @ronaldv runs).

We enabled Incapsula for this because you run the KDE Store out of DigitalOcean and the Russian Government are playing whack-a-mole with Telegram, taking out hunks of DigitalOcean and AWS in the process. This leads to us (KDE Sysadmin) getting service outage complaints from our Russian users.

The Incapsula Homepage is also not available. So it could be the Incapsula service.

@bcooksley Could you please inform Incapsula about the problem?

It works fine for me here - could you try with IPv4 only please?

Strange. With my smartphone here in germany I can reach the page store.kde.org and incapsula too. When I try it from a DigitalOcean server, I also get an error. Do you think there is a solution to the problem?

And the problem with the unreachable URL is a problem on the part of Incapsula. Should not they be informed?

Their engineers will need detailed information to investigate the issue. Please provide the screenshots from the DigitalOcean as well as your local system.
Also, please test IPv6 vs. IPv4, as that may be the cause of the breakage (ie. that Incapsula proxy has lost the ability to talk IPv4)

Local output:

wget -O - store.kde.org | grep "your Plasma Desktop"
--2018-09-27 14:51:13-- http://store.kde.org/
Resolving store.kde.org (store.kde.org)... 2a02:e980:fc::3e, 107.154.38.62
Connecting to store.kde.org (store.kde.org)|2a02:e980:fc::3e|:80... connected.
HTTP request sent, awaiting response... 503 Service Unavailable
2018-09-27 14:51:28 ERROR 503: Service Unavailable.

Your DigitalOcean system should have IPv4 connectivity for testing purposes?

DigitalOcean works. Was my mistake.

Okay. If you could please provide the IPv6 address that you resolve store.kde.org to then i'll report that to them.
(I'm curious how you normally access many sites if your ISP is IPv6 only though)

My ISP Unitymedia uses Dual Stack / Dual Stack Litet and maps my IPv6 address with an IPv4 address. This looks from the outside as if I had an IPv4 address. So do not need a IPv6 address for store.kde.org

I see. If you could provide the IP addresses store.kde.org resolves to for you and confirm that the issue still occurs (and provide a new screenshot if the details have changed) i'll go ahead and report that to them.

Problem is fixed. I can see the site again.