Original thread is locked. [image] Postmortem on today's incident coming soon Hi all, Following up on Josh’s post, I’d like to present the post-mortem from the outage we had yesterday. Impact: From approximately 3:01PM eastern on April 24 until 4:00PM eastern, our main Bubble cluster (both im…

I believe some dedicated clusters was affected from edge cases like a plugin in testing mode? (I guess a plugin in testing mode relies on the shared cluster? Not sure how that works) I chatted with another bubbler who works on a dedicated cluster and they had no issues

[image] georgecollier: At least help us out by committing to % uptime or certain SLOs :frowning: They’ve already committed to making reliability a focus, look how that’s going. I’m not sure how much a commitment will mean unless it’s in a SLA that they are legally bound to.

Could the Bubble team share more on their deployment method? is their shared cluster all just one big cluster that they roll out updates to? Can’t they do a deployment for a small cluster as beta tester(maybe starting with Starter plans) before moving on to the more expensive plans? My client was a…

I believe this has an issue with new plugin versions as well, as I’m no longer able to retrieve the correct object back on production vs the correct object on testing in an API call. As noted in my prior post .

Quick question @georgecollier & @chris.williamson1996 . For myself and others reading these type of threads with less than expert knowledge on Bubble’s backend framework/infrastructure, what SHOULD we expect as customers? Obviously 100% uptime and 100% transparent communication would be ideal but w…

They locked t he thread! :exploding_head: Res Ipsa Loquitur (“the thing speaks for itself.)

I think that the only two things in terms of their deployment method are the Immediate Releases and Scheduled Releases , but in this case, both were affected [image] nocodejordan: Am just wondering why when every outage happens, it causes chaos to every Bubble user… Good point, wondering the …

Frankly, to me that long post is just a lot of mumbo jumbo now. All these mean nothing if they keep coming again and again. I don’t get assured by them now and am immunised. As he wrote himself, they have become expert at writing postmortem messages rather than fixing things.

Seems to be a new trend with Bubble staff writing posts and then either never responding to the community or just locking the threads so nobody can actually respond. It is clearly a shift in the way that Bubble are operating and a big show of lack of care towards us little people. I understand that…

Great point, I have moved my app to scheduled release. Hope that in future it won’t be affected.

Postmortem discussion thread

Topic		Replies	Views
Update: Postmortem on April 24 incident Announcements	33	4542	May 7, 2024
Incident postmortem from 11/29 Announcements	45	5033	December 21, 2022
Workflow error - Temporary bug Bugs	152	3238	May 2, 2024
My Life Went Miserable Tips	38	2480	February 9, 2019
Outage [SEPT 29] Bugs	81	1224	October 2, 2025

Postmortem discussion thread

Related topics