They responded to my bug report, escalating to Tier 2 support team, so they are aware 
Broken here as well!
App UI is up, I’m able to login… but most of the data types are not available, so our production app (during peak hours of the day) is basically 100% down.
Our app is also malfunctioning in several ways. There are so many things going on its hard to even hypothesize what might be happening.
I’m experiencing the same behavior. Users can’t access all their data. I submitted a bug report.
First thing I did was to check out the https://status.bubble.io/ page and it’s very frustrating that all is green. I am grateful that at least we have this forum which can confirm that this the issue is due to Bubble, and is not related to my app specifically.
That’s exactly how I described it when I emailed them
Can’t access searches for some specific data types, does anyone have news?
Ah, the classic All Systems Operational — it’s like a warm hug during a hailstorm.
I thought I was going crazy, I watched workflows run on debug mode and still somehow it breaks. I even cleared my cache and restarted my PC
Let’s see how long it’ll be this time!
Things are looking resolved on my end for now
still broken for me. Dont worry though bubble uptime stats look good at the moment lol
Massive issues for me as well. Running API, Deleting objects, editing lists. copying opjects. and it says its up… im like “am I nuts???”
Since I submitted my bug report a few minutes ago and instructed Bubble to log in as user XXX@gmail.com to see the bug for themselves, I can see that Bubble logged in twice as that user from the US (I’m based in France). So they are still investigating the issue. Don’t forget to submit bug reports!
Things have returned to normal for me.
This is a big one for us. Hopefully it resolves itself, but data prior to the outage has been affected and can be seen in our reporting.
A data point for the community: back to normal for me.
Hi all – confirming that this is working again. Digging into this with the team now, but we shipped a bug that caused data not to load under certain circumstances (not sure what the complete set of circumstances is, but it’s definitely related to privacy rules as discussed above); we’ve reverted the offending code
Thanks for fixing quickly but come on… something like this must surely be picked up during testing (automated or otherwise). It feels like Bubble continuously uses the shared cluster as a test environment at the expense of our live apps.
Hey @josh,
I hope you’re doing well. I’m getting straight to the point here: the recent Bubble updates have been a pain. Our app, along with many others, has broken a few times after these core updates. Most times, nobody realizes there’s an issue until someone reports it on the forum. This means our live apps are down for an hour in the best scenario, or more, which is super frustrating for both us and our users.
I think we already suggested this, but once again, here’s what I suggest:
- Let us control updates: Can we get an option to opt-out of automatic core updates on the shared clusters? It’d be great if we could choose when to upgrade. This way, we can test things out and make sure nothing breaks before making the move. Exactly the same thing we have with version control when a breaking-change is introduced.
- Keep an eye on the forum post-update: After you guys roll out a new update, it’d be cool if someone from the team could actively monitor the forum for at least the next hour. Issues usually pop up quick, and this would help in catching them early.
- AI-forum watcher: I’m sure you guys can use an AI such as OpenAI to detect possible forum threads that are reporting systems down or a massive failure like this thread and internally fire the alarms.
I know you guys are working hard, and it’s a headache to detect this, but this can’t happen every few weeks. Just these couple of tweaks would make things smoother for all of us.
Redu.