Liveblocks had 18 outages in the last 2 years totaling 44h 56m of downtime — averaging 0.7 incidents per month.
There were 18 Liveblocks outages since August 5, 2025 totaling 44h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.
Our provider, Cloudflare, is experiencing an increase in errors across Europe and APAC. A fix has been deployed, and the service is recovering.
This incident has been resolved.
We're currently investigating connectivity issues in both Tel Aviv and Seattle regions.
It looks like the issues have been caused by an upstream provider issue which has been addressed. Systems are available again, but we're still monitoring.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
This incident has been resolved.
We're currently investigating reports of elevated timeouts impacting some customers.
This incident has been resolved.
The API rate limiting may be triggering below the defined limit.
This incident has been resolved.
We are currently investigating this issue.
Cloudflare implemented a fix that is being rolled out.
We are still monitoring the situation. Most latency issues have been resolved and are back at normal levels. Only a very small number of users are still affected.
This incident has been resolved.
We're currently investigated intermittent connectivity issues connecting to rooms. We will update further as we investigate.
A fix has been deployed and we are monitoring
We are continuing to monitor for any further issues.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are having issues with our auth provider, making logging in to the Liveblocks dashboard currently not possible. We are investigating.
We are continuing to investigate this issue.
The issues are resolved, logging in is possible again. We're monitoring the situation.
We are continuing to monitor for any further issues.
This incident has been resolved.
Some pages in the Liveblocks dashboard are unavailable, we're investigating.
We have identified the issue to be related to projects with a large amount of events. Most projects are unaffected. We are continuing to find a fix for the issue.
We have identified the root cause of this issue and are working on a fix.
We are deploying the fix.
The fix has been fully rolled out. We are monitoring the situation.
This incident has been resolved.
We are seeing elevated error rates and are receiving reports of rooms not being available. We are investigating.
The issue is identified as an unavailability in our downstream platform provider. The related incident that's causing this is https://www.cloudflarestatus.com/incidents/8gmgl950y3h7. We are following development closely.
We are seeing error rate dropping again, and room availability is recovering. We are continuing to monitor the situation.
Operations are fully restored.
Many services from the upstream provider AWS were down and impacted us.
There was an incident with a rollout between 2:06pm and 2:17pm UTC.
This incident has been resolved.
Due to an upstream provider issue we experienced a temporary increase in error rate lasting approximately 15 minutes. The upstream issue is resolved and currently being monitored.
We are currently investigating the issue.
Most errors in response generation have been fixed, but responses aren't using knowledge. We're still investigating.
We have identified the root cause and are rolling out a fix.
The fix has been rolled out and we're monitoring the situation.
This incident has been resolved.
The getInboxNotifications endpoint is currently experiencing higher than normal error rate. The error has been identified and we're rolling out a fix.
A fix has been deployed, we are monitoring
We are continuing to monitor for any further issues.
This incident has been resolved.
A deployment at 19:20 UTC time caused the mutation portion of the liveblocks-node sdk to throw an error. The change was reverted after 24 minutes and the problem was resolved.