All Systems Operational

Uptime over the past 90 days. View historical uptime.
IDCloud | Risk Score Operational
90 days ago
99.98 % uptime
Today
API Operational
90 days ago
99.98 % uptime
Today
IDCloud | Identity Verification Operational
90 days ago
99.97 % uptime
Today
API Operational
90 days ago
99.97 % uptime
Today
Liveness Operational
90 days ago
99.98 % uptime
Today
API Operational
90 days ago
99.98 % uptime
Today
IDCloud | Electronic Signature Operational
90 days ago
99.93 % uptime
Today
API Operational
90 days ago
99.93 % uptime
Today
IDCloud | Document Reuse and Capture Operational
90 days ago
99.99 % uptime
Today
API Operational
90 days ago
99.99 % uptime
Today
IDCloud | Portal Operational
90 days ago
99.96 % uptime
Today
ID Portal Operational
90 days ago
99.96 % uptime
Today
IDCloud - Web Journey Operational
90 days ago
99.94 % uptime
Today
API Operational
90 days ago
99.92 % uptime
Today
Messaging System Operational
90 days ago
99.95 % uptime
Today
IDCloud - API/Native Journey Operational
90 days ago
99.97 % uptime
Today
SDK Operational
90 days ago
99.97 % uptime
Today
ID Cloud | Fraud Risk Classification Operational
90 days ago
99.98 % uptime
Today
IDTrust | API Operational
90 days ago
99.98 % uptime
Today
IDCloud - Serpro Similarity Return (Brazil) Operational
90 days ago
100.0 % uptime
Today
ID Serpro (API) Operational
90 days ago
100.0 % uptime
Today
ID Cash Operational
90 days ago
100.0 % uptime
Today
API ID Cash Operational
90 days ago
100.0 % uptime
Today
Card Not Present (ID Pay - Brazil) Operational
90 days ago
99.97 % uptime
Today
API Operational
90 days ago
99.93 % uptime
Today
ID PAY Portal Operational
90 days ago
100.0 % uptime
Today
Messaging System Operational
90 days ago
99.98 % uptime
Today
Unico People Operational
90 days ago
99.98 % uptime
Today
Análise Operational
90 days ago
100.0 % uptime
Today
Portal Cliente (Dashboard) Operational
90 days ago
99.96 % uptime
Today
API Operational
90 days ago
100.0 % uptime
Today
Módulo Benefícios Operational
90 days ago
100.0 % uptime
Today
Notificações Operational
90 days ago
99.99 % uptime
Today
Módulo Candidato Operational
90 days ago
99.99 % uptime
Today
Assinatura Eletrônica Operational
90 days ago
99.92 % uptime
Today
Fluxo de mensagens Operational
90 days ago
100.0 % uptime
Today
Unico People - Sign Operational
90 days ago
99.99 % uptime
Today
Assinatura Eletrônica no API - Unico Sign Operational
90 days ago
99.99 % uptime
Today
Unico Doc Operational
90 days ago
100.0 % uptime
Today
Portal Client (plataforma) Operational
90 days ago
100.0 % uptime
Today
Notificações Operational
90 days ago
100.0 % uptime
Today
Unico Skill Operational
90 days ago
100.0 % uptime
Today
Unico Skill Operational
90 days ago
100.0 % uptime
Today
Support Channels Operational
90 days ago
99.95 % uptime
Today
Phone Support Operational
90 days ago
100.0 % uptime
Today
Whatsapp Operational
90 days ago
99.86 % uptime
Today
Chatbot Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

Scheduled Maintenance Infrastructure - August 6th, 01:00 AM - 03:00 AM (BRT) Aug 6, 2026 01:00-03:00 GMT-03:00

Dear Customer,

At Unico, we work continuously to ensure maximum performance, stability, and security in all your journeys. To honor this commitment, it is essential that our infrastructure remains up to date and prepared with total resilience.

We are writing to inform you that on August 6th, 2026 (Thursday), between 01:00 AM and 03:00 AM (Brasília Time / BRT), we will perform scheduled maintenance on our database infrastructure. This maintenance is crucial for Unico's infrastructure compliance.

Although the total maintenance window is 2 hours, the expected downtime (unavailability) is brief—estimated at 30 seconds per capacity, totaling a maximum of 15 minutes overall, between 01:00 AM and 01:15 AM (BRT). During this specific period, requests may return an HTTP 500 error.

We would like to reassure you that our engineering team will be on standby throughout the entire window. Should any severe anomalous behavior occur outside of what is expected, we have an immediate rollback plan in place to restore service stability within seconds.

Sincerely, Unico Team
Posted on Aug 03, 2026 - 16:39 GMT-03:00

Aug 4, 2026

No incidents reported today.

Aug 3, 2026

No incidents reported.

Aug 2, 2026

No incidents reported.

Aug 1, 2026

No incidents reported.

Jul 31, 2026

Instabilidade people-sign
Resolved - Prezados clientes,

Informamos que o incidente relacionado à exibição de envios no painel de acompanhamento foi oficialmente encerrado.

Após a aplicação da correção e o período de monitoramento, confirmamos que a listagem e o histórico de documentos foram totalmente restabelecidos, e a plataforma opera em completa estabilidade.

Agradecemos pela compreensão e paciência de todos durante o processo.

Atenciosamente,
Jul 31, 11:06 GMT-03:00
Monitoring - Prezados clientes,

Informamos que a correção para a exibição no painel de acompanhamento foi aplicada com sucesso.

A lista de documentos e históricos de envios já está retornando à normalidade. No momento, nossa equipe de engenharia está monitorando o ambiente de perto para garantir a estabilidade total do serviço.

Agradecemos a paciência e traremos a confirmação do encerramento em breve.

Atenciosamente,
Jul 31, 10:20 GMT-03:00
Identified - Prezados clientes,

Gostaríamos de atualizar o status sobre a visualização de documentos no painel de acompanhamento.

O problema foi identificado com sucesso por nossa equipe técnica. No momento, os engenheiros já estão subindo a correção para restabelecer a exibição correta de todos os envios na interface do remetente.

Lembramos que o processamento, envio e assinatura dos documentos continuam operando normalmente.

Volataremos com uma nova atualização assim que a correção for concluída e entrarmos na fase de monitoramento.

Atenciosamente,
Jul 31, 10:08 GMT-03:00
Investigating - Prezados clientes,

Identificamos uma instabilidade técnica pontual que afeta a atualização do painel de acompanhamento após o envio de documentos.

Reforçamos que o fluxo de envio e assinatura está funcionando normalmente: os destinatários continuam recebendo e conseguindo assinar os arquivos. No entanto, o registro do envio pode temporariamente não ser exibido na lista de acompanhamento do remetente.

Nossa equipe de engenharia já está atuando para corrigir a exibição na interface e restabelecer o histórico no painel o mais breve possível.

Pedimos desculpas pelo inconveniente e manteremos todos informados sobre o progresso.

Atenciosamente,
Jul 31, 09:42 GMT-03:00

Jul 30, 2026

No incidents reported.

Jul 29, 2026

Webhook Instability Impacting ID Cloud Capabilities
Resolved - Executive Summary & Impact
We would like to inform you that the incident temporarily affecting the ID Cloud Webhook notification service has been resolved.

Impact Period: From 08:32 to 10:05.
Platform Impact: The instability was strictly limited to Webhook notification delivery, resulting in a delay in message distribution. There was no degradation of the main platform, no failures in the liveness engine, and no data loss.
Customer Impact: The issue affected a small portion of customers. Clients who have implemented a GET polling flow as a contingency (fallback) experienced no downtime or operational impact.


Root Cause & Resolution

Root Cause: The instability was triggered by a feature update in the environment. A temporary mismatch in access permissions between the task queue and the destination route caused requests to be denied, leading to a temporary backlog of notifications.
Resolutive Action: The technical team completed the traffic redirection to the new environment, restoring proper communication between components and releasing the backlog of Webhooks. Processing has returned to normal, and the dispatch queue has been fully cleared.


Commitment & Next Steps
The stability of our services is our highest priority. To ensure total transparency and prevent recurrence, our engineering team will focus on the following fronts:

Detailed Postmortem: A comprehensive report featuring an in-depth root cause analysis and a preventive action plan will be prepared.
Observability Improvements: We will adjust monitoring metrics to ensure greater visibility into inter-service communication errors during transition scenarios.
We sincerely apologize for the inconvenience and remain available for any further clarifications.
Sincerely, Unico Team
Jul 29, 08:00 GMT-03:00

Jul 28, 2026

Scheduled Maintenance - Infrastructure - July 28th - 01:00 AM to 03:00 AM (BRT)
Completed - The scheduled maintenance has been completed.
Jul 28, 03:00 GMT-03:00
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 28, 01:00 GMT-03:00
Scheduled - Dear Customer,

At Unico, we continuously work to ensure maximum performance, stability, and security across all your journeys. To fulfill this commitment, it is essential that our infrastructure remains up to date and fully prepared with complete resilience.

Please be advised that on July 28, 2026 (Tuesday), between 01:00 AM and 03:00 AM (BRT / Brasília Time), we will perform scheduled maintenance on our database infrastructure. This maintenance is crucial to ensure the compliance of Unico’s infrastructure.

Although the total maintenance window is 2 hours, the expected downtime is short, estimated to last from 30 seconds to a maximum of 15 minutes between 01:00 AM and 01:15 AM (BRT). During this specific timeframe, requests may return an HTTP 500 error.

We emphasize that our engineering team will be on standby throughout the entire window. Should any severe anomalous behavior occur outside of what is expected, we have an immediate rollback plan to restore service stability within seconds.

Sincerely,

Unico Team
Jul 21, 15:22 GMT-03:00

Jul 27, 2026

No incidents reported.

Jul 26, 2026

No incidents reported.

Jul 25, 2026

No incidents reported.

Jul 24, 2026

Instability in our Webhooks that is affecting latency in data delivery
Postmortem - Read details
Aug 3, 17:11 GMT-03:00
Resolved - Executive Summary and Impact

Starting at 6:05 PM (Brasília time), an instability occurred in the Webhook service, leading to failure in event processing and notification delivery for affected operations during this period.


Root Cause and Resolution

The incident was caused by an issue with a shared Service Account used across multiple services, resulting in authentication failures.

Upon identifying the root cause, the engineering team restored the required credentials and configuration. Normal operation was fully re-established at 6:29 PM (BRT).


Commitment and Next Steps

As part of continuous improvement and risk mitigation, the engineering team will review resource dependencies and access management across services. This will prevent similar configuration issues in future infrastructure adjustments.
Jul 24, 19:18 GMT-03:00
Monitoring - Dear Customer,

Our engineering team has identified and implemented the necessary actions to resolve the Webhook instability affecting data delivery latency.

At this time, the technical team is conducting a detailed analysis of our data layer and continues to monitor the environment.

We reiterate that further updates will be sent shortly.
Jul 24, 18:53 GMT-03:00
Investigating - Dear Customer,

We are currently investigating an instability in our Webhooks that is affecting latency in data delivery.
Our engineering team is actively working to resolve the issue as quickly as possible.

We will provide further updates shortly.
Jul 24, 18:47 GMT-03:00

Jul 23, 2026

No incidents reported.

Jul 22, 2026

No incidents reported.

Jul 21, 2026

Instability affecting ID CLOUD capabilities
Postmortem - Read details
Aug 3, 11:36 GMT-03:00
Resolved - Executive Summary and Impact

Starting at approximately 12:44 PM (Brasília time) on July 21, 2026, a portion of users in the reduced onboarding journey experienced slower loading of the initial screens in the flow. The impact was observed across all environments where this journey is used, affecting perceived speed and, to a lesser extent, users' ability to complete the process during this period.

Root Cause and Resolution

The investigation is ongoing to confirm the definitive root cause of the incident. There was no impact on servers, network, or infrastructure — the issue was confirmed to be isolated to the on-screen experience on the user's device. As a containment measure, the responsible team applied a preventive adjustment at 1:39 PM (BRT), and loading times returned to normal within a few minutes. The analysis to validate and confirm the root cause is still being conducted by the technical team.

Commitment and Next Steps

As part of the continuous improvement of incident response processes, the team commits to enhancing the automatic escalation flow for responsible teams, making activation even more direct and effective from the moment an incident is opened. Additionally, loading-speed monitoring will be strengthened during the rollout of new changes to this journey, with the goal of identifying and correcting potential regressions even faster, minimizing impact to users in similar situations going forward.
Jul 21, 15:02 GMT-03:00
Monitoring - Dear Customer,

Our engineering team has identified and implemented the necessary actions to resolve the instability in the affected IDCloud flow capabilities.

At this time, the technical team is conducting a detailed analysis of our data layer and continues to monitor the environment.

We reiterate that further updates will be sent shortly.
Jul 21, 13:49 GMT-03:00
Identified - Dear customer,

We are investigating an instability in the IDCloud functionalities that affects the authentication flows in the process journey, specifically impacting the Web Journey (formerly ByUnico).

Our engineering team is mobilized to resolve the issue as soon as possible.
We will provide further updates shortly.
Jul 21, 13:39 GMT-03:00
Instability affecting ID CLOUD capabilities
Postmortem - Read details
Jul 28, 09:20 GMT-03:00
Resolved - Executive Summary and Impact
On July 21, 2026, at around 11:17 AM BRT, a drop in availability was detected in the IDCloud create-process and process-query flows. During the impact window, a portion of customers experienced elevated latency and failures (timeouts) in these operations, which propagated through the chain of dependent services. The effective impact was concentrated in a window of approximately 23 minutes. At peak, error and latency indicators were above normal operating levels.

Root Cause and Resolution
The investigation pointed to the degradation of a read database (replica) supporting these capabilities as the origin. This database began to show increased load and query execution time, with internal contention that stalled processing and backed up read requests. As a result, the services above it started accumulating timeouts and triggering protection mechanisms (circuit breakers), producing the cascading effect experienced by customers.

Commitment and Next Steps
Unico is handling this incident with a detailed postmortem, already being drafted, and will hold a post-incident review (PiR) meeting to consolidate preventive actions. Among the follow-ups already raised during the response are the preparation of diagnostic routines and queries to speed up the identification of contention in this database layer, and improved observability over the databases involved. The detailed preventive actions will be shared in the postmortem.

We reaffirm our commitment to the stability and reliability of the platform and apologize for the inconvenience caused during the period of instability.

Unico Team.
Jul 21, 13:00 GMT-03:00
Monitoring - Dear Customer,

Our engineering team has identified and implemented the necessary actions to resolve the instability in the affected IDCloud flow capabilities.

At this time, the technical team is conducting a detailed analysis of our data layer and continues to monitor the environment.

We reiterate that further updates will be sent shortly.
Jul 21, 11:50 GMT-03:00
Update - We are continuing to work on a fix for this issue.
Jul 21, 11:46 GMT-03:00
Identified - Dear customer,

We are investigating an instability in our IDCloud capabilities, affecting the process creation and process details flows. Our engineering team is mobilized to resolve the issue as soon as possible. We will provide further updates shortly.
Jul 21, 11:30 GMT-03:00
Scheduled Maintenance - Infrastructure - July 21st - 01:00 AM to 02:00 AM (BRT)
Completed - The scheduled maintenance has been completed.
Jul 21, 02:00 GMT-03:00
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 21, 01:00 GMT-03:00
Scheduled - Dear Customer,

At Unico, we continuously work to ensure maximum performance, stability, and security across all your journeys. To fulfill this commitment, it is essential that our infrastructure remains fully updated and prepared with total resilience.

We would like to inform you that on July 21st, 2026 (Tuesday), between 01:00 AM and 02:00 AM (Brasília Time), we will perform emergency maintenance on our database infrastructure. This maintenance is crucial for the compliance of Unico's infrastructure.

Although the total maintenance window is 1 hour, the expected downtime (unavailability) will be short, estimated to last between 30 seconds and a maximum of 2 minutes. During this brief period, requests may return an HTTP 500 error.

We would like to reinforce that our engineering team will be on standby throughout the entire window. If any severe unexpected behavior is identified, we have an immediate rollback plan to restore service stability within seconds.

Best regards,

Unico Team
Jul 20, 14:11 GMT-03:00
← Incident History Powered by Atlassian Statuspage