GetWhys Outage History

GetWhys is up right now

There was 1 GetWhys outage since February 19, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getwhys.io

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 →

Looking to track GetWhys downtime and outages?

Pingoru polls GetWhys's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when GetWhys reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track GetWhys alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring GetWhys for free

5 free monitors · No credit card required