# Has the bubble websocket stopped working?

**URL:** <https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048>\
**Category:** Bugs\
**Created:** [January 27, 2026, 9:31pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048 "2026-01-27T21:31:24Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![carlovsk.edits](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/carlovsk.edits/32/251706_2.png) [@carlovsk.edits](https://forum.bubble.io/u/carlovsk.edits)\
**Post date:** [January 27, 2026, 9:31pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/1 "2026-01-27T21:31:24Z")

</div>

I don’t know how it is for you.

But here, Bubble’s realtime isn’t working, neither for changes in the editor, viewing the preview, nor for changes in the database. It’s only updating when I refresh the page.

Is anyone else having this problem? I tested it on more than one Bubble account.

---

<div class="post-metadata">

**Author:** ![stepwave.io](https://avatars.discourse-cdn.com/v4/letter/s/eb9ed0/32.png) [@stepwave.io](https://forum.bubble.io/u/stepwave.io)\
**Post date:** [January 27, 2026, 9:37pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/2 "2026-01-27T21:37:11Z")

</div>

Yep, stopped working for me at some point in the last hour. I’ve tried to contact Bubble, not sure of the status. Bubble Status page shows everything is up but there’s definitely something going on here.

---

<div class="post-metadata">

**Author:** ![carlovsk.edits](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/carlovsk.edits/32/251706_2.png) [@carlovsk.edits](https://forum.bubble.io/u/carlovsk.edits)\
**Post date:** [January 27, 2026, 9:38pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/3 "2026-01-27T21:38:21Z")

</div>

I just tried it on another browser too, and it didn’t work…

@fede.bubble

---

<div class="post-metadata">

**Author:** ![fede.bubble](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/fede.bubble/32/215574_2.png) [@fede.bubble](https://forum.bubble.io/u/fede.bubble)\
**Post date:** [January 27, 2026, 9:40pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/4 "2026-01-27T21:40:30Z")

</div>

checking with the team, one sec

---

<div class="post-metadata">

**Author:** ![reger-alexander](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/reger-alexander/32/22827_2.png) [@reger-alexander](https://forum.bubble.io/u/reger-alexander)\
**Post date:** [January 27, 2026, 9:43pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/5 "2026-01-27T21:43:04Z")

</div>

I’m seeing the same issues

---

<div class="post-metadata">

**Author:** ![fede.bubble](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/fede.bubble/32/215574_2.png) [@fede.bubble](https://forum.bubble.io/u/fede.bubble)\
**Post date:** [January 27, 2026, 9:47pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/6 "2026-01-27T21:47:03Z")

</div>

# UPDATE 4:46pm EST

Team is investigating

---

<div class="post-metadata">

**Author:** ![jacob20](https://avatars.discourse-cdn.com/v4/letter/j/b3f665/32.png) [@jacob20](https://forum.bubble.io/u/jacob20)\
**Post date:** [January 27, 2026, 9:52pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/7 "2026-01-27T21:52:14Z")

</div>

Yup dealing with this on our end too in dedicated

---

<div class="post-metadata">

**Author:** ![tim27](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/tim27/32/252979_2.png) [@tim27](https://forum.bubble.io/u/tim27)\
**Post date:** [January 27, 2026, 9:52pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/8 "2026-01-27T21:52:18Z")

</div>

I am getting the same. Editor updates are not showing the Refresh your page notification banner on version-test. Real-time updates are not displaying; I need to hard refresh the page to get values to display correctly.

My app is on Shared Servers.

---

<div class="post-metadata">

**Author:** ![ksaitow1](https://avatars.discourse-cdn.com/v4/letter/k/fbc32d/32.png) [@ksaitow1](https://forum.bubble.io/u/ksaitow1)\
**Post date:** [January 27, 2026, 9:54pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/9 "2026-01-27T21:54:57Z")

</div>

Looks like Bubble just posted the issue on [Incident.io](http://Incident.io)

---

<div class="post-metadata">

**Author:** ![fede.bubble](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/fede.bubble/32/215574_2.png) [@fede.bubble](https://forum.bubble.io/u/fede.bubble)\
**Post date:** [January 27, 2026, 9:55pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/10 "2026-01-27T21:55:19Z")

</div>

yep! Status page is now updated

---

<div class="post-metadata">

**Author:** ![carlovsk.edits](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/carlovsk.edits/32/251706_2.png) [@carlovsk.edits](https://forum.bubble.io/u/carlovsk.edits)\
**Post date:** [January 27, 2026, 9:57pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/11 "2026-01-27T21:57:48Z")

</div>

> [@fede.bubble](#):
>
> # UPDATE 4:46pm EST
> 
> Team is investigating

Alright, they’re investigating…

I hope they resolve this quickly, because this directly affects the product purchase flow inside my app, potentially causing users to buy twice, trying once, the data not updating, then trying again… There are countless possible issues when realtime isn’t working.

---

<div class="post-metadata">

**Author:** ![DjackLowCode](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/djacklowcode/32/222536_2.png) [@DjackLowCode](https://forum.bubble.io/u/DjackLowCode)\
**Post date:** [January 27, 2026, 10:10pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/12 "2026-01-27T22:10:26Z")

</div>

Dedicated instances impacted also.

---

<div class="post-metadata">

**Author:** ![rome1](https://avatars.discourse-cdn.com/v4/letter/r/b38774/32.png) [@rome1](https://forum.bubble.io/u/rome1)\
**Post date:** [January 27, 2026, 10:11pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/13 "2026-01-27T22:11:29Z")

</div>

Ooof, hopefully it can be fixed quickly. Completely breaks the user experience for us

---

<div class="post-metadata">

**Author:** ![fede.bubble](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/fede.bubble/32/215574_2.png) [@fede.bubble](https://forum.bubble.io/u/fede.bubble)\
**Post date:** [January 27, 2026, 10:11pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/14 "2026-01-27T22:11:42Z")

</div>

# UPDATE 5:11pm EST

Team has identified the problem, they are pushing a fix

---

<div class="post-metadata">

**Author:** ![rome1](https://avatars.discourse-cdn.com/v4/letter/r/b38774/32.png) [@rome1](https://forum.bubble.io/u/rome1)\
**Post date:** [January 27, 2026, 10:15pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/15 "2026-01-27T22:15:06Z")

</div>

Awesome, love to see how fast the bubble team has been responding to issues lately 🙂 I know you catch a lot of flak for the outages but its reassuring to at least know the team can move quickly.

Would love a debrief after-the-fact on the cause of the issue

---

<div class="post-metadata">

**Author:** ![fede.bubble](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/fede.bubble/32/215574_2.png) [@fede.bubble](https://forum.bubble.io/u/fede.bubble)\
**Post date:** [January 27, 2026, 10:21pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/16 "2026-01-27T22:21:33Z")

</div>

# UPDATE 5:21pm EST

Status page has been updated adding info on what happened

---

<div class="post-metadata">

**Author:** ![fede.bubble](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/fede.bubble/32/215574_2.png) [@fede.bubble](https://forum.bubble.io/u/fede.bubble)\
**Post date:** [January 27, 2026, 10:51pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/17 "2026-01-27T22:51:06Z")

</div>

just checking, everyone back to normal yeah?

---

<div class="post-metadata">

**Author:** ![ksaitow1](https://avatars.discourse-cdn.com/v4/letter/k/fbc32d/32.png) [@ksaitow1](https://forum.bubble.io/u/ksaitow1)\
**Post date:** [January 27, 2026, 11:08pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/18 "2026-01-27T23:08:42Z")

</div>

Seems to be back to normal.

---

<div class="post-metadata">

**Author:** ![stepwave.io](https://avatars.discourse-cdn.com/v4/letter/s/eb9ed0/32.png) [@stepwave.io](https://forum.bubble.io/u/stepwave.io)\
**Post date:** [January 28, 2026, 9:06am UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/19 "2026-01-28T09:06:57Z")

</div>

All back to normal last night.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/bubble/original/3X/2/8/2847faa74692c2ffa5d939d3dc3724cdd060d247.png) [@system](https://forum.bubble.io/u/system)\
**Post date:** [February 10, 2026, 9:31pm UTC](https://forum.bubble.io/t/has-the-bubble-websocket-stopped-working/390048/20 "2026-02-10T21:31:29Z")

</div>

This topic was automatically closed after 14 days. New replies are no longer allowed.
