Batch logo

Is Batch Down?

MarketingLive status, outages, and incident history

No. Batch is up right now.

Every monitored Batch system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment Batch breaks

Batch is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Batch status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Batch Status Summary

As of 04:14 UTC on 9 November 2026, Batch is operational. PulsAPI checked Batch's official status page and found 46 of 46 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Batch, counting degraded performance as up. The latest incident, "Dashboard instability and message delivery disruption", was on Nov 2, 2026 and lasted 1h 48m.

Cite as: PulsAPI, “Batch status”, checked 9 November 2026, 04:14 UTC. https://www.pulsapi.com/services/batch

Batch Component Status

The main Batch systems on this page. All 46 are operational right now.

46operational
[OLD_STATUSPAGE_MODEL] 3rd party integrations » mParticle
Operational
[OLD_STATUSPAGE_MODEL] 3rd party integrations » Salesforce Marketing Cloud
Operational
[OLD_STATUSPAGE_MODEL] 3rd party integrations » Segment
Operational

43 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking [OLD_STATUSPAGE_MODEL] Delivery » Email campaigns, [OLD_STATUSPAGE_MODEL] Delivery » In-app messaging, [OLD_STATUSPAGE_MODEL] Delivery » Push automations, [OLD_STATUSPAGE_MODEL] Delivery » Push campaigns, [OLD_STATUSPAGE_MODEL] Delivery » Transactional push, [OLD_STATUSPAGE_MODEL] Webservices » Custom attributes, [OLD_STATUSPAGE_MODEL] Webservices » Web push static resources, API » [CEP] Audience API, API » [CEP] Campaign API, API » [CEP] Catalog API, API » [CEP] Export API, API » [CEP] Profile API, and 31 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Batch Outages & Incidents

Incident history from the official Batch status page, including resolution updates.

Dashboard instability and message delivery disruptionResolved Nov 2, 2026 · 1h 48mResolved

This incident has been resolved. On November 2, between 12:19 and 13:02 CET, a brief network interruption between our database servers left one of our internal services unable to reconnect, which made the dashboard and the Campaigns API very slow or unavailable and delayed message sending (push, email, SMS and transactional). Service was fully restored at 13:02 CET, and all delayed messages were processed by 13:10 CET. We are adding safeguards so that database connections recover automatically from this kind of interruption. --- [2026-11-02T12:30:05.972Z] (monitoring) On November 2, between 12:19 and 12:58 CET, an internal database connectivity issue caused the dashboard to be very slow and delayed message sending (push, email and transactional API). The issue was mitigated at 12:58 CET: the dashboard is back to normal and the sending backlog has been processed. Campaigns and automations scheduled during this window were delayed and have since been sent. We are continuing to monitor the situation. --- [2026-11-02T12:34:02.923Z] (investigating) We restored the affected internal service at 12:58 CET, and the dashboard is back to normal. Message delivery has resumed: push notifications and emails delayed since 12:20 CET are currently being sent, so some messages may still arrive late. We're still searching for the root issue. We are monitoring until delivery is fully back to real time. --- [2026-11-02T12:33:50.903Z] (investigating) We are investigating an issue affecting the Batch dashboard and message delivery. Since around 12:20 CET, the dashboard may be slow, fail to load campaign data or log users out, and most push notifications and emails (campaigns, automations and transactional) are not being sent. Transactional API calls are still accepted, but the related messages are currently not delivered. Our team is actively working on a resolution.

Delayed and duplicate Android push notifications (Transactional API)Resolved Oct 26, 2026 · 2h 29mResolved

This incident has been resolved. --- [2026-10-26T12:35:00.238Z] (identified) On October 26, between 09:54 and 11:30 CET, a subset of Android push notifications sent via the Transactional API experienced intermittent delays of up to 15 minutes, and some were delivered multiple times to the same device. iOS push notifications, campaigns and automations were not affected. This was caused by a bug on our side, triggered by an edge case during scheduled maintenance performed by our infrastructure provider. Deliveries have been back to normal since 11:30 CET. The bug is still present and the issue could happen again: we are monitoring closely and working on a fix.

Precautionary temporary restriction of file uploads in the dashboardResolved Oct 21, 2026 · 6h 54mResolved

Affected Batch systems have been fully upgraded to patched versions. --- [2026-10-21T11:58:52.057Z] (monitoring) A security vulnerability affecting widely used open-source web software (PHP) was publicly disclosed today. This is not an incident on Batch's side: we have no indication that our platform or our customers' data have been affected. We advise that you check your own systems to see if they are affected by this issue. As a precaution, we are temporarily disabling file uploads in the Batch dashboard while we wait for the necessary updates to be released and apply them. During this time, at least the following actions are unavailable: - Creating audiences from a file - Uploading or updating iOS and Safari push certificates and keys - Updating a landing page favicon Everything else keeps working normally: SDKs, push sending, campaigns, automations, and APIs are not affected. We expect to restore these features within a few hours and will post an update here as soon as they are back.

Batch Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Batch incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history1 day observed
Nov 9100.00% averageNov 9

Live Batch Outage Reports

Problems reported by engineers using Batch. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Batch problems reported yet.

Something wrong with Batch on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Batch

Is Batch down? Its official status page at status.batch.com reports on 53 components, including Segment, Dashboard and Editorial dashboard. PulsAPI checks it every few minutes and can alert you when Batch reports an incident.

Over the past 30 days, PulsAPI has measured Batch uptime at 100.00%. Response times, incident history, and SLA tracking for Batch are available on the PulsAPI dashboard.

Batch Status FAQ

Is Batch down right now?

The verdict at the top of this page comes from the latest poll of the official Batch status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Batch is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Batch recovers.

How do I check Batch uptime history?

PulsAPI tracks Batch uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Batch changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Batch outages?

PulsAPI reads the official Batch status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Batch components?

Yes. PulsAPI monitors 46 individual Batch components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Batch goes down?

Yes. Create a free account and subscribe to Batch: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Batch to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Batch problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Batch?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Batch plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Batch with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services