Workspace offline (503) - what to do?

Questions
1 
Hey. I've seen that this problem has occurred frequently before. However, I haven't been able to find a solution. My cloud instance has been unreachable for about 20 hours, even though everything seems to be fine in the admin backend. I've already sent emails to help@ and support@ but only received a response from the AI ​​bot. Does anyone have any idea how I can get help quickly?

BR Jan

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

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:
2

Thanks for the update @Jan_Ko , since n8n Cloud is currently up (no outage reported on status monitoring services) it’s likely something specific to your workspace or environment.

To help narrow it down, we’ll need a bit more info because right now there aren’t enough details for the community to diagnose what’s happening on your end.

Here’s what to try/check next:

  1. Verify basic connectivity to your workspace URL
    Even if the global Cloud service is up, your specific domain (e.g., yourname.app.n8n.cloud) could be having DNS or routing issues. Try:

    • Opening the workspace URL directly.

    • Running a basic ping or nslookup from your terminal to confirm it resolves.

  2. Check the instance health endpoints
    n8n exposes /healthz and /healthz/readiness endpoints that return HTTP status codes indicating whether the service is reachable and ready. These don’t require credentials and are useful for quick checks:

    https://yourworkspace.app.n8n.cloud/healthz 

https://yourworkspace.app.n8n.cloud/healthz/readiness

    A 200 response means the instance is up and accepting traffic.

  3. Clear local cache / try different network or device
    Sometimes Cloud pages fail to load due to local caching, ISP issues, or browser state, trying another network or device can rule that out.

  4. Share specific errors
    Right now your post doesn’t include:

    • The exact HTTP error you see (e.g., timeout, 502/503, blank page, etc.)

    • What /healthz returns

    • Your workspace URL
      Without that, it’s hard for folks here to guess the cause beyond general troubleshooting.

If you can update your thread with those three pieces (error type, healthz output, and workspace URL), the community will be much better positioned to help.