Live / unico / Incident
unico: Instability/slowness in a small portion of request responses impacting ID product capabilities
unico · unico.ioMajor incidentResolved2026-10-08 20:27 UTC
Public — what happened
Summary
unico reported a major incident beginning at 18:38 UTC on 2026-10-08 in which a small share of requests to its ID product saw intermittent slowness or instability, mostly affecting the Liveness, Risk Score and SDK features, while most requests went through as usual. The company said the problem stemmed from an infrastructure provider and that it was working with that provider to recover. By 18:48 UTC unico said it had taken corrective steps, services were back to normal and it was watching for stability, with a postmortem promised in the following days. The incident was marked resolved at 20:27.
Timeline
- Started — 2026-10-08 18:38 UTC
- Investigating — 2026-10-08 18:38 UTC
- Identified — 2026-10-08 18:47 UTC
- Monitoring — 2026-10-08 18:48 UTC
- Resolved — 2026-10-08 20:27 UTC · 1h 50m 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 unico 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 unico: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the unico report →
More from unico
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.