- Detected by Pingoru
- Jun 29, 2026, 07:20 PM UTC
- Resolved
- Jun 29, 2026, 07:47 PM UTC
- Duration
- 26m
Affected: Face LivenessFace Authenticator
Timeline · 3 updates
-
investigating Jun 29, 2026, 07:20 PM UTC
We are investigating reports of a partial outage affecting Face Liveness and Face Authenticator. Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.
-
monitoring Jun 29, 2026, 07:28 PM UTC
A fix has been implemented and we are actively monitoring Face Liveness and Face Authenticator to confirm full recovery. Further updates will be provided if any degradation is observed.
-
resolved Jun 29, 2026, 07:47 PM UTC
This incident has been resolved. Face Liveness and Face Authenticator are operating normally. We will publish a full summary once our post-incident review is complete.
Read the full incident report →
- Detected by Pingoru
- Jun 24, 2026, 12:52 PM UTC
- Resolved
- Jun 24, 2026, 01:12 PM UTC
- Duration
- 20m
Affected: Facial Biometrics
Timeline · 3 updates
-
investigating Jun 24, 2026, 12:52 PM UTC
We are investigating reports of a partial outage affecting Facial Biometrics. Some requests may be failing or experiencing degraded availability. Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.
-
monitoring Jun 24, 2026, 12:58 PM UTC
A fix has been identified and applied. We are actively monitoring Facial Biometrics to confirm full recovery. Further updates will be provided if conditions change.
-
resolved Jun 24, 2026, 01:12 PM UTC
This incident has been resolved. Facial Biometrics is operating normally. We will publish a full summary once our post-incident review is complete.
Read the full incident report →
- Detected by Pingoru
- Jun 23, 2026, 06:58 AM UTC
- Resolved
- Jun 23, 2026, 12:04 PM UTC
- Duration
- 5h 6m
Affected: [CORE-API] Consultation at Receita Federal with Enhanced Personal Data - (PF1.3)
Timeline · 2 updates
-
investigating Jun 23, 2026, 06:58 AM UTC
We are currently investigating this issue.
-
resolved Jun 23, 2026, 12:04 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 22, 2026, 02:26 PM UTC
- Resolved
- Jun 22, 2026, 03:07 PM UTC
- Duration
- 40m
Affected: Transactions
Timeline · 3 updates
-
investigating Jun 22, 2026, 02:26 PM UTC
We are investigating reports of degraded performance affecting Transactions. Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.
-
monitoring Jun 22, 2026, 02:41 PM UTC
A fix has been identified and applied. We are actively monitoring Transactions to confirm that performance has fully recovered. Further updates will be provided if conditions change.
-
resolved Jun 22, 2026, 03:07 PM UTC
The incident impacted a portion of transactions processed during the affected period. Our technical team is actively working to identify and automatically reprocess all recoverable cases. For cases where reprocessing is not feasible, our Customer Success team will reach out individually to each affected customer to present the available resolution options.
Read the full incident report →
- Detected by Pingoru
- Jun 20, 2026, 03:00 AM UTC
- Resolved
- Jun 20, 2026, 03:00 AM UTC
- Duration
- —
Affected: Face LivenessFace Authenticator
Timeline · 1 update
-
resolved Jun 23, 2026, 07:12 PM UTC
A partial outage affecting Face Liveness and Face Authenticator was identified and resolved. Services returned to normal operation at 00:07 (UTC-3).
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 02:08 PM UTC
- Resolved
- Jun 18, 2026, 03:31 PM UTC
- Duration
- 1h 22m
Affected: [CORE-API] KYC & Membership Compliance (PJ59)
Timeline · 2 updates
-
investigating Jun 18, 2026, 02:08 PM UTC
We are investigating reports of degraded performance on [CORE-API] KYC & Membership Compliance (PJ59). Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.
-
resolved Jun 18, 2026, 03:31 PM UTC
This incident has been resolved. [CORE-API] KYC & Membership Compliance (PJ59) is operating normally. We will publish a full summary once our post-incident review is complete.
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 04:05 AM UTC
- Resolved
- Jun 17, 2026, 05:48 PM UTC
- Duration
- 13h 42m
Affected: Face Liveness
Timeline · 2 updates
-
monitoring Jun 17, 2026, 04:05 AM UTC
A fix was implemented and we are monitoring the results. Since 00:12 BRT (3:12 UTC), the liveness service has been operating normally.
-
resolved Jun 17, 2026, 05:48 PM UTC
This incident has been resolved. Face Liveness is operating normally. We will publish a full summary once our post-incident review is complete.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 07:39 PM UTC
- Resolved
- Jun 10, 2026, 08:57 PM UTC
- Duration
- 1h 18m
Affected: Trust Platform
Timeline · 3 updates
-
investigating Jun 10, 2026, 07:39 PM UTC
We are investigating reports of degraded performance affecting Trust Platform. Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.
-
monitoring Jun 10, 2026, 07:45 PM UTC
A fix has been implemented and we are actively monitoring Trust Platform to confirm full recovery. Further updates will be provided if any degradation is observed.
-
resolved Jun 10, 2026, 08:57 PM UTC
This incident has been resolved. Trust Platform is operating normally. We will publish a full summary once our post-incident review is complete.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 12:53 PM UTC
- Resolved
- Jun 10, 2026, 01:39 PM UTC
- Duration
- 46m
Affected: Facial Biometrics
Timeline · 4 updates
-
investigating Jun 10, 2026, 12:53 PM UTC
We are currently investigating this issue
-
identified Jun 10, 2026, 01:15 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 10, 2026, 01:15 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 10, 2026, 01:39 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 02:16 PM UTC
- Resolved
- Jun 08, 2026, 01:16 PM UTC
- Duration
- —
Affected: [CORE-API] Associated CVM (PJ65)[CORE-API] CVM Associate (PF47)
Timeline · 3 updates
-
investigating Jun 05, 2026, 01:39 PM UTC
We are investigating reports of a major outage affecting [CORE-API] Associated CVM (PJ65) and CVM Associate (PF47). Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.
-
monitoring Jun 05, 2026, 07:11 PM UTC
A fix has been implemented and we are monitoring the recovery of [CORE-API] Associated CVM (PJ65) and CVM Associate (PF47). Further updates will be provided if the situation changes.
-
resolved Jun 08, 2026, 05:14 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 07:15 PM UTC
- Resolved
- Jun 01, 2026, 07:16 PM UTC
- Duration
- 1m
Affected: [CORE-API] Lawsuits with keywords (PJ49)[CORE-API] Processes with keywords (PF49)[CORE-API] Lawsuits (PF48)[CORE-API] Lawsuits (PJ69)
Timeline · 2 updates
-
investigating Jun 01, 2026, 07:15 PM UTC
We are investigating reports of degraded performance affecting [CORE-API] Lawsuits (PJ69), [CORE-API] Lawsuits with keywords (PJ49), [CORE-API] Lawsuits (PF48), and [CORE-API] Processes with keywords (PF49). Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.
-
resolved Jun 01, 2026, 07:16 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 08:09 PM UTC
- Resolved
- May 22, 2026, 09:51 PM UTC
- Duration
- 1h 41m
Affected: Trust Platform
Timeline · 2 updates
-
investigating May 22, 2026, 08:09 PM UTC
We are investigating reports of a major outage affecting Trust Platform. Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.
-
resolved May 22, 2026, 09:51 PM UTC
A fix has been applied and this incident is now resolved. Trust Platform is operating normally. We will publish a full summary once our post-incident review is complete.
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 06:18 PM UTC
- Resolved
- May 19, 2026, 09:16 PM UTC
- Duration
- 1d 2h
Affected: Onboardings
Timeline · 2 updates
-
monitoring May 18, 2026, 06:18 PM UTC
We are monitoring an issue affecting SMS delivery for a subset of numbers within the Onboardings flow. The responsible engineering team has identified the scope of impact and is actively tracking the situation. Further updates will be published as the investigation progresses.
-
resolved May 19, 2026, 09:16 PM UTC
This incident has been resolved. SMS delivery within the Onboardings flow is operating normally. We will publish a full post-incident summary once our review is complete.
Read the full incident report →
- Detected by Pingoru
- May 12, 2026, 04:13 PM UTC
- Resolved
- May 12, 2026, 09:01 PM UTC
- Duration
- 4h 47m
Affected: Facial Biometrics
Timeline · 2 updates
-
monitoring May 12, 2026, 04:13 PM UTC
We have identified an issue affecting Facial Biometrics. The root cause has been identified and a fix has been applied. We are actively monitoring the service to confirm full recovery.
-
resolved May 12, 2026, 09:01 PM UTC
This incident has been resolved. Facial Biometrics is operating normally. We will publish a full summary once our post-incident review is complete.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 01:14 PM UTC
- Resolved
- May 11, 2026, 01:24 PM UTC
- Duration
- 3d
Affected: Transactions
Timeline · 2 updates
-
investigating May 08, 2026, 01:14 PM UTC
Estamos investigando relatos de degradação de performance no componente Transactions. Nossa equipe já está atuando para identificar e resolver o problema. Atualizações serão publicadas conforme houver progresso.
-
resolved May 11, 2026, 01:24 PM UTC
O incidente foi resolvido e o serviço Transactions está operando normalmente. Agradecemos a compreensão de todos durante este período.
Read the full incident report →
- Detected by Pingoru
- May 05, 2026, 02:30 PM UTC
- Resolved
- May 05, 2026, 08:34 PM UTC
- Duration
- 6h 4m
Affected: [CORE-API] Lawsuits (PJ69)[CORE-API] Lawsuits with Keywords (PJ70)[CORE-API] Lawsuits (PF52)[CORE-API] Lawsuits with Keywords (PF53)
Timeline · 3 updates
-
investigating May 05, 2026, 02:30 PM UTC
We are currently experiencing some technical difficulties with our datasource, which has led to a partial disruption to the the pfLegalRecordsExtended, pfLegalRecordsExtendedKeywords, pjLegalRecordsExtended and pjLegalRecordsExtendedKeywords services. Our team is actively working to resolve these issues and restore full service functionality as soon as possible. We apologize for any inconvenience this may have caused and appreciate your patience and understanding during this time.
-
investigating May 05, 2026, 06:46 PM UTC
We are continuing to investigate this issue.
-
resolved May 05, 2026, 08:34 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 05, 2026, 12:49 PM UTC
- Resolved
- May 05, 2026, 02:32 PM UTC
- Duration
- 1h 42m
Affected: Trust Platform
Timeline · 5 updates
-
investigating May 05, 2026, 12:49 PM UTC
We are currently investigating this issue.
-
identified May 05, 2026, 01:15 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring May 05, 2026, 01:52 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring May 05, 2026, 01:52 PM UTC
We are continuing to monitor for any further issues.
-
resolved May 05, 2026, 02:32 PM UTC
O incidente foi resolvido. O componente Trust Platform está operando normalmente. Agradecemos a compreensão de todos durante este período.
Read the full incident report →
- Detected by Pingoru
- Apr 27, 2026, 01:30 AM UTC
- Resolved
- Apr 27, 2026, 01:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 06, 2026, 03:22 PM UTC
Between 22:32 and 22:44 BRT, our facial validation service experienced a period of instability, affecting the experience of some users. During this approximately 12-minute interval, the service's success rate was impacted, resulting in failures for a portion of users.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 12:08 AM UTC
- Resolved
- Apr 24, 2026, 12:40 AM UTC
- Duration
- 32m
Affected: Smart Auth
Timeline · 3 updates
-
identified Apr 24, 2026, 12:08 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Apr 24, 2026, 12:36 AM UTC
A fix has been implemented and we are monitoring the results. Some users may need to retry to complete the Smart Auth validation.
-
resolved Apr 24, 2026, 12:40 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 12:41 AM UTC
- Resolved
- Mar 31, 2026, 12:57 AM UTC
- Duration
- 16m
Affected: Face LivenessFace Authenticator
Timeline · 4 updates
-
investigating Mar 31, 2026, 12:41 AM UTC
We are noticing an increase in the service’s error rate.
-
identified Mar 31, 2026, 12:43 AM UTC
The team is working to activate redundancy mechanisms and reduce the impact of the errors.
-
monitoring Mar 31, 2026, 12:55 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 31, 2026, 02:05 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 25, 2026, 03:00 PM UTC
- Resolved
- Mar 27, 2026, 03:04 PM UTC
- Duration
- 2d
Affected: [CORE-API] Processes with keywords (PF49)
Timeline · 4 updates
-
identified Mar 25, 2026, 03:22 PM UTC
The issue has been identified and a fix is being implemented.
-
identified Mar 25, 2026, 03:23 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Mar 25, 2026, 03:34 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 27, 2026, 03:04 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 13, 2026, 09:53 PM UTC
- Resolved
- Mar 14, 2026, 12:58 AM UTC
- Duration
- 3h 5m
Affected: OnboardingsWeb Onboarding
Timeline · 2 updates
-
monitoring Mar 13, 2026, 09:53 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 14, 2026, 12:58 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 13, 2026, 08:49 PM UTC
- Resolved
- Mar 13, 2026, 09:52 PM UTC
- Duration
- 1h 2m
Affected: OnboardingsWeb Onboarding
Timeline · 3 updates
-
investigating Mar 13, 2026, 09:03 PM UTC
We are currently investigating this issue.
-
monitoring Mar 13, 2026, 09:05 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 13, 2026, 09:52 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 02:40 PM UTC
- Resolved
- Mar 12, 2026, 05:43 PM UTC
- Duration
- 3h 2m
Affected: Global Document DetectorGlobal Doc Reader
Timeline · 2 updates
-
investigating Mar 12, 2026, 02:40 PM UTC
We are experiencing a high error rate in services related to global document verification.
-
resolved Mar 12, 2026, 05:43 PM UTC
This incident has been resolved and services are operational again.
Read the full incident report →
- Detected by Pingoru
- Jan 12, 2026, 06:37 PM UTC
- Resolved
- Jan 12, 2026, 08:48 PM UTC
- Duration
- 2h 11m
Affected: [CORE-API] CVM Associate (PF47)
Timeline · 2 updates
-
investigating Jan 12, 2026, 06:37 PM UTC
We are currently investigating this issue.
-
resolved Jan 12, 2026, 08:48 PM UTC
This incident has been resolved.
Read the full incident report →