Is Batch down?

Last checked 6m ago
Current status
Batch is up

No incidents right now.

Official status page: https://status.batch.com · Polled every 5 minutes · 46 components tracked

Batch is operational right now. Last checked 6m ago; the most recent incident resolved 26d ago.

Real-time Batch status, recent outages, and incident history — pulled directly from Batch's official status page at https://status.batch.com every 5 minutes. Pingoru tracks 46 Batch services and has captured 10 incidents in the last 90 days (99.75% uptime). Get email, Slack, Discord, or webhook alerts the moment Batch reports a new incident — free for 5 monitors, no credit card.

Users who monitor Batch also follow these Marketing services: Mailgun Klaviyo Iterable Braze Brevo Customer.io ZoomInfo Optimizely SurveyMonkey Yotpo View all 6,000+ providers
Batch uptime 99.75% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started May 19, 2026, 07:47 AM UTC · Resolved May 18, 2026, 11:00 PM UTC
    Timeline · 1 update
    • resolved · May 19, 2026, 07:47 AM UTC

      Between May 8 at 01:00 CEST and 7:14 CEST, a subset of CEP recurring automations failed to execute as scheduled. Affected automations were not sent during this window and were not retried. The issue has been resolved. The service has been operating normally since 7:14 CEST.

    Latest: Between May 8 at 01:00 CEST and 7:14 CEST, a subset of CEP recurring automations failed to execute as scheduled. Affected automations were not sent during this window and were not …

  2. Resolved 2h 7m
    Started May 13, 2026, 04:08 PM UTC · Resolved May 13, 2026, 06:16 PM UTC
    [MEP] Transactional API
    Timeline · 4 updates
    • investigating · May 13, 2026, 04:08 PM UTC

      We are investigating an issue affecting push notification delivery via the [MEP] Transactional API. Notifications submitted since 14:20 CEST may not be delivered. Our team is working to identify the cause.

    • identified · May 13, 2026, 04:40 PM UTC

      We have identified the cause of the issue. A recent configuration change caused push notifications submitted via the Transactional API to not reach our delivery pipeline. A fix is being deployed. Once it is in place, affected notifications will be delivered and no data will be lost.

    • monitoring · May 13, 2026, 05:03 PM UTC

      A fix has been deployed and the backlog of delayed notifications has been processed. New notifications are being sent as expected. We are monitoring the results.

    • resolved · May 13, 2026, 06:16 PM UTC

      All delayed notifications have been processed, and new notifications are now being delivered as expected. The incident is resolved, and all services are operating normally.

    Latest: All delayed notifications have been processed, and new notifications are now being delivered as expected. The incident is resolved, and all services are operating normally.

  3. Resolved
    Started May 12, 2026, 03:08 PM UTC · Resolved May 08, 2026, 03:00 AM UTC
    Timeline · 1 update
    • resolved · May 12, 2026, 03:08 PM UTC

      Between May 8 at 05:00 CEST and 11:15 CEST, a subset of CEP recurring automations failed to execute as scheduled. Affected automations were not sent during this window and were not retried. The issue has been resolved. The service has been operating normally since 11:30 CEST.

    Latest: Between May 8 at 05:00 CEST and 11:15 CEST, a subset of CEP recurring automations failed to execute as scheduled. Affected automations were not sent during this window and were not…

  4. Resolved 2h 8m
    Started May 07, 2026, 10:37 AM UTC · Resolved May 07, 2026, 12:45 PM UTC
    Data ingestion
    Timeline · 2 updates
    • monitoring · May 07, 2026, 10:37 AM UTC

      Our profile data indexation pipeline experienced instability starting at May 7, 05:30 CEST, causing it to fall behind on processing. As a result, profile data used for CEP one-time and recurring campaign targeting was delayed by up to 2 hours 30 minutes for a subset of traffic. The issue has been resolved. Processing has resumed and is recovering. We are monitoring the situation closely.

    • resolved · May 07, 2026, 12:45 PM UTC

      Profile data indexation has returned to normal. One-time and recurring CEP campaigns are now using up-to-date profile data for targeting and personalization. No data has been lost during this incident.

    Latest: Profile data indexation has returned to normal. One-time and recurring CEP campaigns are now using up-to-date profile data for targeting and personalization. No data has been lost …

  5. Resolved
    Started May 04, 2026, 08:13 AM UTC · Resolved May 03, 2026, 10:30 PM UTC
    Timeline · 1 update
    • resolved · May 04, 2026, 08:13 AM UTC

      Between May 4, 2026 at 00:00 CEST and May 4, 2026 at 09:30 CEST, approximately 25% of requests serving the Web SDK were failing. This prevented the SDK from loading on some web pages, and as a result, some events may not have been tracked during this period. Push notifications were not affected and were delivered as expected throughout the incident.

    Latest: Between May 4, 2026 at 00:00 CEST and May 4, 2026 at 09:30 CEST, approximately 25% of requests serving the Web SDK were failing. This prevented the SDK from loading on some web pag…

See the full Batch outage history

5 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Batch outage history →

Or sign up free to get alerts when Batch breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 10 incidents View full outage history →