Unable to login: Workspace Offline Issue (503)

Questions
1

Describe the problem/error/question

I am unable to login due to a Workspace offline (503) error on our n8n cloud instance. We are currently on the Pro plan. We have done everything we can from our side from deleting multiple workflows to trimming executions and logs. Is there anything that can be done about this? This has been ongoing for past few hours. No executions and its im on currently on the Pro plan. No community nodes on, no workflows eating up memory. No logs being saved.

Grateful for any support/help - information if there is any n8n on Cloudflare outage ASAP with response time.

Not sure if n8n on Cloudflare is an issue. Simply frustrating, logging tickets only get me a support email bot response wit amagic link that doesnt work.

What is the error message (if any)?

Workspace offline (503) and Running version [email protected]

Please share your workflow

No commun

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
1 Like
2

Running version [email protected]

3

Hi @kartik.iyengar

Short and honest answer: this is almost certainly a n8n Cloud–side issue, not something you can fix from your end.

A 503 “Workspace offline” on n8n Cloud means your workspace container isn’t coming up (or is being restarted) at the platform level. Deleting workflows, trimming executions, or checking community nodes won’t help once the workspace itself is offline.

At this point, the only real actions are:

  • Open a Cloud support ticket (which you already did)
  • Ask explicitly for workspace restart / redeploy by the Cloud team
  • Check status.n8n.io to confirm whether there’s an ongoing incident (Cloudflare or internal)

Unfortunately, there’s no self-service recovery for this scenario on Cloud plans. It’s frustrating, but resolution requires intervention from n8n Cloud support.

4

Same issue for us on v2.4.8, definitely not a stable release.

Some workflows hang the instance. The workflow execution continues (until cancelled) but the site crashes and returns 503’s until the instance is restarted.