Is Strapi Down?

No — Strapi is up

Reachable from all 8 checked regions

Average response time: 315ms

Last checked 2 hours ago · checks run every 6 hours

Official status page: https://status.strapi.io

Strapi uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

291ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 46 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

46-day clean streak

Sep 10 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

iad

165ms

DNS 115ms TCP 1ms TLS 4ms TTFB 130ms

jnb

1156ms

DNS 122ms TCP 0ms TLS 7ms TTFB 669ms

lax

210ms

DNS 141ms TCP 2ms TLS 4ms TTFB 186ms

lhr

64ms

DNS 42ms TCP 2ms TLS 3ms TTFB 55ms

nrt

531ms

DNS 200ms TCP 31ms TLS 35ms TTFB 406ms

ord

109ms

DNS 29ms TCP 1ms TLS 3ms TTFB 101ms

sin

179ms

DNS 116ms TCP 1ms TLS 4ms TTFB 172ms

sjc

110ms

DNS 88ms TCP 1ms TLS 4ms TTFB 99ms

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.
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. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Strapi goes down

This page refreshes every 6 hours. 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