Frequent 502/503 Errors and Unstable Workspace in AP Region (n8n Cloud)

Questions
1

Hi n8n Support Team,
I am experiencing frequent 502 and 503 errors on my n8n Cloud workspace. Today, the workspace has often been unreachable or extremely unstable.
Issue details:

  • The editor and workflows regularly show 502/503 errors or a “Workspace offline / restarting” message.

  • Sometimes the workspace loads after a refresh or restart, but it usually fails again after a few minutes.

  • Even very small workflows (just a few nodes) can trigger 503 errors or “Connection lost” in the editor.

  • This happens at different times of the day and across different browsers and networks, so it does not seem to be a local network issue.

Impact:

  • I cannot reliably access the editor to edit or test workflows.

  • Scheduled workflows sometimes do not execute as expected.

  • This instability is affecting our production/business automations.

Environment:

  • Region: AP

  • Hosting: n8n Cloud

  • Workspace: funnow

  • Plan: Pro

Could you please:

  1. Check if there are any ongoing issues or incidents affecting AP region workspaces?

  2. Review my workspace instance for crash loops, resource limits, or other errors that might be causing these repeated 502/503 responses?

  3. Let me know if there is any temporary mitigation or configuration change I can apply from my side?

I have attached screenshots of the 502/503 error pages and “Workspace offline / Connection lost” messages for your reference.

image
image247×360 42.5 KB

image
image377×233 6.17 KB

(By the way, I did attempt to restart the workspace and upgrade the version to 1.122.4, and the problem is still there.)

Thank you for your help.
Best regards,

2

Hi

If you haven’t already, please report this to the support team [email protected] - I will take a look tomorrow also [UK hours, 3rd December]

3

I took a look at this - please be sure to open a support request with the team.

I can see many OOM instances on your env that will need further investigation.
Let me know when the support request is raised and we can discuss further there.

Thanks,
Jon

4

I’m having the same issue. did you find any solution

5

Hello

If you have this issue - please submit a support request for the team to take a look - you can do so by sending an email to [email protected]

Many thanks,
Jon

6

Did they find a solution to this? I am experiencing the same issue, also wrote support with no response as of yet.