Outage report · Major outage

Socure outage on Feb 25, 2026

[RETROACTIVE SEV2] - All Web Capture App impacted by "Session Expired" errors during capture links

SeverityMajor outage

StartedFeb 25, 2026, 15:30UTC

ResolvedFeb 25, 2026, 17:08UTC

Duration1h 39m

What happened

Socure reported a major outage starting Feb 25, 2026, 15:30 UTC, affecting Predictive DocV, Predictive DocV. It was marked resolved at Feb 25, 2026, 17:08 UTC.

The incident lasted 1h 39m from first report to resolution.
Socure had reported no other partial or major outages in the 90 days before it.
7 other vendors we track reported a significant incident within 12 hours of it.

Latest update from Socure

**Root Cause Analysis:** **Incident: DocV Capture App Production Environment Mismatch \(DR Build\)** **Date Range:** February 25, 2026 **Impact: 35% error rate; Production Capture App served DR endpoints, causing "Session Expired" errors due to CSP blocks.** **Summary:** On February 25, 2026, between 10:34 AM EST and 12:26 PM EST, the DocV Capture App experienced a service degradation where **35% of sessions failed.** The incident was triggered when a build intended for a Disaster Recovery \(DR\) test was uploaded to a DR S3 bucket. An undocumented replication rule automatically propagated this DR configuration into the Production S3 bucket. Consequently, the production application attempted to communicate with DR endpoints, which were blocked by the Production Content Security Policy \(CSP\), resulting in "Session Expired" errors for end users. **Timeline:** | **Date / Time \(ET\)** | **Event** | | --- | --- | | 09:58 AM | DR-specific build published to DR S3 bucket \(PLT-6791\

Read Socure's official incident report ↗