- Level
- confirmed
- Worst impact
- Degraded
- Components
- API
- Down Index
- 31of 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 4h 27m it lasted.
Anything that failed between 2024-09-28 15:30 UTC and 2024-09-28 19:57 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 4
- investigating
useUsersThreads_experimental is currently unstable when returning a large number of threads. The team is investigating
provider
- identified
A suboptimal query has been identified, which caused undesired timeouts. The team is currently working on a fix.
provider
- monitoring
A fix has been deployed. The team is monitoring production.
provider
- resolved
Producting system are now back to normal.
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-93715adbf6
Is Liveblocks still down?
No, this incident was resolved 2024-09-28 19:57 UTC. For Liveblocks's live state, see https://down.guide/liveblocks.
How long did it last?
4h 27m, from 2024-09-28 15:30 UTC to 2024-09-28 19:57 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.