Instatus had 8 outages in the last 2 years — averaging 0.3 incidents per month.
There were 8 Instatus outages since August 10, 2025. Each is summarised below — incident details, duration, and resolution information.
Type: Incident Duration: 10 minutes Affected Components: Uptime monitoring May 21, 13:10:00 GMT+0 - Identified - We did a faulty release that caused some false monitor alerts to be sent to customers. May 21, 13:20:00 GMT+0 - Resolved - We rolled back, so monitors should be working fine now.
Type: Incident Duration: 24 minutes Affected Components: Private status pages, Dashboard Dec 5, 08:48:00 GMT+0 - Investigating - We faced issues affecting our private pages and dashboard logins caused by a [Cloudflare incident.](https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q) Dec 5, 09:12:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 hour and 46 minutes Affected Components: Incident response, On-call, Slack app, API, Discord, Public status pages, RSS & Atom, Webhooks, Email, Public status pages, Slack, Microsoft Teams, SMS, Dashboard, Maintenance Automations, Google Chat, Private status pages, Uptime monitoring Nov 18, 12:00:00 GMT+0 - Identified - There's an outage in Cloudflare that resulted in a major outage to our API and dashboard. Nov 18, 13:46:23 GMT+0 - Resolved - 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!
Type: Maintenance Duration: 13 minutes Affected Components: Incident response, Slack, On-call, API, Webhooks, Email, Microsoft Teams, Discord, SMS, RSS & Atom, Dashboard, Maintenance Automations, Google Chat, Private status pages, Uptime monitoring, , Notifications → Oct 25, 15:12:48 GMT+0 - Completed - Maintenance has completed successfully. Oct 25, 15:00:00 GMT+0 - Identified - We'll switch our backend and API location to us-east-2 because it's usually more stable. We expect a 10 minute downtime that will affect our dashboard and API. Public status pages will continue to be available for your users.
Type: Incident Duration: 2 hours Affected Components: Incident response, Private status pages, Maintenance Automations Oct 20, 07:35:00 GMT+0 - Identified - 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. Oct 20, 09:35:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 hour and 14 minutes Affected Components: API, RSS & Atom Oct 5, 17:32:27 GMT+0 - Investigating - 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. Oct 5, 18:46:13 GMT+0 - Resolved - This incident has been resolved.
Type: Maintenance Duration: 1 hour and 6 minutes Affected Components: Public status pages, Incident response, Slack, Public status pages, Slack app, On-call, Private status pages, API, Maintenance Automations, Webhooks, Email, Microsoft Teams, Discord, SMS, Google Chat, RSS & Atom, Dashboard, Uptime monitoring Oct 5, 17:06:06 GMT+0 - Completed - Maintenance has completed successfully. Oct 5, 16:00:00 GMT+0 - Identified - We'll be having a data migration in order to improve our performance. We expect no downtime, but we're scheduling this maintenance just in case. Oct 5, 16:00:01 GMT+0 - Identified - Maintenance is now in progress
Type: Incident Duration: 1 hour and 10 minutes Affected Components: Uptime monitoring Aug 10, 14:20:00 GMT+0 - Resolved - Issue is now fixed. We removed the incorrect records added during the incident. Aug 10, 13:10:00 GMT+0 - Identified - We had a buggy release that resulted in checks incorrectly marked as degraded