Batch incident

Delays in CEP profile data indexation

Minor Resolved View vendor source →

Batch experienced a minor incident on May 7, 2026 affecting Data ingestion, lasting 2h 8m. The incident has been resolved; the full update timeline is below.

Started
May 07, 2026, 10:37 AM UTC
Resolved
May 07, 2026, 12:45 PM UTC
Duration
2h 8m
Detected by Pingoru
May 07, 2026, 10:37 AM UTC

Affected components

Data ingestion

Update timeline

  1. monitoring May 07, 2026, 10:37 AM UTC

    Our profile data indexation pipeline experienced instability starting at May 7, 05:30 CEST, causing it to fall behind on processing. As a result, profile data used for CEP one-time and recurring campaign targeting was delayed by up to 2 hours 30 minutes for a subset of traffic. The issue has been resolved. Processing has resumed and is recovering. We are monitoring the situation closely.

  2. resolved May 07, 2026, 12:45 PM UTC

    Profile data indexation has returned to normal. One-time and recurring CEP campaigns are now using up-to-date profile data for targeting and personalization. No data has been lost during this incident.

Looking to track Batch downtime and outages?

Pingoru polls Batch's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Batch reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Batch alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Batch for free

5 free monitors · No credit card required