# CRITICAL BUG - Entire Cloud instance crashed - Cant reach n8n support

**URL:** <https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056>\
**Category:** Feedback\
**Tags:** error-trigger\
**Created:** [November 10, 2025, 12:09pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056 "2025-11-10T12:09:23Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![mads](https://avatars.discourse-cdn.com/v4/letter/m/ec9cab/32.png) [@mads](https://community.n8n.io/u/mads)\
**Post date:** [November 10, 2025, 12:09pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/1 "2025-11-10T12:09:23Z")

</div>

Hello as the subject states, i have found what i think is a bug… out entire instance just freezes when i log in, and i cannot use the instance, i think it might be an infinite loop or something.. i have tried to reach n8n, but the response is just an ai support thats absolutely useless…

**What i did:**

1. Edited an agent nodes system instructions.
2. While the node editor was open i clicked version history.
3. It prompted if i wanted to save.
4. I clicked save.
5. The version history right panel opened.
6. The panel displayed the current version as if there was an error in the version.
7. Then the entire page became non reactive.

Now every time i try to load our domain it just freezes and throws a browser error:  
Error code: RESULT\_CODE\_HUNG

I have tried clearing cache.  
Restart the instance  
Relog

I have no idea what has happend, and our entire infrastructure that depends on n8n is now down, it seems the flows actually runs, but i cannot use the instance…

Has anyone tried this or know how to fix

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/a/6/a65795d307e69d35d1be36c0767cfef9769bfcab.png)

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/0/9/09a829bcf4a0d7ef9f3e9de0fbce9d648b4f0c59.png)

---

<div class="post-metadata">

**Author:** ![cillianbc](https://avatars.discourse-cdn.com/v4/letter/c/58956e/32.png) [@cillianbc](https://community.n8n.io/u/cillianbc)\
**Post date:** [November 10, 2025, 12:12pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/2 "2025-11-10T12:12:31Z")

</div>

Exact same issue, last 30 min

---

<div class="post-metadata">

**Author:** ![Giorgio\_Messina](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/giorgio_messina/32/136339_2.png) [@Giorgio\_Messina](https://community.n8n.io/u/Giorgio_Messina)\
**Post date:** [November 10, 2025, 12:21pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/3 "2025-11-10T12:21:18Z")

</div>

Hi, how did you solve it?  
I have the same problem

---

<div class="post-metadata">

**Author:** ![RCheesley](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/rcheesley/32/17571_2.png) [@RCheesley](https://community.n8n.io/u/RCheesley)\
**Post date:** [November 10, 2025, 12:26pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/4 "2025-11-10T12:26:48Z")

</div>

Same problem here, as well. Can’t access anything in my instance, pages are timing out and the browser is killing them as they’re becoming unresponsive.

---

<div class="post-metadata">

**Author:** ![MODESTE\_KASSEM](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/modeste_kassem/32/122709_2.png) [@MODESTE\_KASSEM](https://community.n8n.io/u/MODESTE_KASSEM)\
**Post date:** [November 10, 2025, 12:28pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/5 "2025-11-10T12:28:12Z")

</div>

Same issue

---

<div class="post-metadata">

**Author:** ![mads](https://avatars.discourse-cdn.com/v4/letter/m/ec9cab/32.png) [@mads](https://community.n8n.io/u/mads)\
**Post date:** [November 10, 2025, 12:33pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/6 "2025-11-10T12:33:27Z")

</div>

No solution yet - still unresponsive.

---

<div class="post-metadata">

**Author:** ![Chris\_Northcote](https://avatars.discourse-cdn.com/v4/letter/c/e36b37/32.png) [@Chris\_Northcote](https://community.n8n.io/u/Chris_Northcote)\
**Post date:** [November 10, 2025, 12:34pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/7 "2025-11-10T12:34:43Z")

</div>

Same here, anyone receive anything from support?

---

<div class="post-metadata">

**Author:** ![mads](https://avatars.discourse-cdn.com/v4/letter/m/ec9cab/32.png) [@mads](https://community.n8n.io/u/mads)\
**Post date:** [November 10, 2025, 12:39pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/8 "2025-11-10T12:39:46Z")

</div>

Nothing yet.

---

<div class="post-metadata">

**Author:** ![mads](https://avatars.discourse-cdn.com/v4/letter/m/ec9cab/32.png) [@mads](https://community.n8n.io/u/mads)\
**Post date:** [November 10, 2025, 12:41pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/9 "2025-11-10T12:41:03Z")

</div>

Same issue.

It seems the pages are also using a lot more memory than usual.

---

<div class="post-metadata">

**Author:** ![Lukas.Va](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/lukas.va/32/130117_2.png) [@Lukas.Va](https://community.n8n.io/u/Lukas.Va)\
**Post date:** [November 10, 2025, 12:41pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/10 "2025-11-10T12:41:16Z")

</div>

End up discovering this after writing the email to the support. Will follow the thread. I’m glad it was not me accidentally creating a sort of infinite loop by splitting workflows. 🙂

A perfect case to request a workstation upgrade to the one with max ram hehe.

---

<div class="post-metadata">

**Author:** ![rutgervanhagen](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/rutgervanhagen/32/51675_2.png) [@rutgervanhagen](https://community.n8n.io/u/rutgervanhagen)\
**Post date:** [November 10, 2025, 12:46pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/11 "2025-11-10T12:46:17Z")

</div>

Same here, please fix this quick!

---

<div class="post-metadata">

**Author:** ![abhigo](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/abhigo/32/136350_2.png) [@abhigo](https://community.n8n.io/u/abhigo)\
**Post date:** [November 10, 2025, 12:57pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/12 "2025-11-10T12:57:43Z")

</div>

Facing same issue. Need a quick fix. All work is on halt.

---

<div class="post-metadata">

**Author:** ![skpwrz](https://avatars.discourse-cdn.com/v4/letter/s/b9e5f3/32.png) [@skpwrz](https://community.n8n.io/u/skpwrz)\
**Post date:** [November 10, 2025, 1:10pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/13 "2025-11-10T13:10:00Z")

</div>

Is there a status page anywhere, or decent support which is not just an AI bot?

For a paid cloud service, this is pretty bad.

---

<div class="post-metadata">

**Author:** ![Giorgio\_Messina](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/giorgio_messina/32/136339_2.png) [@Giorgio\_Messina](https://community.n8n.io/u/Giorgio_Messina)\
**Post date:** [November 10, 2025, 1:10pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/14 "2025-11-10T13:10:32Z")

</div>

Any news? I am still blocked

---

<div class="post-metadata">

**Author:** ![sfx](https://avatars.discourse-cdn.com/v4/letter/s/c37758/32.png) [@sfx](https://community.n8n.io/u/sfx)\
**Post date:** [November 10, 2025, 1:12pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/15 "2025-11-10T13:12:00Z")

</div>

same issue

---

<div class="post-metadata">

**Author:** ![RCheesley](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/rcheesley/32/17571_2.png) [@RCheesley](https://community.n8n.io/u/RCheesley)\
**Post date:** [November 10, 2025, 1:12pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/16 "2025-11-10T13:12:35Z")

</div>

I found this: [https://status.n8n.cloud/](https://status.n8n.cloud/) linked to from an archived repo on their GitHub but no idea if they actually maintain it actively.

---

<div class="post-metadata">

**Author:** ![rutgervanhagen](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/rutgervanhagen/32/51675_2.png) [@rutgervanhagen](https://community.n8n.io/u/rutgervanhagen)\
**Post date:** [November 10, 2025, 1:15pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/17 "2025-11-10T13:15:09Z")

</div>

Looks like they deployed a new update which crashes the browser?

---

<div class="post-metadata">

**Author:** ![mads](https://avatars.discourse-cdn.com/v4/letter/m/ec9cab/32.png) [@mads](https://community.n8n.io/u/mads)\
**Post date:** [November 10, 2025, 1:22pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/18 "2025-11-10T13:22:58Z")

</div>

Definitely updated, that error wasn’t there 10 minutes ago 🙂

---

<div class="post-metadata">

**Author:** ![DARU](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/daru/32/136361_2.png) [@DARU](https://community.n8n.io/u/DARU)\
**Post date:** [November 10, 2025, 1:28pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/19 "2025-11-10T13:28:18Z")

</div>

Same problem here. Its still unresponsive.

---

<div class="post-metadata">

**Author:** ![jamiemadden\_n8n](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jamiemadden_n8n/32/90234_2.png) [@jamiemadden\_n8n](https://community.n8n.io/u/jamiemadden_n8n)\
**Post date:** [November 10, 2025, 2:06pm UTC](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056/20 "2025-11-10T14:06:11Z")

</div>

Hi All,

We are aware of an ongoing incident with some cloud users and are actively working to resolve the incident.

As soon as we have more information, we’ll let you know. We ask for your patience at this time.

cheers,

Jamie

[Next page](https://community.n8n.io/t/critical-bug-entire-cloud-instance-crashed-cant-reach-n8n-support/219056.md?page=2)
