Caf incident

Instability noticed in general services

Major Resolved View vendor source →

Caf experienced a major incident on October 20, 2025 affecting OCR and [CORE API] Basic Data (PJ1) and 1 more component, lasting 1d 8h. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 10:32 AM UTC
Resolved
Oct 21, 2025, 07:01 PM UTC
Duration
1d 8h
Detected by Pingoru
Oct 20, 2025, 10:32 AM UTC

Affected components

OCR[CORE API] Basic Data (PJ1)[CORE-API] Consultation at Receita Federal - NEW (PF2)TransactionsFace Match[CORE-API] KYC & Compliance (PJ44)[CORE-API] Criminal background - Federal PoliceOnboardingsFacial Biometrics[CORE-API] Basic Data (PF1.1)

Update timeline

  1. investigating Oct 20, 2025, 10:31 AM UTC

    We are currently investigating this issue.

  2. investigating Oct 20, 2025, 10:31 AM UTC

    We have identified service instability due to main providers issues.

  3. identified Oct 20, 2025, 01:36 PM UTC

    We have identified the root cause of the issue, which is related to an ongoing incident within AWS infrastructure. The disruption originated from service degradation in AWS components that our systems rely on. We are continuing to monitor the recovery progress and are working closely with AWS to ensure full service restoration. You can follow updates from AWS at: https://health.aws.amazon.com/health/status

  4. monitoring Oct 20, 2025, 01:36 PM UTC

    We are seeing initial signs of recovery across the affected services. Error rates are gradually decreasing, and system stability is improving. We continue to monitor the environment closely and remain in contact with AWS to ensure full resolution.

  5. identified Oct 20, 2025, 02:21 PM UTC

    We are still observing elevated error rates across our services related to ongoing issues with AWS infrastructure. This instability continues to impact parts of our operations, and we are actively monitoring the situation. Further updates will be provided as more information becomes available. You can follow updates from AWS at: https://health.aws.amazon.com/health/status

  6. identified Oct 20, 2025, 05:28 PM UTC

    We are continuing to work on a fix for this issue.

  7. monitoring Oct 20, 2025, 06:07 PM UTC

    We are seeing early signs of recovery, and some services have already started to come back online. Our teams continue to closely monitor the situation to ensure full stability. We will share further updates as recovery continues. You can follow updates from AWS at: https://health.aws.amazon.com/health/status

  8. monitoring Oct 20, 2025, 08:37 PM UTC

    Services are beeing recovery and we continue to work on reprocessing and closely monitoring the system. Based on the current recovery trend, we expect full restoration to be completed shortly.

  9. resolved Oct 21, 2025, 07:01 PM UTC

    This incident has been resolved.