CheckUpstream measured Liveblocks at 100.000% availability across 2829 independent checks (global · api). 2 incidents were recorded in the past 12 months; the most recent resolved 46 days ago after 1 hour. Status signals are polled from Liveblocks's official Atlassian Statuspage status page, alongside independent probes and community reports.
30 days measured availability how this is computed
100.000%
global · api · n=2829 · p95 237ms (30d)
Share of our own checks against Liveblocks endpoints that returned Liveblocks's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Liveblocks posted no incidents in this window. That is either a clean run or a communication policy — from outside, the two look identical.
Fewer incidents in the last 30 days than 55% of 232 tracked services.
Share of each window with no impact declared by Liveblocks
7d
100.000%
30d
100.000%
90d
100.000%
180d
100.000%
1y
100.000%
Does Liveblocks actually matter to you?
A Liveblocks outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Live Liveblocks status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/liveblocks)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Liveblocks is currently Operational. CheckUpstream tracks Liveblocks in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is Liveblocks down" view? See the Liveblocks Live status page.
Liveblocks's last resolved incident started 46 days ago and lasted 1h 24m (degraded performance).
Liveblocks's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Liveblocks endpoints. It is the share of checks that returned the expected response, not a figure taken from Liveblocks's status page.
Sign up to CheckUpstream and add Liveblocks to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Liveblocks's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.