Live / Batch / Incident
Batch: Dashboard instability and message delivery disruption
Batch · batch.comMajor incidentResolved2026-11-02 13:07 UTC
Public — what happened
Summary
Batch said it was investigating a problem that made its dashboard slow, unable to load campaign data, or prone to logging users out, while most push notifications and emails were not being sent. It said transactional API calls were still accepted but the resulting messages were not delivered. Batch reported that it restored an affected internal service, the dashboard returned to normal, and delayed messages began going out, though some might still arrive late and it was still looking for the root issue. The incident, which started at 11:57 UTC on 2026-11-02, was marked resolved at 13:07.
Affected
Dashboard, Email delivery, [CEP] Campaign API, Push Delivery, SMS Delivery
Timeline
- Started — 2026-11-02 11:57 UTC
- Investigating — 2026-11-02 11:57 UTC (2 updates)
- Resolved — 2026-11-02 13:07 UTC · 1h 11m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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 46, 2026, our weekly internet health report.