- Level
- confirmed
- Worst impact
- Partial outage
- Components
- API
- Down Index
- 38of 100
What to do
Check whether you use Liveblocks API. 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 12m it lasted.
Anything that failed between 2026-10-29 14:58 UTC and 2026-10-29 16:10 UTC may need a replay.Subscribe to Liveblocks's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=liveblocks works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Root cause
The cause is an ongoing incident at our infrastructure provider affecting Durable Objects, and we're waiting on their fix.
Category: Upstream dependency
Read the postmortemUpdates from Liveblocks 4
- identified
We're seeing elevated error rates affecting a subset of rooms since earlier today. Some users may fail to connect to rooms (WebSocket connection timeouts), and some Storage reads and writes via the REST API may fail. This appears to be related to an ongoing incident at our infrastructure provider affecting Durable Objects: https://www.cloudflarestatus.com/incidents/r4mz367vddi7. We're monitoring closely and will post an update as soon as we know more.
provider
- identified
We're still seeing elevated errors when connecting to rooms and accessing Storage. The cause is an ongoing incident at our infrastructure provider affecting Durable Objects, and we're waiting on their fix. We're monitoring closely and will post another update once things change.
provider
- monitoring
Errors have dropped to normal levels. We're continuing to monitor while our infrastructure provider confirms their fix.
provider
- resolved
This incident has been resolved.
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-920c2a9eac
Is Liveblocks still down?
No, this incident was resolved 2026-10-29 16:10 UTC. For Liveblocks's live state, see https://down.guide/liveblocks.
How long did it last?
1h 12m, from 2026-10-29 14:58 UTC to 2026-10-29 16:10 UTC, by the times Liveblocks posted.
What was affected?
Liveblocks named API.
What caused it?
Upstream dependency. Liveblocks wrote: "The cause is an ongoing incident at our infrastructure provider affecting Durable Objects, and we're waiting on their fix." The postmortem: https://stspg.io/t975wkwpv46h
Where does this come from?
Liveblocks's official status page, https://liveblocks.statuspage.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.