Live / Batch / Incident
Batch: Delayed and duplicate Android push notifications (Transactional API)
Batch · batch.comResolved2026-10-26 15:04 UTC
Public — what happened
Summary
Batch said that on October 26, some Android push notifications sent through its Transactional API were delayed by up to 15 minutes and, in some cases, delivered more than once to the same device. The company said the problem ran from 09:54 to 11:30 CET, and that iOS notifications, campaigns and automations were not affected. Batch said it traced the issue to a bug on its own side, set off by an unusual situation during scheduled maintenance by its infrastructure provider. It said deliveries have been normal since 11:30 CET, though the bug remains and could recur while it works on a fix, and the incident is now marked resolved.
Timeline
- Started — 2026-10-26 12:35 UTC
- Identified — 2026-10-26 12:35 UTC
- Resolved — 2026-10-26 15:04 UTC · 2h 29m 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 45, 2026, our weekly internet health report.