Live / Socure / Incident
Socure: [SEV3] - eCBSV API Outage Resulting in 5xx Errors
Socure · socure.comMinor incidentResolved2026-10-15 15:59 UTC
Public — what happened
Summary
Socure reported a minor unplanned outage on October 15, 2026, starting at 14:52 UTC, in which its eCBSV module returned 5xx server errors. The company attributed the problem to responses coming from the SSA and said it had reached out to its vendor to look into it. Within a few minutes Socure said error rates had dropped and it was watching them while awaiting word from the vendor. The incident was marked resolved at 15:59 UTC the same day.
Affected
eCBSV, eCBSV
Timeline
- Started — 2026-10-15 14:52 UTC
- Identified — 2026-10-15 14:52 UTC
- Monitoring — 2026-10-15 14:55 UTC
- Resolved — 2026-10-15 15:59 UTC · 1h 07m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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 43, 2026, our weekly internet health report.