🚨 Workspace offline (503) – n8n Cloud instance crashing repeatedly (URGENT)

Hi everyone,

I need urgent help with my n8n Cloud workspace. Since Friday, my instance has been stuck in a loop of “Workspace offline (503)”, and I still haven’t received a response from support.

Workspace details

  • Workspace URL: lokl.app.n8n.cloud

  • Account email: [email protected]

  • Issue started: Friday [28/11/2025]

What is happening

  • The workspace keeps showing “Workspace offline (503)”.

  • I can temporarily restore access by restarting the instance from the Cloud Admin Dashboard, but it only works for 2–5 minutes before going offline again.

  • No workflows run at all — my entire automation system is down.

  • This issue is repeating every time, which suggests a crash loop or internal failure.

What I have already tried

  • Logging into the Cloud Admin Dashboard using “Send magic link”.

  • Restarting the instance multiple times.

  • Trying different browsers, disabling VPN/proxies, incognito mode, etc.

  • Contacted support by email — no human response since Friday, only automated replies.

Impact

This downtime has my business completely stalled.
All critical workflows depend on this n8n Cloud instance.

Request

Could someone from the n8n team escalate this to an engineer and check why the workspace keeps entering a crash/restart loop?

I’m happy to provide logs, screenshots, or anything else needed.
Here is the error I see every time:

Thank you in advance — I really need help resolving this.

— Jhon

Hey Jhon! That crash loop sounds like a resource issue or a corrupted workflow causing the instance to fail on startup. Since you are on N8n Cloud, only their support team can access backend logs and fix this. Keep pushing on your support ticket and reply to the automated emails with “URGENT” in the subject to escalate it. Meanwhile, check if you recently added any workflows with heavy loops, large data processing, or community nodes that might be crashing on execution. Hopefully support gets back to you soon—this definitely needs engineer attention.

anyone having luck contact support. It has been days with no reply?

No but i got the exact same issue. It’s been since yesterday and no reply.