- 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 8m it lasted.
Anything that failed between 2025-08-29 13:22 UTC and 2025-08-29 14:30 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 are currently investigating the issue.
provider
- investigating
Most errors in response generation have been fixed, but responses aren't using knowledge. We're still investigating.
provider
- identified
We have identified the root cause and are rolling out a fix.
provider
- monitoring
The fix has been rolled out and we're monitoring the situation.
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-b14db570f4
Is Liveblocks still down?
No, this incident was resolved 2025-08-29 14:30 UTC. For Liveblocks's live state, see https://down.guide/liveblocks.
How long did it last?
1h 8m, from 2025-08-29 13:22 UTC to 2025-08-29 14:30 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.