Live / Socure / Incident
Socure: eCBSV Transaction Failure due to high latency
Socure · socure.comMinor incidentResolved2026-09-02 18:58 UTC
Public — what happened
Summary
Socure said its eCBSV module was experiencing slowdowns beginning on 2026-09-02 at 18:31 UTC, which could cause longer response times and failed transactions for customers using it. The company said its vendor, the SSA, had reported the elevated latency as the source of the problem, and that Socure was working with the SSA on a fix. Socure rated the incident as minor, and it was marked resolved on 2026-09-03 at 15:45.
Timeline
- Started — 2026-09-02 18:31 UTC
- Resolved — 2026-09-03 15:45 UTC · 21h 14m 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 37, 2026, our weekly internet health report.