[SOLVED] 2021-10-29 Cloud.squidex.io Timeout

Maintenance
1

I have…

I’m submitting a…

  • [ ] Regression (a behavior that stopped working in a new release)
  • [ ] Bug report
  • [X] Performance issue
  • [ ] Documentation issue or request

Current behavior

From yesterday morning at 11.30AM we have a random timeout to reach this address https://cloud.squidex.io/api/

Could you check it if everything is ok?

Thanks!

Expected behavior

Minimal reproduction of the problem

Environment

  • [ ] Self hosted with docker
  • [ ] Self hosted with IIS
  • [ ] Self hosted with other version
  • [X] Cloud version

Version: [VERSION]

Browser:

  • [X ] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [X] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge

Others:

2

Squidex
Squidex1147×477 13.7 KB

Maybe a timeout RTO on TPC SYN connection?

3

Hi,

I have not realized anything. I have 2 monitoring systems which have not triggered an alarm.

4

Seems it solved from few minutes…
Thanks!

5

hello,

this website has also been unreachable for us for a while, our services (hosted in AWS) are still unable to resolve the cloud.squidex.io hostname. Looks like it isn’t just us:

image
image842×711 96 KB

are you still looking into it @Sebastian?

regards,
Piotr

6

Also us have the same problem. @Sebastian could you check it?
Thanks!

7

can i ask how we are looking with the error? The client has now raised this as they are unable to use the cloud UI - and our services still unable to reach the API.

8

@Sebastian It seems to https://cloud.squidex.io/ is still down and due to that all our Production sites are not working. Could you plz check?

9

I am very sorry for this downtime. The problem was an issue with the DNS or more specifically with the domain.

A few weeks ago the credit card was blocked and a new credit card has been issued and for whatever reason I have not received a notification from the domain provider.

Today the site was not available, because the account has been blocked until the domain was payed. I have received the warnings very late, because it seems that the monitoring tool has very long cache duration of the DNS entry. I guess some of you might have noticed it earlier than me.

10

thanks for the update. We are still having issues with reaching the host - do you have a rough idea about when it might be fixed?

11

It works for me. So I guess it is your DNS provider or DNS hierarchy. Perhaps you can force a flush of the DNS cache.

12

You can use websites such as https://www.whatsmydns.net/#A/cloud.squidex.io to keep track of where the propagation has reached so far.

1 Like