Skip to main content
Strapi logo

Is Strapi Down?

No — Strapi is up
Strapi's status page
Not available · we could not read it
FlareWarden checks
Website reachable · 8 of 8 regions · 159 ms

Right now

We could not read Strapi's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

strapi.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
159 ms
Checked

By region

  • Amsterdam reachable, 148 ms
  • Chicago reachable, 58 ms
  • Paris reachable, 495 ms
  • San Jose reachable, 61 ms
  • Singapore reachable, 277 ms
  • Stockholm reachable, 69 ms
  • Sydney reachable, 27 ms
  • Toronto reachable, 143 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam119 ms2 ms4 ms138 ms
Chicago29 ms1 ms3 ms50 ms
Paris144 ms1 ms3 ms488 ms
San Jose39 ms2 ms4 ms52 ms
Singapore245 ms3 ms6 ms262 ms
Stockholm50 ms1 ms3 ms60 ms
Sydney10 ms1 ms5 ms23 ms
Toronto58 ms8 ms13 ms108 ms
We check that strapi.io loads, not every feature behind it. Test it yourself

History

Strapi website availability

Measured by FlareWarden · strapi.io

Last 7 days
100%
Last 30 days
100%
Last 90 days
100%
Avg response, 30 days
235ms

Last 30 days

86-day clean streak
Oct 20: 100.00% uptime, 32 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 31 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Nov 6: 100.00% uptime, 32 checks
Nov 7: 100.00% uptime, 32 checks
Nov 8: 100.00% uptime, 32 checks
Nov 9: 100.00% uptime, 32 checks
Nov 10: 100.00% uptime, 32 checks
Nov 11: 100.00% uptime, 32 checks
Nov 12: 100.00% uptime, 32 checks
Nov 13: 100.00% uptime, 32 checks
Nov 14: 100.00% uptime, 32 checks
Nov 15: 100.00% uptime, 32 checks
Nov 16: 100.00% uptime, 32 checks
Nov 17: 100.00% uptime, 32 checks
Nov 18: 100.00% uptime, 8 checks
Oct 20 Today
No downtime Partial Downtime Not measurable No data

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

What Strapi does

Strapi is an MIT-licensed open-source headless CMS that gives developers a content API and an admin panel over their own data model. Strapi Cloud is the managed option, deploying from a GitHub repository with Postgres, a CDN and email included. Most Strapi installations are self-hosted on the customer's own infrastructure, which matters a great deal when reading anything about a Strapi outage.

What an outage looks like

For Strapi Cloud projects, the admin panel at cloud.strapi.io will not load and the content API stops answering, so any front end reading content from it renders empty or errors. Media served through the Assets API fails, leaving broken images on otherwise working pages. Transactional email sent through the Mailer API does not go out. Deployments from GitHub do not build.

What to do about it

Check status.strapi.io, which reports Cloud, the API, the Assets API, the Mailer API, third party services, the strapi.io website and docs.strapi.io as separate rows. If you self-host Strapi, none of these affect your installation. For Cloud projects, a front end holding cached or statically generated content keeps serving readers while the API is unavailable, so check how your site fetches content before treating this as urgent.

Is it down for everyone, or just you?

If this page says Strapi 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

Strapi outage FAQ

Is my self-hosted Strapi affected by a Strapi Cloud outage?
No. Strapi is MIT-licensed open source and runs on your own servers when self-hosted, with full control over data residency; the same codebase powers both options. An incident on status.strapi.io covers Strapi Cloud and Strapi's own web properties. If you deployed Strapi yourself, your content API is unaffected and the status page is not describing your system.
Why are images broken but the text is fine?
Because the Assets API is a separate component from the main API. Content can be delivered while media files are not, which renders a page with all its text and none of its pictures. The status page lists Cloud, API, Assets API and Mailer API individually, so this is a distinguishable failure rather than a general outage of everything.
Does an outage affect a site already built from Strapi content?
Only if the site fetches content at request time. A front end that statically generates pages at build time already holds the content and keeps serving it, and readers see nothing wrong. A site that calls the Strapi API on every request has nothing to render. This is the single biggest factor in how much a Strapi Cloud incident actually costs you.
Will a deployment I pushed during the incident go out?
Strapi Cloud deploys from a GitHub repository, so a push made during an incident may not build until the platform recovers. The commit is safe in the repository either way. Check the Cloud row on the status page before re-triggering, since pushing repeatedly to force a build adds queued work rather than getting ahead of the backlog.

How we measure this

  • We request Strapi'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 Strapi 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 Strapi 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. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when Strapi goes down

We check Strapi 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