Vendor record
Strapi
Checked
Front door check counts and Strapi’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We have no front door checks against Strapi in the last 30 days. That does not show whether it was reachable.
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Strapi product, region or your app worked.
How we count front door checksStrapi says
Incident posts from Strapi’s status page, with its titles, impact levels and times. They say what Strapi chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
6
incidents Strapi posted, last 90 days
Median recorded duration: 50m. From 6 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Some projects may be unavailable
Not specifiedStrapi’s postStarted, per Strapi
Closed in our record(1h)
Backups temporarily unavailable in the dashboard
Not specifiedStrapi’s postStarted, per Strapi
Closed in our record(1h 26m)
Third party services went down
MajorStarted, per Strapi
Closed in our record(34m)
Third party services went down
MinorStarted, per Strapi
Closed in our record(23m)
Projects unavailable following a redeployment
Not specifiedStrapi’s postStarted, per Strapi
Closed in our record(50m)
5 older records
Compute provider deployment outage
Not specifiedStrapi’s postStarted, per Strapi
Closed in our record(9h)
Deployment failures
Not specifiedStrapi’s postStarted, per Strapi
Closed in our record(14h 44m)
Delayed / Failed API responses
Not specifiedStrapi’s postStarted, per Strapi
Closed in our record(26m)
Project creation unavailable
Not specifiedStrapi’s postStarted, per Strapi
Closed in our record(1h 15m)
Issues with Login with Magic Link
Not specifiedStrapi’s postStarted, per Strapi
Closed in our record(14h 38m)
Your code, your dependencies
See which of your code paths call Strapi
Connect GitHub or GitLab to find where your public or private repository uses Strapi. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Strapi status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Strapi currently down?
Strapi's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Strapi last have an outage?
The most recent closed incident record began 35 days ago and spans 1 hour. The vendor reported an incident. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Strapi?
No. CheckUpstream does not run front door checks against Strapi. The incident history on this page is what Strapi reported, not a measure of how often it was available.
How do I monitor Strapi in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Strapi?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.