- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 28of 100
What to do
Check whether your product depends on Bubble. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 15m it lasted.
Anything that failed between 2026-08-04 16:40 UTC and 2026-08-04 17:55 UTC may need a replay.Subscribe to Bubble's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=bubble works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Bubble 2
- investigating
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.
provider
- 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-9f09236df4
Is Bubble still down?
No, this incident was resolved 2026-08-04 17:55 UTC. For Bubble's live state, see https://down.guide/bubble.
How long did it last?
1h 15m, from 2026-08-04 16:40 UTC to 2026-08-04 17:55 UTC, by the times Bubble posted.
What caused it?
Bubble hasn't published a root cause. If it does, it shows here.
Where does this come from?
Bubble's official status page, https://status.bubble.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.