Live / Socure / Incident
Socure: [Sev3] Elevated error rate for RiskOS Evaluation APIs
Socure · socure.comMinor incidentResolved2026-10-17 02:10 UTC
Public — what happened
Summary
Socure said some customers using its RiskOS Evaluate APIs may have seen intermittent errors or failed requests, with the problem reported as beginning at 3:00 EDT on October 16, 2026. The company said it had found a database issue and was working on it. By 21:18 UTC it said an interim measure had stopped the elevated errors, and it moved the incident to monitoring while it worked toward a full fix. Socure's page marks the incident resolved at 02:10 UTC on October 17.
Affected
RiskOS
Timeline
- Started — 2026-10-16 20:20 UTC
- Investigating — 2026-10-16 20:20 UTC
- Monitoring — 2026-10-16 21:18 UTC (2 updates)
- Resolved — 2026-10-17 02:10 UTC · 5h 51m 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.