CheckUpstream measured Storyblok at 100.000% availability across 2029 independent checks (global · api). No incidents have been recorded for Storyblok in the past 12 months. Status signals are polled from Storyblok's official status feed, alongside independent probes and community reports.
30 days measured availability how this is computed
100.000%
global · api · n=2029 · p95 444ms (30d)
Share of our own checks against Storyblok endpoints that returned Storyblok's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Storyblok 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 Storyblok
7d
100.000%
30d
100.000%
90d
100.000%
180d
100.000%
1y
100.000%
Does Storyblok actually matter to you?
A Storyblok 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 →No incidents recorded for this service.
Live Storyblok status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/storyblok)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Storyblok is currently Operational. CheckUpstream tracks Storyblok 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 Storyblok down" view? See the Storyblok Live status page.
Storyblok has not had a resolved incident in the past 12 months on the surfaces CheckUpstream monitors.
Storyblok's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Storyblok endpoints. It is the share of checks that returned the expected response, not a figure taken from Storyblok's status page.
Sign up to CheckUpstream and add Storyblok 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 Storyblok'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.