Live  /  Socure  /  Incident

Socure: [SEV1] Document Verification Decisioning Impacted

Socure · socure.comMajor incidentResolved2026-11-12 05:34 UTC
Public — what happened

Summary

Socure reported a major incident, which it labeled SEV1, affecting how decisions were made in its Document Verification service. The company said it began investigating at 04:49 UTC on 2026-11-12. By 05:05 UTC it said it had put a fix in place to reduce the impact and was watching to confirm the problem was gone. The incident was marked resolved at 05:34, and Socure did not state a cause in the text provided.

Affected

Predictive DocV, Predictive DocV

As listed on Socure’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Socure against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Socure: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Socure report →

More from Socure

Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.

The full archive is on the Socure status & history page.

Related: Socure status & history. SquidGrid is not affiliated with Socure.