Unico logo

Is Unico Down?

Identity & AuthLive status, outages, and incident history

No. Unico is up right now.

Every monitored Unico system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment Unico breaks

Unico is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Unico status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Unico Status Summary

As of 18:11 UTC on 14 November 2026, Unico is operational. PulsAPI checked Unico's official status page and found 19 of 19 components operational, with no active incidents. The latest incident, "IDDocs partial outage", was on Nov 5, 2026 and lasted 14 min.

Cite as: PulsAPI, “Unico status”, checked 14 November 2026, 18:11 UTC. https://www.pulsapi.com/services/unico

Unico Component Status

The main Unico systems on this page. All 19 are operational right now.

19operational
1-1 Validation
Operational
Age Verification
Operational
API
Operational

16 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Authentication & Authorization, Document Capture & Reuse, Fraud Risk Classification, Identity Verification, Liveness, Multi-accounts 1-N, Portal, Risk Score, Serpro Similarity, Smart Revalidation, Telephone, Web, and 4 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Unico Outages & Incidents

Incident history from the official Unico status page, including resolution updates.

IDDocs partial outageResolved Nov 5, 2026 · 14 minResolved

The instability affecting our document reuse and saving service has been fully resolved. All systems are operating normally and all metrics have returned to expected levels. The issue was caused by degraded performance in one of our infrastructure components, which impacted document saving operations and service availability between 18:38 and 19:07 BRT on November 5, 2026. We apologize for any inconvenience this may have caused. --- [2026-11-05T22:12:54Z] (monitoring) We have identified and addressed the root cause of the instability affecting our document reuse and saving service. All systems have been restored to normal operation and we are actively monitoring to ensure full stability is maintained. We apologize for any inconvenience this may have caused and will provide a final update once we confirm the issue is fully resolved. --- [2026-11-05T22:11:25Z] (identified) We have identified the root cause of the instability affecting our document reuse and saving service. The issue was caused by degraded performance in one of our infrastructure components, which impacted document saving operations and service availability. Our team has applied the necessary fix and services have been restored to normal operation. We will continue monitoring to ensure full stability. We apologize for any inconvenience this may have caused. --- [2026-11-05T22:03:06Z] (investigating) We have identified an instability in our document reuse and saving service, which may be causing slowness or intermittent failures in this functionality. Our team is already aware and actively working on a resolution. We will update this page as soon as there are any developments. We apologize for the inconvenience.

Instability in IDDocs (document capture) and IDPay (transaction validation)Resolved Nov 4, 2026 · 5h 23mResolved

Dear Customer, The incident affecting IDDocs (document capture and storage) and IDPay (transaction validation) has been resolved, and both capabilities are operating normally. **Executive Summary and Impact** Between 9:43 PM and 11:51 PM (BRT) on November 3, some requests to document capture and storage and to transaction validation experienced slowness or returned errors. **Commitment and Next Steps** A detailed Postmortem will be shared shortly. We are reviewing how this limit can be detected earlier and prevented from affecting our services in the future. We apologize for any inconvenience this may have caused and thank you for your understanding. Unico Team --- [2026-11-04T02:55:15Z] (monitoring) Dear Customer, Our team has completed the corrective actions and the environment is now showing stability. IDDocs and IDPay can be used normally. We are keeping the service under close, assisted monitoring to ensure consistent performance, and our team remains alert to any fluctuation. We will send a final update once the incident is fully resolved. Unico Team --- [2026-11-04T02:34:00Z] (identified) Dear Customer, We have identified an instability in the IDDocs and IDPay capabilities, affecting document capture and storage as well as transaction validation. Some requests may experience slowness or return errors. Our engineering team is already mobilized to diagnose the issue and is working to restore normal operation as quickly as possible. We will send further updates shortly. Unico Team

WhatsApp link delivery failureResolved Nov 2, 2026 · 1h 18mResolved

Dear Customer, **Executive Summary and Impact** On November 2, 2026, between approximately 5:15 PM and 9:09 PM (Brasília time, UTC-3), we identified an instability in the delivery of WhatsApp notifications containing the journey link. During this period, some end users may not have received the link through this channel. The impact affected a minimal portion of customers who use WhatsApp as their notification channel in Brazil. SMS and email notifications, as well as the journey itself, operated normally throughout the period, and there was no data loss. **Root Cause and Resolution** The cause was identified in one of the message templates used to send WhatsApp notifications in Brazil, which stopped being delivered by our partner responsible for sending messages. The other templates continued to operate normally. As a corrective measure, our team migrated notifications for the affected customers to an alternative, previously validated message template, which restored delivery. The service was kept under close monitoring until normalization was confirmed. **Commitment and Next Steps** We continue working with our partner on the definitive fix for the affected message template and on strengthening our notification delivery monitoring to detect this type of failure more quickly. A detailed Postmortem will be shared shortly. We sincerely apologize for the inconvenience and appreciate your understanding. Unico Team --- [2026-11-03T00:19:39Z] (monitoring) Dear Customer, Corrective actions for the instability in the delivery of WhatsApp notifications containing the journey link have been completed, and the environment is now stable. WhatsApp notifications can now be used normally. Our team remains under close monitoring to ensure consistent service and is attentive to any fluctuation. For users who did not receive the link during the instability period, we recommend resending the notification. Further updates will be shared shortly. Unico Team --- [2026-11-02T23:52:50Z] (identified) Dear Customer, We have identified the source of the instability in the delivery of WhatsApp notifications containing the journey link. The cause was traced to a configuration in the message template used by our partner responsible for sending WhatsApp messages. The impact remains limited to a minimal portion of customers who use WhatsApp as their notification channel. Notifications via SMS and email, as well as the journey itself, continue to operate normally. Until service is restored, we recommend using SMS as the notification channel. Status: Under correction Unico Team --- [2026-11-02T23:15:11Z] (investigating) Dear Customer, We have identified an instability in the delivery of WhatsApp notifications containing the journey link, observed from 5:00 PM (Brasília time, UTC-3) today, November 2. The impact affected a minimal portion of customers who use WhatsApp as their notification channel, which may cause some users not to receive the link through this channel. Notifications sent via SMS and email continue to operate normally, as does the journey itself. While the diagnosis is being completed, we recommend using SMS as the notification channel. Our engineering team is already mobilized for the diagnosis, and new updates will be shared shortly. Unico Team

Unico Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Unico incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Unico Outage Reports

Problems reported by engineers using Unico. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Unico problems reported yet.

Something wrong with Unico on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Unico

Unico posts its status at status.unico.io. The page covers 19 components, among them 1-1 Validation, API and Age Verification. Past incidents and uptime for Unico stay on this page, which helps when you want to know how often it has trouble.

Unico Status FAQ

Is Unico down right now?

The verdict at the top of this page comes from the latest poll of the official Unico status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Unico is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Unico recovers.

How do I check Unico uptime history?

PulsAPI tracks Unico uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Unico changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Unico outages?

PulsAPI reads the official Unico status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Unico components?

Yes. PulsAPI monitors 19 individual Unico components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Unico goes down?

Yes. Create a free account and subscribe to Unico: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Unico to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Unico problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Unico?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Unico plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Unico with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services