Instatus Outage History

Instatus is up right now

Pingoru has recorded 52 incidents for Instatus: 7 in the last 12 months and 0 in the last 90 days.

Source: instat.us

52incidents recorded
7last 12 months
0last 90 days
21 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Instatus in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202620 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 515 (0%)

Incidents, newest first

Minor May 21, 2026 False monitor alerts 10m

Started May 21, 2026, 01:10 PM UTC· resolved May 21, 2026, 01:20 PM UTC

  1. identified May 21, 2026, 01:10 PM UTC

    We did a faulty release that caused some false monitor alerts to be sent to customers..

  2. resolved May 21, 2026, 01:20 PM UTC

    We rolled back, so monitors should be working fine now..

Read the full incident report →

Minor December 5, 2025 Issues with login to our private pages and dashboard 24m

Started Dec 05, 2025, 08:48 AM UTC· resolved Dec 05, 2025, 09:12 AM UTC

  1. investigating Dec 05, 2025, 08:48 AM UTC

    We faced issues affecting our private pages and dashboard logins caused by a [Cloudflare incident.](https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q).

  2. resolved Dec 05, 2025, 09:12 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor November 18, 2025 Issues accessing our dashboard and private status pages 1h 46m

Started Nov 18, 2025, 12:00 PM UTC· resolved Nov 18, 2025, 01:46 PM UTC

  1. identified Nov 18, 2025, 12:00 PM UTC

    There's an outage in Cloudflare that resulted in a major outage to our API and dashboard. .

  2. resolved Nov 18, 2025, 01:46 PM UTC

    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!.

Read the full incident report →

Minor October 25, 2025 Switching our AWS region – Instatus

Started Oct 25, 2025, 03:00 PM UTC· resolved Oct 25, 2025, 03:00 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major October 20, 2025 Outages with some of our services 2h

Started Oct 20, 2025, 07:35 AM UTC· resolved Oct 20, 2025, 09:35 AM UTC

  1. identified Oct 20, 2025, 07:35 AM UTC

    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..

  2. resolved Oct 20, 2025, 09:35 AM UTC

    This incident has been resolved..

Read the full incident report →

Major October 5, 2025 Unavailable RSS & JSON endpoints 1h 13m

Started Oct 05, 2025, 05:32 PM UTC· resolved Oct 05, 2025, 06:46 PM UTC

  1. investigating Oct 05, 2025, 05:32 PM UTC

    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..

  2. resolved Oct 05, 2025, 06:46 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor October 5, 2025 Data migration –

Started Oct 05, 2025, 04:00 PM UTC· resolved Oct 05, 2025, 04:00 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor August 10, 2025 Incorrect degraded checks 1h 10m

Started Aug 10, 2025, 01:10 PM UTC· resolved Aug 10, 2025, 02:20 PM UTC

  1. identified Aug 10, 2025, 01:10 PM UTC

    We had a buggy release that resulted in checks incorrectly marked as degraded.

  2. resolved Aug 10, 2025, 02:20 PM UTC

    Issue is now fixed. We removed the incorrect records added during the incident..

Read the full incident report →

Minor June 12, 2025 Some issues with SSO auth and Directory Sync 49m

Started Jun 12, 2025, 07:13 PM UTC· resolved Jun 12, 2025, 08:03 PM UTC

  1. identified Jun 12, 2025, 07:13 PM UTC

    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..

  2. resolved Jun 12, 2025, 08:03 PM UTC

    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/)..

Read the full incident report →

Major April 29, 2025 Outage affecting dashboard and API 10m

Started Apr 29, 2025, 05:15 PM UTC· resolved Apr 29, 2025, 05:25 PM UTC

  1. identified Apr 29, 2025, 05:15 PM UTC

    We had an issue affecting your ability to update your status pages via the dashboard or API. Private pages were also affected..

  2. resolved Apr 29, 2025, 05:25 PM UTC

    Sorry for the trouble. Issue is now resolved! .

Read the full incident report →

Minor April 20, 2025 Data migration (2) –

Started Apr 20, 2025, 09:00 PM UTC· resolved Apr 20, 2025, 09:00 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 19, 2025 Planned data migration –

Started Apr 19, 2025, 09:00 PM UTC· resolved Apr 19, 2025, 09:00 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor March 3, 2025 Dashboard not available 10m

Started Mar 03, 2025, 03:20 PM UTC· resolved Mar 03, 2025, 03:30 PM UTC

  1. identified Mar 03, 2025, 03:20 PM UTC

    We are continuing to work on a fix for this incident..

  2. resolved Mar 03, 2025, 03:30 PM UTC

    It's now been resolved. Was due to a project transfer that went wrong..

Read the full incident report →

Minor November 10, 2024 Issue with accessing subdomains of public pages 14m

Started Nov 10, 2024, 05:55 PM UTC· resolved Nov 10, 2024, 06:09 PM UTC

  1. monitoring Nov 10, 2024, 05:55 PM UTC

    We implemented a fix and are currently monitoring the result..

  2. resolved Nov 10, 2024, 06:09 PM UTC

    Issue should be fixed now. It was caused by faulty transfer of project on our frontend provider..

Read the full incident report →