What Is status.storyblok.com?
Storyblok's official status page at status.storyblok.com is powered by Atlassian Statuspage and tracks real-time health for all of Storyblok's infrastructure. It shows per-component status so you can immediately see whether the CDN Content Delivery API, the Management API, the visual editor app, or the Image Service is the source of problems.
Storyblok is a component-based headless CMS popular with enterprise and agency teams building composable web applications. Its CDN-first architecture means content delivery is usually resilient even when the Management API has issues.
Storyblok Status Indicators: What Each Color Means
Get alerted the instant Storyblok goes down
Better Stack monitors your Storyblok CDN API endpoints every 30 seconds and alerts your team before users see blank content areas. Free tier included.
Try Better Stack Free →Storyblok Services: What Can Fail Independently
Storyblok is architected with distinct services that can fail independently. Knowing which one is down determines your response and workarounds:
Content Delivery API (CDN)
What it is: The CDN-backed read API at api.storyblok.com/v2/cdn that your website uses to fetch published stories. This is the most critical service for live production sites.
Signs of issues: Blank content areas on your website, API calls returning 5xx errors, story fetch timeouts, "story not found" errors for published content.
Workaround: Storyblok's CDN caches story data globally. Even during API disruptions, your CDN edge cache often continues serving content. Implement aggressive client-side or framework-level caching. Next.js ISR serves stale cached content automatically.
Management API (mapi)
What it is: The read/write API at mapi.storyblok.com used by the Storyblok editor, CI/CD pipelines, and any programmatic content operations.
Signs of issues: Content saves failing in the visual editor, story creation or update API calls returning errors, import/export pipelines failing.
Workaround: Management API issues do not affect your live website serving CDN content. Delay content publishes and migrations until the incident resolves. Your live site continues running on cached CDN content.
Storyblok App (Visual Editor)
What it is: The browser-based editor at app.storyblok.com where content teams create and edit stories using the visual editing interface.
Signs of issues: app.storyblok.com fails to load, login not working, the visual preview not rendering, component panel not loading.
Workaround: App downtime affects editors only — your live website is unaffected. Editors should wait for the incident to resolve. If urgent, the Management API (if operational) can be used for programmatic content updates.
Image Service
What it is: Storyblok's image transformation service that resizes, crops, and converts images via URL parameters (img2.storyblok.com).
Signs of issues: Images returning 404, 503, or serving the wrong dimensions, transformed image URLs not loading while original source URLs work.
Workaround: Fall back to the original unoptimized image URL. Most image CDN issues are transient. Add a fallback <img> src pointing to original storage URLs in your image components.
App Extensions & Plugins
What it is: Third-party plugins and custom field types loaded within the Storyblok editor environment.
Signs of issues: Custom field types not loading in the editor, plugin UI broken, field validation not running.
Workaround: App extension issues only affect editors in the Storyblok app. Your live website is unaffected since extensions are editor-only tools. Check if the issue is with Storyblok's extension hosting or your own plugin endpoint.
Preview Token vs Published Token: A Common "Outage"
One of the most common Storyblok "outages" that is actually a configuration issue: using the wrong access token. Storyblok has two types:
Preview TokenDevelopment / staging environments
Returns both published and draft content. Use with version=draft for unpublished stories. Never expose in production — returns unpublished content.
Public TokenProduction environments
Returns only published content. Use with version=published (or omit — defaults to published in production). This is the token to use on your live website.
If your production site suddenly shows no content, the first thing to check is whether your environment variable points to a preview token with version=draft — published stories return empty results with draft version in some configurations.
5 Ways to Check Storyblok Status Right Now
Official Storyblok Status Page
Visit status.storyblok.com for component-level real-time status. Subscribe via email or webhook for incident notifications.
status.storyblok.com →API Status Check (Independent Monitor)
APIStatusCheck independently monitors Storyblok endpoints and shows real uptime data. Independent monitoring catches incidents the official status page may not yet reflect.
Check live Storyblok status →Storyblok Discord
The Storyblok Discord server (#support and #general channels) is the fastest source of community incident reports. The Storyblok team actively monitors Discord.
discord.gg/storyblok →Test the CDN API Directly
The most reliable test — skip your framework and query the CDN directly:
curl "https://api.storyblok.com/v2/cdn/stories?token=[your-public-token]&version=published&per_page=1"Status JSON API
Poll the Storyblok Statuspage API for automated monitoring.
curl https://status.storyblok.com/api/v2/status.jsonStoryblok Error Messages During Outages
503Service UnavailableStoryblok API is down or overloaded. Check status.storyblok.com and implement retries with exponential backoff.429Rate LimitedToo many API requests. Not an outage — implement caching and reduce API call frequency. Free tier has lower rate limits than Enterprise plans.401UnauthorizedInvalid or expired access token. Verify your STORYBLOK_ACCESS_TOKEN environment variable and that you are using the correct token for your environment.404 on storyStory Not FoundEither the story slug is wrong, the story is not published (using published token), or the space ID is incorrect. Not an outage.NetworkErrorConnection FailedCDN endpoint is unreachable. Could be a CDN issue — check status.storyblok.com. Also check for local network or DNS issues.CORS errorBrowser BlockClient-side API calls blocked by browser CORS policy. Move API calls server-side or add proper CORS origin configuration. Not an outage.Monitor your Storyblok CDN automatically
Better Stack creates synthetic monitors for your Storyblok Content Delivery API — alerts your team the instant content delivery fails. Free for small teams.
Try Better Stack Free →What to Do When Storyblok Is Down
Immediate Triage
- Check status.storyblok.com for active incidents
- Identify affected service: CDN, Management API, App, or Image Service
- Test your CDN endpoint directly with curl
- Verify access token and version parameter
- Check Storyblok Discord for community confirmation
Engineering Response
- Next.js ISR/SSG automatically serves stale cached content
- Add CDN-level or Redis caching of story API responses
- Implement stale-while-revalidate for story fetches
- Pause non-critical content publishes during incidents
- Fall back to unoptimized image URLs if Image Service fails
Check Storyblok Status Programmatically
# Check overall Storyblok status
curl https://status.storyblok.com/api/v2/status.json# Check individual components (CDN, Management API, App, Image Service)
curl https://status.storyblok.com/api/v2/components.json# Active incidents
curl https://status.storyblok.com/api/v2/incidents/unresolved.json# Direct CDN health check (replace [token] with your public token)
curl "https://api.storyblok.com/v2/cdn/spaces/me?token=[token]" \
-o /dev/null -w "%{http_code}"Storyblok Status vs Sanity Status: Reliability Comparison
Storyblok Reliability Profile
- ✓ CDN-first delivery makes content resilient to API issues
- ✓ status.storyblok.com with component-level tracking
- ✓ CDN, Management API, App, and Image Service tracked separately
- ✓ Enterprise plans include SLA commitments
- ✗ Visual editor downtime can block urgent content changes
Sanity Reliability Profile
- ✓ Content Lake API and Studio tracked independently
- ✓ Open-source — incidents corroborated on GitHub
- ✓ Strong community Slack for incident reports
- ✓ status.sanity.io with per-component breakdown
- ✗ No CDN caching layer by default (requires your own CDN)
For Sanity status, see our Sanity status guide. For Contentful status, see our Contentful status guide.
Frequently Asked Questions
Where is the official Storyblok status page?
Storyblok's official status page is at status.storyblok.com. It shows real-time status for the Content Delivery API (CDN), Management API, the Storyblok App editor, the Image Service, and App Extensions. Subscribe for email or webhook notifications.
Why is Storyblok content not loading on my website?
First, test the CDN directly with curl (bypassing your framework). If content loads via curl but not in your app, the issue is in your code — check your token, version parameter, and space ID. If curl also fails, check status.storyblok.com and the Storyblok Discord.
What is the difference between CDN API and Management API status?
The CDN API (api.storyblok.com/v2/cdn) is CDN-backed and serves published content to your live website. The Management API (mapi.storyblok.com) handles editor saves and programmatic content operations. They run on separate infrastructure — the Management API can be down while CDN continues serving your live site.
Does Storyblok have a status API for programmatic checks?
Yes. Query https://status.storyblok.com/api/v2/status.json for overall status. The indicator field returns none (operational), minor, major, or critical. Use /api/v2/components.json for per-component breakdown.
How do I get alerts when Storyblok goes down?
Subscribe to status.storyblok.com via email or webhook. For production sites, use Better Stack or API Status Check Alert Pro to monitor your CDN endpoint. The Storyblok Discord #support channel is also a fast source of incident reports.
Is Storyblok down for everyone or just me?
Run: curl "https://api.storyblok.com/v2/cdn/spaces/me?token=[your-token]" — a 200 means Storyblok is up and the problem is in your configuration. A 5xx confirms an API issue. Then check status.storyblok.com. Also verify you're not using a preview token in production — this is a very common false-outage scenario.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Storyblok goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Storyblok + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial