[URGENT] WeWeb Service is down - 503 ERROR

Ask us anything
21

Hi @Raphael, thank you for the update.

One of our clients has had a spike in intermittent outages (a few minutes) over the last several weeks. Will this fix likely also address that?

CleanShot 2024-02-24 at 14.15.58@2x
CleanShot 2024-02-24 at 14.15.58@2x2016Ɨ400 37.9 KB

22

Can confirm. Same here, I observe apps having small outages all week on betterstack.

24

We still had one instance of 503 today February 26th around 5:42 PM GMT

503
5031899Ɨ944 79.2 KB

EDIT: It lasted for about two minutes and it affected everyone using the Website at that time.

25

Hi there, has been going up & down again in the last hour. Hope you guys are on it; I also alerted support.

Thanks!

26

hi WeWeb team, and @Raphael @Joyce

I am sure everyone would like to know if you can you please share if there is an underlying issue + cause that is being investigated and can you please share if there is a plan to counter this ?

Getting worried hereā€¦

Regards

27

@Marc

28

Hi everyone, thank you for your patience with us on this one, really appreciate it.

Hereā€™s a little more info on whatā€™s going on:

  • our infrastructure was overloaded by an incredibly high number of API calls
  • it doesnā€™t appear to be malicious but we are working on identifying which apps are causing this and on updating our infra to fix the issue permanently
  • in the meantime, weā€™ve found a temporary fix that should prevent any further downtime

Please continue to tell us if you notice anything unusual on your live apps.

We are monitoring the topic closely and will continue to keep you posted.

Best,
Joyce

29

Thank you, @Joyce!

30

All my sites just went down with the 503 error, tried different browsers, incognito, still same issue, canā€™t get anything to load, just started today 3/13 - 11AM

31

Same for me. For at least an hour it disconnects every several minutesā€¦

32

My sites just came back on but it was intermittent earlier for me before it went out completely

33

Hello :wave:

Quick update on this topic: the instability has been fixed and should not happen again. It was due to an internal misconfiguration on our new infrastructure.