Outage report · Major outage

Shepherd outage on Feb 26, 2026

Shepherd Application System Outage

SeverityMajor outage

StartedFeb 26, 2026, 20:45UTC

ResolvedFeb 26, 2026, 21:44UTC

Duration59m

What happened

Shepherd reported a major outage starting Feb 26, 2026, 20:45 UTC, affecting Shepherd Application. It was marked resolved at Feb 26, 2026, 21:44 UTC.

The incident lasted 59m from first report to resolution.
It was the 3rd longest of 4 significant outages Shepherd reported in the 12 months up to it.
Shepherd had reported 1 other partial or major outage in the 90 days before it.
1 other vendor we track reported a significant incident within 12 hours of it.

Latest update from Shepherd

## Summary On February 25 and February 26, Shepherd experienced two separate production outages during peak business hours. Both incidents resulted in full application unavailability, including intermittent access to Read-Only mode. * **February 25:** 2:32pm–3:12pm ET \(~40 minutes\) * **February 26:** 3:32pm–4:42pm ET \(~70 minutes from first degradation to full stabilization; primary instability ~27 minutes\) While the timing overlapped with release activity, both incidents were the result of resource exhaustion and thread pool starvation within our production environment under peak load conditions. ## February 25 ### What Happened At 2:32pm ET on February 25, production application servers became unresponsive within seconds of each other. The application did not crash from an exception; instead, worker processes froze and stopped responding to health checks. As threads became blocked and connection pools were exhausted, the system stopped accepting new requests. This created

Read Shepherd's official incident report ↗