- Level
- confirmed
- Worst impact
- Partial outage
- Components
- API
- Down Index
- 42of 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 6h 33m it lasted.
Anything that failed between 2024-01-05 11:27 UTC and 2024-01-05 18:00 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 2
- investigating
At 3:30 AM EST, we detected an unusual amount of storage write failures. Accounts using Storage might be impacted. Our team is investigating this issue.
provider
- resolved
Storage write failures impact a very limited number of rooms on a very limited set of customers. The underlying issue has been identified and fixed.
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-db81b47d6d
Is Liveblocks still down?
No, this incident was resolved 2024-01-05 18:00 UTC. For Liveblocks's live state, see https://down.guide/providers/liveblocks.
How long did it last?
6h 33m, from 2024-01-05 11:27 UTC to 2024-01-05 18:00 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.