Instatus had 14 outages in the last 2 years totaling 8h 7m of downtime — averaging 0.6 incidents per month.
There were 14 Instatus outages since November 10, 2024 totaling 8h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.
We did a faulty release that caused some false monitor alerts to be sent to customers..
We rolled back, so monitors should be working fine now..
We faced issues affecting our private pages and dashboard logins caused by a [Cloudflare incident.](https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q).
This incident has been resolved..
There's an outage in Cloudflare that resulted in a major outage to our API and dashboard. .
We re-routed from Cloudflare, and now our services should be accessible. We'll make sure we have a quicker system of re-routing in the future. Sorry for the outage!.
We faced issues with some of our services, including scheduled maintenance periods, private status pages, and adding incidents for some customes. This was caused by outages to our providers including AWS and Vercel..
This incident has been resolved..
Public endpoints like /rss, /atom, /components.json, etc are unavailable due to a faulty release. We're currently fixing it and we will update you..
This incident has been resolved..
We had a buggy release that resulted in checks incorrectly marked as degraded.
Issue is now fixed. We removed the incorrect records added during the incident..
There's a current issue with our upstream provider, WorkOS. Here's their [incident report.](https://status.workos.com/incidents/k9s870cktcsf) We use it for login via SSO as well as Directory Sync..
The issue is now resolved by them applying a fix that mitigated their upstream outage. Please feel free to continue monitoring [their incident](https://status.workos.com/)..
We had an issue affecting your ability to update your status pages via the dashboard or API. Private pages were also affected..
Sorry for the trouble. Issue is now resolved! .
We are continuing to work on a fix for this incident..
It's now been resolved. Was due to a project transfer that went wrong..
We implemented a fix and are currently monitoring the result..
Issue should be fixed now. It was caused by faulty transfer of project on our frontend provider..