Confiant Outage History

Confiant is up right now

Confiant had 4 outages in the last 2 years totaling 765h 43m of downtime — averaging 0.2 incidents per month.

There were 4 Confiant outages since January 12, 2026 totaling 765h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.confiant.com

Minor August 1, 2026

Blocking Webhook Service Degraded

Detected by Pingoru
Aug 01, 2026, 03:57 PM UTC
Resolved
Aug 01, 2026, 05:05 PM UTC
Duration
1h 8m
Affected: Confiant API
Timeline · 2 updates
  1. investigating Aug 01, 2026, 03:57 PM UTC

    Service with the blocking webhook is currently degraded. We are actively investigating.

  2. resolved Aug 01, 2026, 05:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 10, 2026

Ad Scanning System Degradation

Detected by Pingoru
Jul 10, 2026, 02:57 PM UTC
Resolved
Jul 10, 2026, 02:57 PM UTC
Duration
Affected: Confiant API
Timeline · 1 update
  1. resolved Jul 10, 2026, 02:57 PM UTC

    We experienced system degradation with scanning today from 6:44am - 7:11am PST. This was caused by a deployment that produced service unavailable errors with our scanning APIs. These APIs are backup as of 7:11am PST and we will continue to monitor them as the backed up queues process. Scanning results are delayed as a result of this incident. We will monitor the system to ensure the queues are processed and the system returns to full health.

Read the full incident report →

Major January 12, 2026

We are currently experiencing degraded service on our Platform UI

Detected by Pingoru
Jan 12, 2026, 08:19 PM UTC
Resolved
Feb 13, 2026, 04:48 PM UTC
Duration
31d 20h
Affected: Confiant Reporting UI
Timeline · 7 updates
  1. investigating Jan 12, 2026, 08:19 PM UTC

    We are currently experiencing a partial outage on our Platform UI: Scan Log: not available Creative search: not available Publisher blocks: available

  2. investigating Jan 13, 2026, 12:51 AM UTC

    We are continuing to investigate this issue.

  3. investigating Jan 13, 2026, 02:25 PM UTC

    We are continuing to investigate this issue.

  4. identified Jan 13, 2026, 05:30 PM UTC

    The issue has been identified, and we are working on a remediation plan.

  5. identified Jan 13, 2026, 11:00 PM UTC

    We are continuing to work through the remediation plan for this issue.

  6. identified Jan 14, 2026, 06:05 PM UTC

    Partial service has been restored. Creative search and scan log are now available with a partial data set. Remediation to restore additional data is in progress.

  7. resolved Feb 13, 2026, 04:48 PM UTC

    This incident has been fully resolved, and normal service has been fully resolved.

Read the full incident report →