Caf Outage History

Caf is up right now

Caf had 54 outages in the last 2 years totaling 118h 50m of downtime — averaging 2.2 incidents per month.

There were 54 Caf outages since September 30, 2025 totaling 118h 50m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://caf.statuspage.io

Minor September 18, 2026

Core API Instability

Detected by Pingoru
Sep 18, 2026, 05:48 PM UTC
Resolved
Sep 17, 2026, 03:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Sep 18, 2026, 05:48 PM UTC

    Between 00:30 and 10:05 BRT on September 17, 2026, we identified intermittent instability affecting the Core API. Validation and authentication flows were temporarily impacted. The issue has been fully resolved and all services are operating normally.

Read the full incident report →

Minor September 18, 2026

Temporary Unavailability — DD SDK

Detected by Pingoru
Sep 18, 2026, 05:04 PM UTC
Resolved
Sep 17, 2026, 01:05 PM UTC
Duration
Timeline · 1 update
  1. resolved Sep 18, 2026, 05:04 PM UTC

    [Resolved] Temporary Unavailability — DD SDK We identified and resolved an instability that temporarily affected the initialization and transaction processing on the DD SDK. The root cause was an improper block at the network/firewall layer, which was promptly removed by our engineering teams.

Read the full incident report →

Major September 18, 2026

Major Outage — Lawsuits with Keywords (PF53), Lawsuits (PF52) & Enhanced Personal Data (PF1.3)

Detected by Pingoru
Sep 18, 2026, 01:23 PM UTC
Resolved
Sep 18, 2026, 01:56 PM UTC
Duration
33m
Affected: [CORE-API] Lawsuits (PF52)[CORE-API] Lawsuits with Keywords (PF53)[CORE-API] Consultation at Receita Federal with Enhanced Personal Data - (PF1.3)
Timeline · 2 updates
  1. identified Sep 18, 2026, 01:23 PM UTC

    We have identified a major outage affecting Lawsuits with Keywords (PF53), Lawsuits (PF52), and Enhanced Personal Data (PF1.3). The root cause has been identified and our engineering team is actively working on remediation. Further updates will be published as the situation progresses.

  2. resolved Sep 18, 2026, 01:56 PM UTC

    This incident has been resolved. Lawsuits (PF52), Lawsuits with Keywords (PF53), and Enhanced Personal Data (PF1.3) are fully operational. We will publish a post-incident summary once our review is complete.

Read the full incident report →

Minor September 17, 2026

Degraded Performance — [CORE-API] DENATRAN Driver Data + Traffic Violations

Detected by Pingoru
Sep 17, 2026, 09:37 AM UTC
Resolved
Sep 17, 2026, 02:58 PM UTC
Duration
5h 20m
Affected: [CORE-API] DENATRAN Driver Data + Traffic Violations
Timeline · 2 updates
  1. investigating Sep 17, 2026, 09:37 AM UTC

    We are investigating reports of degraded performance affecting [CORE-API] DENATRAN Driver Data + Traffic Violations. Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.

  2. resolved Sep 17, 2026, 02:58 PM UTC

    This incident has been resolved. [CORE-API] DENATRAN Driver Data + Traffic Violations is operating normally. We will publish a full summary once our post-incident review is complete.

Read the full incident report →

Notice September 14, 2026

Scheduled Maintenance - DNS Infrastructure

Detected by Pingoru
Sep 14, 2026, 01:44 PM UTC
Resolved
Sep 17, 2026, 06:07 AM UTC
Duration
2d 16h
Affected: TransactionsOnboardingsWeb Onboarding
Timeline · 3 updates
  1. scheduled Sep 14, 2026, 01:44 PM UTC

    Realizaremos uma manutenção de DNS, o que causará uma indisponibilidade temporária de alguns minutos em alguns hosts.

  2. scheduled Sep 17, 2026, 02:30 AM UTC

    Maintenance will begin as scheduled in 60 minutes.

  3. in progress Sep 17, 2026, 03:30 AM UTC

    Scheduled maintenance is currently in progress. We will provide updates as necessary.

Read the full incident report →

Minor September 8, 2026

Degraded Performance — [CORE-API] Associated CVM (PJ65)

Detected by Pingoru
Sep 08, 2026, 06:15 PM UTC
Resolved
Sep 08, 2026, 07:47 PM UTC
Duration
1h 32m
Affected: [CORE-API] Associated CVM (PJ65)
Timeline · 2 updates
  1. investigating Sep 08, 2026, 06:15 PM UTC

    We are investigating reports of degraded performance affecting [CORE-API] Associated CVM (PJ65). Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.

  2. resolved Sep 08, 2026, 07:47 PM UTC

    This incident has been resolved. [CORE-API] Associated CVM (PJ65) is operating normally. We will publish a full summary once our post-incident review is complete.

Read the full incident report →

Minor September 3, 2026

Degraded Performance — [CORE-API] Temporary Penalties at CVM (PJ93)

Detected by Pingoru
Sep 03, 2026, 02:59 PM UTC
Resolved
Sep 03, 2026, 04:57 PM UTC
Duration
1h 57m
Affected: [CORE-API] Temporary Penalties at CVM (PJ93)
Timeline · 2 updates
  1. investigating Sep 03, 2026, 02:59 PM UTC

    We are investigating reports of degraded performance affecting [CORE-API] Temporary Penalties at CVM (PJ93). Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.

  2. resolved Sep 03, 2026, 04:57 PM UTC

    This incident has been resolved. [CORE-API] Temporary Penalties at CVM (PJ93) is operating normally. We will publish a full summary once our post-incident review is complete.

Read the full incident report →

Minor August 24, 2026

Degraded Performance — Lawsuits & Processes Services

Detected by Pingoru
Aug 24, 2026, 04:46 AM UTC
Resolved
Aug 24, 2026, 11:53 AM UTC
Duration
7h 7m
Affected: [CORE-API] Lawsuits with keywords (PJ49)[CORE-API] Processes with keywords (PF49)[CORE-API] Lawsuits (PF48)[CORE-API] Lawsuits (PJ69)
Timeline · 2 updates
  1. investigating Aug 24, 2026, 04:46 AM UTC

    We are investigating reports of degraded performance affecting Lawsuits (PJ69), Lawsuits with keywords (PJ49), Lawsuits (PF48), and Processes with keywords (PF49). Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.

  2. resolved Aug 24, 2026, 11:53 AM UTC

    This incident has been resolved. Lawsuits (PJ69), Lawsuits with keywords (PJ49), Lawsuits (PF48), and Processes with keywords (PF49) are operating normally. We will publish a full summary once our post-incident review is complete.

Read the full incident report →

Minor August 24, 2026

Degraded Performance — Lawsuits & Processes with Keywords

Detected by Pingoru
Aug 24, 2026, 03:40 AM UTC
Resolved
Aug 24, 2026, 04:24 AM UTC
Duration
44m
Affected: [CORE-API] Lawsuits with keywords (PJ49)[CORE-API] Processes with keywords (PF49)[CORE-API] Lawsuits (PF48)[CORE-API] Lawsuits (PJ69)
Timeline · 2 updates
  1. investigating Aug 24, 2026, 03:40 AM UTC

    We are investigating reports of degraded performance affecting Lawsuits (PJ69), Lawsuits with Keywords (PJ49), Lawsuits (PF48), and Processes with Keywords (PF49). Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.

  2. resolved Aug 24, 2026, 04:24 AM UTC

    This incident has been resolved. Lawsuits (PJ69), Lawsuits with Keywords (PJ49), Lawsuits (PF48), and Processes with Keywords (PF49) are operating normally. We will publish a full summary once our post-incident review is complete.

Read the full incident report →

Minor August 17, 2026

[CORE-API] KYC & Membership Compliance — Degraded Performance

Detected by Pingoru
Aug 17, 2026, 01:06 PM UTC
Resolved
Aug 17, 2026, 08:11 PM UTC
Duration
7h 5m
Affected: [CORE-API] KYC & Membership Compliance (PJ59)
Timeline · 2 updates
  1. investigating Aug 17, 2026, 01:06 PM UTC

    We are investigating reports of degraded performance affecting [CORE-API] KYC & Membership Compliance. Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.

  2. resolved Aug 17, 2026, 08:11 PM UTC

    This incident has been resolved. [CORE-API] KYC & Membership Compliance is operating normally. We will publish a full summary once our post-incident review is complete.

Read the full incident report →

Minor August 11, 2026

Degraded Performance — DENATRAN Driver Data + Traffic Violations

Detected by Pingoru
Aug 11, 2026, 03:01 AM UTC
Resolved
Aug 11, 2026, 10:20 AM UTC
Duration
7h 18m
Affected: [CORE-API] DENATRAN Driver Data + Traffic Violations
Timeline · 2 updates
  1. investigating Aug 11, 2026, 03:01 AM UTC

    We are investigating reports of degraded performance affecting DENATRAN Driver Data + Traffic Violations. Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.

  2. resolved Aug 11, 2026, 10:20 AM UTC

    This incident has been resolved. DENATRAN Driver Data + Traffic Violations is operating normally. We will publish a full summary once our post-incident review is complete.

Read the full incident report →

Minor August 4, 2026

[CORE-API] DENATRAN Driver Data + Traffic Violations — Degraded Performance

Detected by Pingoru
Aug 04, 2026, 02:13 PM UTC
Resolved
Aug 04, 2026, 04:26 PM UTC
Duration
2h 13m
Affected: [CORE-API] DENATRAN Driver Data + Traffic Violations
Timeline · 2 updates
  1. investigating Aug 04, 2026, 02:13 PM UTC

    We are investigating reports of degraded performance affecting [CORE-API] DENATRAN Driver Data + Traffic Violations. Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.

  2. resolved Aug 04, 2026, 04:26 PM UTC

    This incident has been resolved. [CORE-API] DENATRAN Driver Data + Traffic Violations is operating normally. We will publish a full summary once our post-incident review is complete.

Read the full incident report →

Minor July 28, 2026

Degraded Performance — Manual Operation

Detected by Pingoru
Jul 28, 2026, 10:54 PM UTC
Resolved
Jul 28, 2026, 11:29 PM UTC
Duration
35m
Affected: Manual Operation
Timeline · 2 updates
  1. investigating Jul 28, 2026, 10:54 PM UTC

    We are investigating reports of degraded performance affecting Manual Operation. Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.

  2. resolved Jul 28, 2026, 11:29 PM UTC

    This incident has been resolved. Manual Operation is operating normally. We will publish a full summary once our post-incident review is complete.

Read the full incident report →

Minor July 23, 2026

[CORE-API] Criminal background - Federal Police — Degraded Performance

Detected by Pingoru
Jul 23, 2026, 02:08 AM UTC
Resolved
Jul 23, 2026, 11:55 AM UTC
Duration
9h 46m
Affected: [CORE-API] Criminal background - Federal Police
Timeline · 2 updates
  1. investigating Jul 23, 2026, 02:08 AM UTC

    We are investigating reports of degraded performance affecting [CORE-API] Criminal background - Federal Police. Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.

  2. resolved Jul 23, 2026, 11:55 AM UTC

    This incident has been resolved. [CORE-API] Criminal background - Federal Police is operating normally. We will publish a full summary once our post-incident review is complete.

Read the full incident report →

Minor July 22, 2026

Degraded Performance — Criminal Background - Federal Police

Detected by Pingoru
Jul 22, 2026, 11:03 PM UTC
Resolved
Jul 23, 2026, 12:14 AM UTC
Duration
1h 10m
Affected: [CORE-API] Criminal background - Federal Police
Timeline · 2 updates
  1. investigating Jul 22, 2026, 11:03 PM UTC

    We are investigating reports of degraded performance affecting Criminal Background - Federal Police. Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.

  2. resolved Jul 23, 2026, 12:14 AM UTC

    This incident has been resolved. Criminal Background - Federal Police is operating normally as of July 22, 2026, at 20:05 BRT. We will publish a full summary once our post-incident review is complete.

Read the full incident report →

Minor July 8, 2026

Partial Outage — Manual Operation

Detected by Pingoru
Jul 08, 2026, 09:02 PM UTC
Resolved
Jul 08, 2026, 09:04 PM UTC
Duration
2m
Affected: Manual Operation
Timeline · 2 updates
  1. investigating Jul 08, 2026, 09:02 PM UTC

    We are investigating reports of a partial outage affecting Manual Operation. Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.

  2. resolved Jul 08, 2026, 09:04 PM UTC

    This incident has been resolved. Manual Operation has been fully restored and is operating normally as of July 8, 2026 at 15:50 BRT. We will publish a full summary once our post-incident review is complete.

Read the full incident report →

Minor July 7, 2026

Degraded Performance — [CORE-API] Criminal background - Federal Police

Detected by Pingoru
Jul 07, 2026, 12:50 PM UTC
Resolved
Jul 07, 2026, 12:54 PM UTC
Duration
3m
Affected: [CORE-API] Criminal background - Federal Police
Timeline · 2 updates
  1. investigating Jul 07, 2026, 12:50 PM UTC

    We are investigating reports of degraded performance affecting [CORE-API] Criminal background - Federal Police. Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.

  2. resolved Jul 07, 2026, 12:54 PM UTC

    This incident has been resolved. [CORE-API] Criminal background - Federal Police is operating normally. We will publish a full summary once our post-incident review is complete.

Read the full incident report →

Minor July 2, 2026

Degraded Performance — Temporary Penalties at CVM (PJ93)

Detected by Pingoru
Jul 02, 2026, 06:46 PM UTC
Resolved
Jul 02, 2026, 07:56 PM UTC
Duration
1h 10m
Affected: [CORE-API] Temporary Penalties at CVM (PJ93)
Timeline · 2 updates
  1. investigating Jul 02, 2026, 06:46 PM UTC

    We are investigating reports of degraded performance affecting Temporary Penalties at CVM (PJ93). Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.

  2. resolved Jul 02, 2026, 07:56 PM UTC

    This incident has been resolved. Temporary Penalties at CVM (PJ93) is operating normally. We will publish a full summary once our post-incident review is complete.

Read the full incident report →

Minor July 1, 2026

Degraded Performance — [CORE-API] KYC & Membership Compliance (PJ59)

Detected by Pingoru
Jul 01, 2026, 12:54 PM UTC
Resolved
Jul 01, 2026, 01:27 PM UTC
Duration
33m
Affected: [CORE-API] KYC & Membership Compliance (PJ59)
Timeline · 2 updates
  1. investigating Jul 01, 2026, 12:54 PM UTC

    We are investigating reports of degraded performance affecting [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.

  2. resolved Jul 01, 2026, 01:27 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 →

Minor July 1, 2026

Degraded Performance — [CORE-API] Credit Score (PF87)

Detected by Pingoru
Jul 01, 2026, 12:49 PM UTC
Resolved
Jul 01, 2026, 01:27 PM UTC
Duration
38m
Affected: [CORE-API] Credit Score (PF87)
Timeline · 2 updates
  1. investigating Jul 01, 2026, 12:49 PM UTC

    We are investigating reports of degraded performance affecting [CORE-API] Credit Score (PF87). Engineers are actively engaged and working to identify the root cause. Updates will be published as the investigation progresses.

  2. resolved Jul 01, 2026, 01:27 PM UTC

    This incident has been resolved. [CORE-API] Credit Score (PF87) is operating normally. We will publish a full summary once our post-incident review is complete.

Read the full incident report →

Major June 29, 2026

Partial Outage — Face Liveness and Face Authenticator

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
  1. 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.

  2. 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.

  3. 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 →

Major June 24, 2026

Partial Outage — Facial Biometrics

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
  1. 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.

  2. 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.

  3. 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 →

Major June 23, 2026

Degraded Performance — Consultation at Receita Federal with Enhanced Personal Data (PF1.3)

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
  1. investigating Jun 23, 2026, 06:58 AM UTC

    We are currently investigating this issue.

  2. resolved Jun 23, 2026, 12:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 22, 2026

Degraded Performance — Transactions

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
  1. 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.

  2. 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.

  3. 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 →

Minor June 20, 2026

Partial Outage — Face Liveness & Face Authenticator

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
  1. 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 →