52 recorded Bubble incidents since February 2026, with official updates, affected components, duration and resolution information.
Status: Identified We're continuing to work on restoring functionality. We are working on a more substantial update, and will post it (or another interim check-in) by 9 pm ET. Affected components Bubble Dedicated (Partial outage) Bubble Editor (Partial outage) Main Bubble Environment (Partial outage)
Status: Resolved Fix has been deployed and tested. Android builds are succeeding. Affected components Google Play Store deployment (Operational)
Status: Resolved We have confirmed the situation was resolved
Status: Resolved The 3rd party service is still in degraded performance but our builds are succeeding. Affected components Apple App Store deployment (Operational) Google Play Store deployment (Operational)
Status: Resolved The root cause has been identified and fixed. Affected components Main Bubble Environment (Operational) Bubble Dedicated (Operational)
Status: Resolved This bug has been marked as a known issue while we continue to communicate with chrome support. Affected components Bubble Editor (Operational)
Status: Resolved JitPack is back online, and Android builds are succeeding Affected components Google Play Store deployment (Operational)
Status: Resolved Services are up. We are continuing to monitor, but all apps are available and working. Affected components Bubble Dedicated (Operational) Bubble Editor (Operational) Main Bubble Environment (Operational)
Status: Resolved 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. Affected components Main Bubble Environment (Operational) Cloudflare Gateway (Operational) Cloudflare Infrastructure (Operational)
Status: Resolved Our service provider is operating normally. Affected components Application Logs & Metrics (Operational)
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 automated systems are identifying elevated log storage errors starting 11:15 AM ET. Some logs might not be showing up sporadically
Log ingestion is still 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/>
Our log provider is back online, and logs are being ingested. We are continuing to monitor the situation to make sure it does not degrade again.
Log ingestion is stable.
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 team 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.
