Most users experiences should’ve been like this. If anyone experienced severe outages feel free to DM me the details of your account/app and I’ll pass them to the team (in case there was an underlying issue within the issue)
5 Likes
Bubble’s status page does not report accurate downtime
Here is the status from bubble and below that is the status of bubble when using our own statuspage and connecting directly into bubbles downtime.
Bubble
Ours
(Powered by Bubble’s statuspage)
You can see that bubble really only has a 98.5% uptime.
Both ours and bubble’s downtime / uptime should be exactly the same, the difference here is that changes made retroactively to manipulate historical downtime on bubble, does not reflect any changes when using a statuspage component (if that’s what’s going on)
2 Likes
like I mentioned above, I’m not part of the engineering team, but I feel like this lacks nuance. If you look at how statuspage works you’ll notice that it depends on Bubble’s implementation of component states. In very rare occasions Bubble might throw a false status update. Ideally there would be some sort of “impartial” observability tool Bubble could use, but who knows how doable that is.
1 Like
status page shows all operational, but my site isn’t working. I get this message:
We found bad DNS records for … These records are pointing to the servers that do not belong to Bubble: A record 104.19.241.93, A record 104.19.240.93
That seems unrelated… check your DNS records
1 Like
Is it possible they changed after 5 years of working just fine?
Bubble 2.0 please. Complete overhaul
Well, its happening once again!!!