- Level
- confirmed
- Worst impact
- Major outage
- Components
- API
- Down Index
- 52of 100
What to do
Check whether you use Liveblocks API. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3h 35m it lasted.
Anything that failed between 2025-06-12 18:20 UTC and 2025-06-12 21:55 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.
Updates from Liveblocks 5
- investigating
We're currently experiencing issues with one of our cloud providers, which causes elevated API Errors on the Liveblocks API.
provider
- investigating
We are continuing to investigate this issue.
provider
- identified
Our provider, Cloudflare, identified the issue, and we are starting to see services recover.
provider
- monitoring
Cloudflare resolved the issue. Liveblocks API is operational again.
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-3edcc60b6b
Is Liveblocks still down?
No, this incident was resolved 2025-06-12 21:55 UTC. For Liveblocks's live state, see https://down.guide/providers/liveblocks.
How long did it last?
3h 35m, from 2025-06-12 18:20 UTC to 2025-06-12 21:55 UTC, by the times Liveblocks posted.
What was affected?
Liveblocks named API.
What caused it?
Liveblocks hasn't published a root cause. If it does, it shows here.
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.