Liveblocks logo

Is Liveblocks Down?

Developer ToolsLive status, outages, and incident history

No. Liveblocks is up right now.

Every monitored Liveblocks system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · every 60s

Know the moment Liveblocks breaks

Liveblocks is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Liveblocks status page
How we know: the official Liveblocks status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Liveblocks Status Summary

As of 03:38 UTC on 9 November 2026, Liveblocks is operational. PulsAPI checked Liveblocks's official status page and found 2 of 2 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Liveblocks, counting degraded performance as up. The latest incident, "Elevated errors connecting to rooms and accessing Storage", was on Oct 29, 2026 and lasted 1h 12m.

Cite as: PulsAPI, “Liveblocks status”, checked 9 November 2026, 03:38 UTC. https://www.pulsapi.com/services/liveblocks

Liveblocks Component Status

The main Liveblocks systems on this page. All 2 are operational right now.

2operational
API
Operational
Website & Dashboard
Operational

Component statuses may change independently during partial outages.

Recent Liveblocks Outages & Incidents

Incident history from the official Liveblocks status page, including resolution updates.

Elevated errors connecting to rooms and accessing StorageResolved Oct 29, 2026 · 1h 12mResolved

This incident has been resolved. --- [2026-10-29T16:02:54.584Z] (monitoring) Errors have dropped to normal levels. We're continuing to monitor while our infrastructure provider confirms their fix. --- [2026-10-29T15:33:06.994Z] (identified) We're still seeing elevated errors when connecting to rooms and accessing Storage. The cause is an ongoing incident at our infrastructure provider affecting Durable Objects, and we're waiting on their fix. We're monitoring closely and will post another update once things change. --- [2026-10-29T14:58:26.712Z] (identified) We're seeing elevated error rates affecting a subset of rooms since earlier today. Some users may fail to connect to rooms (WebSocket connection timeouts), and some Storage reads and writes via the REST API may fail. This appears to be related to an ongoing incident at our infrastructure provider affecting Durable Objects: https://www.cloudflarestatus.com/incidents/r4mz367vddi7. We're monitoring closely and will post an update as soon as we know more.

Some rooms failing to connectResolved Oct 29, 2026 · 2h 54mResolved

This incident has been resolved. --- [2026-10-29T11:09:10.062Z] (investigating) Only a small part of the issues have been fully resolved, but we're still seeing other issues stemming from a second root cause. We're still ivnestigating. --- [2026-10-29T09:45:06.871Z] (monitoring) Our infrastructure provider has identified and mitigated the underlying issue. We're seeing recovery and are monitoring to make sure it holds. --- [2026-10-29T08:56:10.705Z] (investigating) We're investigating an issue where a small number of rooms intermittently fail to connect or load. Most rooms are unaffected. We're looking into this together with our infrastructure provider and will post an update when we know more.

Elevated API Errors for Comments and Notifications endpointsResolved Aug 13, 2026 · 1 minResolved

This incident has been resolved. --- [2026-08-13T15:32:42.458Z] (identified) The issue has been identified and a fix is being implemented.

Liveblocks Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Liveblocks incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history1 day observed
Nov 9100.00% averageNov 9

Live Liveblocks Outage Reports

Problems reported by engineers using Liveblocks. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Liveblocks problems reported yet.

Something wrong with Liveblocks on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Liveblocks

Liveblocks posts its status at liveblocks.statuspage.io. The page covers 2 components, among them API and Website & Dashboard. Past incidents and uptime for Liveblocks stay on this page, which helps when you want to know how often it has trouble.

Over the past 30 days, PulsAPI has measured Liveblocks uptime at 100.00%. Response times, incident history, and SLA tracking for Liveblocks are available on the PulsAPI dashboard.

Liveblocks Status FAQ

Is Liveblocks down right now?

The verdict at the top of this page comes from the latest poll of the official Liveblocks status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Liveblocks is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Liveblocks recovers.

How do I check Liveblocks uptime history?

PulsAPI tracks Liveblocks uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Liveblocks changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Liveblocks outages?

PulsAPI reads the official Liveblocks status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Liveblocks components?

Yes. PulsAPI monitors 2 individual Liveblocks components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Liveblocks goes down?

Yes. Create a free account and subscribe to Liveblocks: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Liveblocks to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Liveblocks problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Liveblocks?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Liveblocks plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Liveblocks with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services