Sorry incident

Management UI Performance Degradation

Major Resolved View vendor source →
Started
Apr 22, 2026, 05:54 PM UTC
Resolved
Apr 23, 2026, 12:33 PM UTC
Duration
18h 39m
Detected by Pingoru
Apr 22, 2026, 05:54 PM UTC

Update timeline

  1. resolved Apr 24, 2026, 06:26 PM UTC

    From 17:54 UTC on April 22, our monitoring began detecting degraded performance on the Management UI, with response times increasing above normal levels. Customers may have noticed the Management UI feeling slow or unresponsive between 17:54 UTC on April 22 and 12:33 UTC on April 23. A period of elevated automated traffic placed additional load on our servers, which combined with an existing issue in how we handle slow requests led to a gradual build-up that caused the performance degradation our monitoring detected. **Timeline** - **17:54 UTC, April 22** — Monitoring detects degraded performance and increasing response times - **08:02 UTC, April 23** — Team alerted, investigation begins - **09:37 UTC, April 23** — Servers restarted, normal performance restored - **12:33 UTC, April 23** — Fix applied **What We've Done** - Updated our server configuration to prevent this from recurring - Improved our alerting to ensure our team are notified more promptly of similar degradation - Performance improvements to our most resource-intensive pages are underway We appreciate your patience, and we're sorry for any disruption this may have caused. If you have any questions, please don't hesitate to reach out to our team.

Looking to track Sorry downtime and outages?

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

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

5 free monitors · No credit card required