Bubble had 54 outages in the last 2 years totaling 129h 16m of downtime — averaging 2.2 incidents per month.
There were 54 Bubble outages since December 5, 2025 totaling 129h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.
Because of the ongoing [Jitpack outage](https://statusgator.com/services/jitpack), new Android builds are failing.
JitPack is back online, and Android builds are succeeding
Some apps appear to be missing their data. The data is there, but it is not showing in the app. We are investigating a misconfiguration of the database name.
We've identified the problem and are working on rolling out the solution. **Data remains intact.** Our service to get the data out is currently offline.
The fix has been rolled out, all users are back up and running. We will be monitoring.
Services are up. We are continuing to monitor, but all apps are available and working.
We are currently investigating a brief outage that was returning HTTP 520s for a couple of minutes. All services are now healthy, but we are continuing to investigate root cause.
We have narrowed our investigation and found the root cause of today's service outage. We are currently working on hardening this mechanism at our load-balancer level to prevent future occurrences.
Our log and metrics provider is currently experiencing ingest performance degradation. You may observe a delay in fetching logs during this time.
The provider has implemented and pushed a fix and are currently monitoring results.
Our service provider is operating normally.
Some dedicated customers are down, seeing SSL/TLS errors.
An issue w/ TLS/SSL certificate termination has been identified.
We have fixed the SSL/TLS issues w/ these domains and are monitoring.
All errors are resolved.
Apps and editors are intermittently down. We are investigating the root cause.
Cloudflare had a brief outage in their proxy service. We're operating normally and monitoring.
Cloudflare has stabilized. We will continue to monitor this throughout the day and weekend.
Log ingestion is degraded, due to an outage in our log provider. We are working with them to get this fixed as soon as possible. [https://status.observeinc.com/](https://status.observeinc.com/ "https://status.observeinc.com/")
Log ingestion is stable.
We are currently experiencing an intermitent issue with [bubble.io](http://bubble.io "bubble.io") and related services.
We've seen a spike of unidentified traffic which has now been subsided. We are making efforts to prevent this in the future.
We're stable now and haven't seen any other issues.
[Bubble.io](http://Bubble.io "Bubble.io") was unreachable from 3:04 to 3:09pm ET
An internal system had an issue which made the bubble editor temporarily become unavailable.
Our load balancer is stopping traffic to Bubble.io
The issue was found and mitigated. Monitoring while we implement a permanent fix.
Continuing monitoring, Bubble.io available again.
A permanent solution to the repeated problem we have been experiencing has been found and deployed.
We are seeing issues with our load balancer, causing traffic to not be routed properly. We are investigating and will have an ETA for remediation shortly.
Load balancer and traffic has been restored, and the response team continues to investigate root cause.
A race condition with our deployment pipeline and ECS cluster caused our load balancer to point to inactive machines. While the current issue is resolved, the incident response will work on mitigation of future issues of this type.
One of the databases powering real-time updates is experiencing issues. We've found the problem and are mitigating.
We have addressed the issue and are seeing errors go down. We will continue monitoring.
Error rates in the real-time update system have returned to normal.
We've identified the issue and are rolling back.
We've rolled back the change.
We've been monitoring for a while as deployments on our side have triggered this issue. We're satisfied with the duration and stability.
We're aware of pages loading from [bubble.io](http://bubble.io "bubble.io") loading slowly, beyond what's acceptable.
The issue was identified and resolved.
We're seeing a slowdown in the editor.
We've identified the issue and are rolling out a fix -- expecting it to recover over the next couple minutes
A second issue was found which caused sporadic issues to occur. We've identified, and monitored.
[bubble.io](http://bubble.io "bubble.io") application and editor down
We are investigating the issue now -- bubble.io is back up.
We are still investigating and are seeing we are stable for now. We are internally following up for next steps.
For applications, cannot delete domains in the Web App section for Domain Settings.
We have resolve the issue and monitoring.
Some users are experiencing a "Service Temporarily Unavailable" in the editor.
The issue has been identified.
We are aware that between ~1PM ET and 2:50 PM ET realtime updates for many apps were delayed / broken and we believe it’s fixed now but are monitoring For more details, behind the scenes we have been rolling out a new notifier service to better handle the realtime update system but we hadn’t yet enabled the alerts on this service. We are adding those now.
Realtime updates are now operationally stable.
Android builds are failing because of a required dependency that lives in the Jitpack repository. We're currently waiting for Jitpack to come back up. You can check Jitpack status here: https://statusgator.com/services/jitpack
Downstream dependency Jitpack has resolved their outage and builds are succeeding again.
We have identified the root cause and actively investigating a fix
Builds are no longer timing out.
We are addressing reports of new issues showing in the issue checker and in runmode for apps with plugins that add custom data types.
We have identified the issue and are rolling back the change.
We have rolled out a fix and are testing that all cases seem resolved.
The issue should be fixed. If there are any remaining issues in the issue checker, please navigate to their page by clicking on the issue in the issue checker and they should resolve.
Functionality on unarchiving apps is currently having issues, which may cause issues loading User Data.
We’ve identified the problem and are attempting to roll out a fix now.
We have fixed the issue and all apps should be fixed now that were experiencing issues loading data.
We have gotten reports in the past few days of versions not appearing correctly in the editor. They are still accessible directly from their url but they don't appear in the version panel, preventing users from manipulating them or merging them. We are looking into this.
We have pushed a temporary mitigation for this issue, inaccessible versions should now be showing up properly. We are looking into longer-term fixes to address adjacent issues with extra deleted versions sporadically showing up.
We have identified the root cause and are planning on supplanting the mitigations with longer-term reliability fixes for this piece of logic