Is Storyblok down or not working?

What happened to Storyblok, why did the service go down and not work? Here you can see who else is having the same problem with Storyblok, as well as possible solutions. According to our statistics, the following most often do not work: App, Login, Website.

Current status: No failures

At the moment, according to our data, Storyblok is working fine, but single failures are possible. If Storyblok does not work for you, then report your problem and write a comment.
Add comment

Storyblok outage reports in the last 24 hours

User reports by hour (UTC), last 24 hours

Hour
Weight 0 0 0 0 0 0
Hour
Weight 0 0 0 0 0 0
Hour
Weight 0 0 0 0 0 0
Hour
Weight 0 0 0 0 0 0

Total weight in 24 hours: 0 Busiest hour: 20:00 UTC (weight 0)

How this score compares

Current 24-hour weight is 0. Warnings start at 20, Failed at 50. Median services on this language today is 0.

Other services in this category

Official links

  • Facebook: https://www.facebook.com/1066528693384814
  • Twitter: http://www.twitter.com/storyblok

Facts

Official website storyblok.com
Started 2017
Country worldwide

About Storyblok

Storyblok is a headless content management system that has operated since 2017. It serves customers worldwide and its official website is storyblok.com.
Storyblok is a headless content management system used by teams to build websites and apps. When its platform has an incident, editors may be unable to log in, previews may stop loading, and published content can fail to appear for visitors. This page collects current status details, user reports, and recent history in one place so you can tell whether the problem is on your side or theirs.
Storyblok provides a content platform with an editor, a management API, a delivery API, and a content delivery network. Developers build sites and apps on top of it, while editors write and publish content in the web app. Problems usually fall into a few groups: the editor or login page may be slow or unavailable, the management API may reject changes, or content delivery may return errors and stale entries. Delivery issues often show up as broken pages or missing assets even when the editor still works. Before reporting a problem, check your own connection and try a private browsing window. Confirm your API keys and space settings are unchanged, and test a direct request to the delivery API from your terminal or browser. If a cached response looks stale, a short wait or a cache purge on your side can resolve it. If the platform itself is affected, the incident details and updates will appear here.

Questions

Is Storyblok down right now?

According to reports on this page, Storyblok looks fine for most people. Isolated failures still happen — report yours if you are stuck.

When was the last mass outage?

We do not have a recorded mass outage for Storyblok yet.

Why can I log in to the editor but my website still shows old content?

The editor and the delivery side are separate systems. A content delivery issue can leave your site serving cached or stale pages while editing continues to work. Check the status details here, then try purging your own cache before assuming the platform is at fault.

Do I need a Storyblok account to check the status?

No. This status page is public. You only need an account to work inside the Storyblok editor or to use the APIs.

Storyblok - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.
  • No registration required.
  • Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
  • Active links in the text of the message are not published, but displayed in plain text.
  • It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.