Live  /  Batch  /  Incident

Batch: Processing delays for profile updates

Batch · batch.comMinor incidentResolved2026-10-20 14:36 UTC
Public — what happened

Summary

Batch said its profile processing pipeline was running behind, delaying updates such as attributes, events and delivery statuses by roughly 15 minutes, with the lag growing, and that automations triggered by those updates could also be late. The company reported identifying the problem and a fix being deployed at the 14:04 UTC start, and said no data had been lost. By 14:15 UTC Batch said processing had resumed and updates sent through its Profile API were again handled in real time, while updates from its mobile SDKs were still delayed as a backlog cleared. The incident was marked resolved at 14:36 UTC on 2026-10-20.

Affected

[CEP] Profile API, Data ingestion, Event Targeting & Retargeting

As listed on Batch’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Batch against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Batch: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Batch report →

More from Batch

Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.

The full archive is on the Batch status & history page.

Related: Batch status & history. SquidGrid is not affiliated with Batch.