Bubble outage, 10 November 2026
We're investigating reports that bubble.io and the editor are not loading for users.
- Started
- Resolved
- 10 Nov 2026, 20:34 UTC (after 55 min)
- Impact
- Minor
Is this still happening?
No. Bubble marked this incident resolved on 10 Nov 2026, 20:34 UTC, 55 min after it began.
Right now: Bubble reports all systems operational. (as of 13 Nov, 20:53 UTC) Live Bubble status
At a glance
- Bubble rated this a minor incident.
- It was resolved after 55 min. That is shorter than a typical Bubble incident: the median of the 29 other resolved ones we recorded is 1 h 45 min.
- Bubble had 6 other incidents in the 30 days before it.
- 3 earlier incidents look like the same kind of problem (same affected part or wording); the most recent was on 7 Jul 2026.
Our summary from the Bubble incidents we have recorded since 11 Jun 2026 - how we count.
What caused it: Bubble's root cause analysis
**What happened** At 9:00 AM ET on November 10 we shipped a change to how our servers cache data. A side effect was that our servers began requesting font data from Google far more often than before. Google caps how many of these requests we can make per day. That afternoon we hit that cap, and Google began rejecting our requests. Page loads that depended on that font data stalled or failed, and the failed requests were retried, which kept us pinned at the limit. **Timeline (November 10, ET)** - **2:10 PM**: Google begins rejecting our font requests. Errors and slow page loads start. - **2:20 PM**: First user reports appear on the forum. - **2:26 PM**: Our monitoring alerts fire and engineers are paged. - **2:39 PM**: We trace the problem to the 9:00 AM change and decide to roll it back. - **2:49 PM**: We confirm the usage cap is the cause, ask Google for a higher limit, and begin provisioning separate capacity so we don't have to wait for that request. - **3:00 PM**: The rollback is live. It does not restore service on its own, because we are still over the cap. - **3:08 PM**: We find that our servers have not picked up the new capacity. We correct this and restart them. - **3:09 PM**: Uptime checks pass again. - **3:15 PM**: Errors have dropped off and we move to monitoring. **What we're doing about it** - The change that caused the increase has been rolled back. - We have provisioned additional capacity and asked Google for a higher limit. - We are changing how fonts are loaded so that page loads no longer depend on a request to Google. This work is in progress.
Last update from Bubble
**What happened** At 9:00 AM ET on November 10 we shipped a change to how our servers cache data. A side effect was that our servers began requesting font data from Google far more often than before. Google caps how many of these requests we can make per day. That afternoon we hit that cap, and Google began rejecting our requests. Page loads that depended on that font data stalled or failed, and the failed requests were retried, which kept us pinned at the limit. **Timeline (November 10, ET)** - **2:10 PM**: Google begins rejecting our font requests. Errors and slow page loads start. - **2:20 PM**: First user reports appear on the forum. - **2:26 PM**: Our monitoring alerts fire and en...
Similar Bubble incidents
Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.
-
, resolved after 1 h 52 min
-
, resolved after 33 min
-
, resolved after 36 min
Other recent Bubble incidents
Something wrong on this page?
Thanks - your report is on its way to us. We read every one.