GetWhys Outage History

GetWhys is up right now

GetWhys had 3 outages in the last 2 years totaling 53m of downtime — averaging 0.1 incidents per month.

There were 3 GetWhys outages since November 18, 2025 totaling 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getwhys.io

Minor May 7, 2026

Elevated Application Errors Due to Database Issues

Detected by Pingoru
May 07, 2026, 02:55 AM UTC
Resolved
May 07, 2026, 02:55 AM UTC
Duration
Affected: App
Timeline · 6 updates
  1. investigating May 07, 2026, 02:05 AM UTC

    Status: Investigating We are investigating an issue affecting database availability that is causing elevated application errors and intermittent failures across parts of the platform. Affected components App (Full outage)

  2. investigating May 07, 2026, 02:11 AM UTC

    Status: Investigating We are currently investigating elevated application errors caused by issues with an upstream infrastructure provider affecting database availability. Some users may experience intermittent failures or delayed background processing while mitigation and recovery efforts are underway. Affected components App (Full outage)

  3. identified May 07, 2026, 02:23 AM UTC

    Status: Identified We are continuing to monitor elevated application errors caused by an upstream infrastructure provider incident affecting database availability. The provider has identified the issue and is implementing a fix. We will share additional updates as recovery progresses. Affected components App (Full outage)

  4. monitoring May 07, 2026, 02:42 AM UTC

    Status: Monitoring We’re seeing signs of recovery following the upstream infrastructure issue affecting database availability. Things are starting to stabilize and error rates are coming down, though we’re continuing to monitor closely while systems fully recover. Affected components App (Full outage)

  5. monitoring May 07, 2026, 02:43 AM UTC

    Status: Monitoring Services have largely recovered following the upstream infrastructure incident and things are looking stable again. We’ll continue monitoring closely. Affected components App (Operational)

  6. resolved May 07, 2026, 02:55 AM UTC

    Status: Resolved The upstream infrastructure incident has been resolved and services are operating normally again. We’ll continue monitoring closely, but all systems currently appear healthy. Affected components App (Operational)

Read the full incident report →

Minor February 19, 2026

Degraded Performance

Detected by Pingoru
Feb 19, 2026, 07:18 PM UTC
Resolved
Feb 19, 2026, 07:18 PM UTC
Duration
Affected: App
Timeline · 2 updates
  1. monitoring Feb 19, 2026, 05:30 PM UTC

    Status: Monitoring We’re currently experiencing authentication disruptions due to an ongoing incident with our auth provider, Clerk. Some users may encounter login failures or session interruptions. We’re actively monitoring the situation and will provide updates as we receive them from . You can follow Clerk’s status here: https://status.clerk.com/incidents/01KHVBF47Q3SDK1VX7ZNHQ316R We’ll share another update as soon as service stability improves. Affected components App (Degraded performance)

  2. resolved Feb 19, 2026, 07:18 PM UTC

    Status: Resolved Auth provider has resolved performance issues Affected components App (Operational)

Read the full incident report →