Bubble forum down
Timeline · 2 updates
- investigating Apr 28, 2026, 09:19 AM UTC
- resolved Apr 28, 2026, 11:26 AM UTC
There were 17 Bubble outages since February 9, 2026 totaling 2h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.
Status: Resolved A component of Bubble's core infrastructure suffered a sudden spike of traffic, and did not autoscale properly. This caused connections to timeout and dropped traffic. The team has adjusted scaling parameters and will continue to monitor. Affected components Main Bubble Environment (Operational)
Status: Resolved Cloudflare has resolved their issue. .co domains are functioning properly. Affected components Cloudflare Gateway (Operational)
Status: Resolved The team has deployed changes to production and performance has been restored. The team will continue to monitor into the night, but we are currently calling the issue resolved. Affected components Main Bubble Environment (Operational)
Status: Resolved We rolled back the erroneous build and everything is back to normal on the dedicated environments
Status: Resolved Systems have returned to normal, data access and real-time updates are working as expected. Affected components Main Bubble Environment (Operational)
Status: Resolved Snowflake has implemented a fix for their issue. We can confirm that logging has caught up, no data was lost, and queries are no longer exhibiting errors. Affected components Bubble Editor (Operational) Main Bubble Environment (Operational)
Status: Resolved Configuration has been pushed and logs should now be restored for dedicated instances. Affected components Bubble Editor (Operational)
Status: Resolved Error rates have returned to normal levels and unarchivals are appearing to be back to a healthy state. Affected components Bubble Editor (Operational) Main Bubble Environment (Operational)
Status: Resolved We were able mitigate the issue with the component that was preventing dedicated logins, and functionality has been restored. Affected components Bubble Editor (Operational)
Status: Resolved This region is still volitile, but we have migrated all apps into Frankfurt from the region. Affected components Main Bubble Environment (Operational)
Status: Resolved Data operations have been restored.
Status: Resolved Deploys are succeeding.
Status: Resolved We have fixed the issue Affected components Bubble Editor (Operational)
Status: Resolved Editor access for dedicated customers has been restored. Affected components Bubble Editor (Operational)
Status: Resolved Logs appear to be working normally again. Affected components Bubble Editor (Operational)
Pingoru polls Bubble's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required