Live  /  Batch  /  Incident

Batch: Delays in file-based audience imports

Batch · batch.comMajor incidentResolved2026-10-14 14:05 UTC
Public — what happened

Summary

Batch said that audience lists uploaded as files over FTP or SFTP had not been processed since October 12, which meant those audiences were not being refreshed. The company reported the problem as identified at 13:11 UTC on October 14, 2026, and said a fix was being rolled out at that time. By 13:37 UTC, Batch said imports were working again and the files that had piled up since October 12 were being worked through automatically. The incident was marked resolved at 14:05 the same day; Batch did not give a cause.

Affected

Custom Audiences, Audiences

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 43, 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.