Is Liveblocks Down?

No — Liveblocks is up

Liveblocks's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 712 ms

Right now

The verdict is the worse of these two. How we decide

Liveblocks's status page

liveblocks.statuspage.io · read 4 minutes ago · checked every 3 minutes

Operational

Liveblocks's components, as its status page reports them
Component	Status
API	Operational
Website & Dashboard	Operational

Open their status page

FlareWarden checks

liveblocks.io from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 712 ms
Checked: 2 hours ago

By region

Amsterdam reachable, 941 ms
Chicago reachable, 406 ms
San Jose reachable, 291 ms
Singapore reachable, 868 ms
Stockholm reachable, 978 ms
Sydney reachable, 676 ms
Tokyo reachable, 1086 ms
Toronto reachable, 453 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	39 ms	4 ms	22 ms	329 ms
Chicago	48 ms	1 ms	23 ms	256 ms
San Jose	154 ms	2 ms	12 ms	268 ms
Singapore	80 ms	3 ms	7 ms	351 ms
Stockholm	167 ms	1 ms	12 ms	468 ms
Sydney	5 ms	1 ms	11 ms	261 ms
Tokyo	189 ms	2 ms	13 ms	756 ms
Toronto	52 ms	11 ms	29 ms	278 ms

We check that liveblocks.io loads, not every feature behind it. Test it yourself

History

Incidents Liveblocks reported

Since Oct 22, 15 days · from liveblocks.statuspage.io

Incidents: 2
Major or critical: 1
Median to resolve: 2h 3m

Elevated errors connecting to rooms and accessing Storage
major · Oct 29
lasted 1h 12m
Some rooms failing to connect
minor · Oct 29
lasted 2h 54m

Liveblocks website availability

Measured by FlareWarden · liveblocks.io

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 762ms

Last 30 days

59-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of liveblocks.io from multiple regions every 6 hours. Liveblocks's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 59 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Liveblocks does

Liveblocks provides the infrastructure behind multiplayer features in web applications: presence indicators, live cursors, comments, notifications and conflict-free shared documents. Applications connect to it over WebSockets and it synchronises state between everyone in a room. Products that build collaborative editing on it depend on it for the parts users notice most immediately.

What an outage looks like

Collaborators disappear from a document, cursors and presence stop updating, and edits made by one person never appear for anyone else. Each user often keeps editing their own local copy without an error, so two people can both believe they are working normally while seeing entirely different content. Comments and notifications stop loading.

What to do about it

Read liveblocks.statuspage.io, which reports API and Website and Dashboard as its components. If API is affected, treat the session as unsynchronised rather than healthy and warn collaborators before they diverge further. Avoid having several people continue editing the same document during an incident, since the reconciliation on recovery is the part most likely to surprise you. If only Website and Dashboard is affected, your application's realtime connections are unaffected.

Is it down for everyone, or just you?

If this page says Liveblocks is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Liveblocks outage FAQ

My document still edits normally but nobody else sees my changes. Is Liveblocks down?

That is the characteristic symptom. Liveblocks clients apply changes locally first and synchronise them afterwards, so an interruption leaves each person editing a working local copy with no error shown. Everyone believes the document is fine and everyone is seeing something different. Check the API row on liveblocks.statuspage.io as soon as presence indicators or cursors stop moving, because that is the earliest visible sign.

Will edits made during a Liveblocks outage be lost?

Liveblocks uses conflict-free data structures designed to merge changes when a connection is restored, so edits made offline commonly reconcile rather than disappear. Liveblocks does not publish a guarantee covering every failure mode, so treat reconciliation as likely rather than certain, and copy anything irreplaceable out of the editor before refreshing. Refreshing mid-incident is the action most likely to discard unsynchronised local state.

Is it Liveblocks or my own WebSocket connection?

Compare scope. A local network or proxy blocking WebSockets affects one user, often on a corporate network or VPN, while a Liveblocks incident disconnects every collaborator at once. The measurements above probe from several regions, so if they all report the service reachable and only one person has dropped out, look at that person's network before the platform.

The Liveblocks dashboard will not load. Is my application affected?

Probably not. Liveblocks reports Website and Dashboard as a component separate from API, so the site you use to inspect rooms and usage can be down while your application's realtime connections continue normally. Treat it as lost administration rather than an outage, and check the API row to confirm end users are unaffected.

Should I tell users to stop editing during a Liveblocks incident?

For shared documents, yes, it is usually the safer instruction. The longer several people edit the same room while disconnected, the more divergent local states have to be merged on recovery, and the more likely someone sees an outcome they did not expect. Asking collaborators to pause and to copy anything critical elsewhere costs little and avoids the messiest failure mode.

How we measure this

We request Liveblocks's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Liveblocks publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Liveblocks itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Liveblocks goes down

We check Liveblocks every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required