Batch outage on Jul 23, 2026

What happened

Batch reported a major outage starting Jul 23, 2026, 10:11 UTC, affecting Push Delivery. It was marked resolved at Jul 23, 2026, 11:08 UTC.

• The incident lasted 57m from first report to resolution.
• Batch had reported 3 other partial or major outages in the 90 days before it.
• 11 other vendors we track reported a significant incident within 12 hours of it.

Latest update from Batch

This incident has been resolved.

Read Batch's official incident report ↗

What our independent monitoring saw

Our independent monitoring of Batch started after this incident, so this report is based on Batch's status page.

Other outages around the same time

Significant incidents other vendors reported within 12 hours of this one.

• Major outageVercelJul 23, 2026, 06:47 UTC

  Dashboard authentication errors

• Major outageEpos NowJul 23, 2026, 07:16 UTC

  Delays in transactions syncing to Back Office

• Partial outageGrafana CloudJul 23, 2026, 10:13 UTC

  Stacks using SCIM user provisioning are currently unable to log into Grafana

• Major outageOry NetworkJul 23, 2026, 11:27 UTC

  Investigating elevated issues

• Partial outageABC Fitness (Ignite / Evo)Jul 23, 2026, 15:43 UTC

  3rd Party Vendor Outage Impacting ABC Fitness Services.

• Partial outageSignWellJul 23, 2026, 16:11 UTC

  Investigating — Digital signature certification delayed

• Partial outageMongoDB AtlasJul 23, 2026, 16:21 UTC

  Cluster connectivity issues in Azure westus

• Partial outageTimelyJul 23, 2026, 16:47 UTC

  Inconsistent Application Availability

• Partial outageFieldEdgeJul 23, 2026, 16:53 UTC

  Microsoft West Outage Impacting FieldEdge Services

• Partial outageGrafana CloudJul 23, 2026, 17:14 UTC

  Metrics Write Path Errors

• Partial outageOVHcloud Public CloudJul 23, 2026, 19:14 UTC

  [EU-WEST-PAR][Storage] - Object storage S3 Standard Incident Notification

Batch's overall reliability

Full Batch reliability report and live status → · Most reliable Batch alternatives →