Instatus had 18 outages in the last 2 years — averaging 0.7 incidents per month.
There were 18 Instatus outages since June 26, 2024. 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
Type: Incident Duration: 49 minutes Affected Components: Private status pages, Dashboard Jun 12, 20:03:00 GMT+0 - Resolved - 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/). Jun 12, 19:13:40 GMT+0 - Identified - 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.
Type: Incident Duration: 10 minutes Affected Components: Public status pages, Private status pages, Dashboard, Maintenance Automations, Discord, Google Chat, Slack, Webhooks, SMS, RSS & Atom, Microsoft Teams, Email, API Apr 29, 17:25:00 GMT+0 - Resolved - Sorry for the trouble. Issue is now resolved! Apr 29, 17:15:00 GMT+0 - Identified - We had an issue affecting your ability to update your status pages via the dashboard or API. Private pages were also affected.
Type: Maintenance Duration: 10 minutes Affected Components: Public status pages, Private status pages, Dashboard, Maintenance Automations, Discord, Google Chat, Slack, Webhooks, SMS, RSS & Atom, Microsoft Teams, Email, API Apr 20, 21:00:00 GMT+0 - Identified - We're planning a data migration during the weekend. Status pages will continue to be accessible, but you won't be able to do updates during the migration. Apr 20, 21:10:00 GMT+0 - Completed - Maintenance is now complete! Apr 20, 21:00:01 GMT+0 - Identified - Maintenance is now in progress
Type: Maintenance Duration: 29 minutes Affected Components: Public status pages, Private status pages, Dashboard, API, Maintenance Automations, Discord, Google Chat, Slack, Webhooks, SMS, RSS & Atom, Microsoft Teams, Email Apr 19, 21:28:37 GMT+0 - Completed - Maintenance is completed successfully. Thank you for your patience! Apr 19, 21:00:00 GMT+0 - Identified - We're doing an update during the weekend that requires data migration. We expect a downtime of 10 minutes on updates only. Status pages will continue to be available, but you won't be able to update them until maintenance ends. Apr 19, 21:00:01 GMT+0 - Identified - Maintenance is now in progress
Type: Incident Duration: 10 minutes Affected Components: Dashboard Mar 3, 15:30:00 GMT+0 - Resolved - It's now been resolved. Was due to a project transfer that went wrong. Mar 3, 15:20:00 GMT+0 - Identified - We are continuing to work on a fix for this incident.
Type: Incident Duration: 14 minutes Affected Components: Public status pages Nov 10, 18:09:00 GMT+0 - Resolved - Issue should be fixed now. It was caused by faulty transfer of project on our frontend provider. Nov 10, 17:55:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result.
Type: Incident Duration: 15 minutes Affected Components: Dashboard Sep 26, 15:40:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Sep 26, 15:55:00 GMT+0 - Resolved - The issue has been resolved!
Type: Incident Duration: 27 minutes Affected Components: Public status pages, Private status pages Aug 7, 19:24:00 GMT+0 - Resolved - Everything should be working now! Aug 7, 19:54:03 GMT+0 - Postmortem - Seems like all services are back to normal. Here's our provider's [incident. ](https://www.vercel-status.com/incidents/f6b2blrl5f5f)We're sorry for the downtime. In the upcoming days, we'll investigate alternatives that we can switch to in case this happens in the future. Aug 7, 19:29:00 GMT+0 - Monitoring - Services became unavailable again Aug 7, 19:43:00 GMT+0 - Resolved - Issue was resolved again Aug 7, 19:18:00 GMT+0 - Monitoring - All our components were unavailable due to an outage with our frontend hosting provider.
Type: Incident Duration: 1 hour and 30 minutes Affected Components: Dashboard, Private status pages Jul 16, 07:00:00 GMT+0 - Resolved - Issue is now resolved Jul 16, 05:30:00 GMT+0 - Monitoring - We did a faulty release that resulted in problems with new logins to Instatus dashboard as well as status pages.
Type: Incident Duration: 1 hour and 55 minutes Affected Components: Private status pages Jun 26, 05:15:00 GMT+0 - Investigating - We had an issue were many private pages were returning 404 Not found page Jun 26, 07:10:00 GMT+0 - Resolved - This was resolved earlier. This likely happened because of our frontend hosting provider. We're still investigating it with them.