I’m reaching out here because my production workspace has been down for over 5 hours and I’m stuck in a 503 Workspace Offline / Restarting loop.
The issue: The instance briefly comes online for about 5 seconds (I can see the dashboard) and then immediately crashes back to a 503 error.
What I’ve done:
Subscription is active and verified.
Tried accessing via Admin Magic Link (same result).
Already opened a support ticket
Support AI mentioned it was escalated to engineering, but I haven’t received a human update yet and my business operations are completely halted.
Request: Could a moderator or staff member please check the status of my instance? It seems like a backend crash loop or a database lock after a recent update.
This behaviour usually means the workspace process is crashing during startup. It briefly comes online, then fails to finish initializing and gets restarted again, which creates the 503 loop you’re seeing.
On n8n Cloud there isn’t a user-side fix for this, because the instance dies before you can change anything. This is typically a backend issue such as a failed migration or database problem and needs intervention from the n8n Cloud team.
As a temporary workaround, the only option is to run critical flows in a separate/self-hosted instance if you have one. For the broken cloud workspace itself, the quickest path is to continue with your open support ticket and provide your workspace ID and the time the loop started so engineering can repair it.