Live  /  unico  /  Incident

unico: Instability in IDDocs (document capture) and IDPay (transaction validation)

unico · unico.ioMajor incidentResolved2026-11-04 06:06 UTC
Public — what happened

Summary

unico reported a major incident beginning at 02:30 UTC on 2026-11-04 that affected its IDDocs and IDPay services, which handle document capture and storage and transaction validation. The company said some requests could be slow or return errors, and that its engineers were working on the problem. By 02:55 UTC unico said it had finished corrective actions, that both services were stable and usable, and that it was monitoring them closely. The incident was marked resolved at 06:06.

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 unico 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 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 46, 2026, our weekly internet health report.

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

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