User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
Is Batch down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → batch.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 74 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 06 | 0 | 0.0 | 72 ms | 0 |
| Mon 08 | 0 | 0.0 | 227 ms | 0 |
| Mon 10 | 0 | 0.0 | 118 ms | 0 |
| Mon 12 | 0 | 0.0 | 96 ms | 0 |
| Mon 14 | 0 | 0.0 | 271 ms | 0 |
| Mon 16 | 0 | 0.0 | 106 ms | 0 |
| Mon 19 | 0 | 0.0 | 271 ms | 0 |
| Mon 21 | 0 | 0.0 | 115 ms | 0 |
| Mon 23 | 0 | 0.0 | 113 ms | 0 |
| Tue 01 | 0 | 0.0 | 290 ms | 0 |
| Tue 03 | 0 | 0.0 | 236 ms | 0 |
| Tue 05 | 0 | 0.0 | 83 ms | 0 |
| Tue 07 | 0 | 0.0 | 79 ms | 0 |
| Tue 09 | 0 | 0.0 | 163 ms | 0 |
| Tue 11 | 0 | 0.0 | 190 ms | 0 |
| Tue 14 | 0 | 0.0 | 214 ms | 0 |
| Tue 16 | 0 | 0.0 | 86 ms | 0 |
| Tue 18 | 0 | 0.0 | 123 ms | 0 |
| Tue 20 | 0 | 0.0 | 148 ms | 0 |
| Tue 22 | 0 | 0.0 | 108 ms | 0 |
| Wed 01 | 0 | 0.0 | 222 ms | 0 |
| Wed 03 | 0 | 0.0 | 147 ms | 0 |
| Wed 05 | 0 | 0.0 | 108 ms | 0 |
| Wed 07 | 0 | 0.0 | 206 ms | 0 |
| Wed 10 | 0 | 0.0 | 232 ms | 0 |
| Wed 12 | 0 | 0.0 | 171 ms | 0 |
| Wed 14 | 0 | 0.0 | 203 ms | 0 |
| Wed 16 | 0 | 0.0 | 228 ms | 0 |
| Wed 18 | 0 | 0.0 | 166 ms | 0 |
| Wed 20 | 0 | 0.0 | 65 ms | 0 |
| Wed 23 | 0 | 0.0 | 237 ms | 0 |
| Thu 01 | 0 | 0.0 | 170 ms | 0 |
| Thu 03 | 0 | 0.0 | 168 ms | 0 |
| Thu 05 | 0 | 0.0 | 217 ms | 0 |
| Thu 07 | 0 | 0.0 | 183 ms | 0 |
| Thu 09 | 0 | 0.0 | 246 ms | 0 |
| Thu 11 | 0 | 0.0 | 75 ms | 0 |
| Thu 13 | 0 | 0.0 | 155 ms | 0 |
| Thu 15 | 0 | 0.0 | 239 ms | 0 |
| Thu 17 | 0 | 0.0 | 163 ms | 0 |
| Thu 19 | 0 | 0.0 | 123 ms | 0 |
| Thu 21 | 0 | 0.0 | 195 ms | 0 |
| Thu 23 | 0 | 0.0 | 174 ms | 0 |
| Fri 01 | 0 | 0.0 | 258 ms | 0 |
| Fri 03 | 0 | 0.0 | 160 ms | 0 |
| Fri 06 | 0 | 0.0 | 200 ms | 0 |
| Fri 08 | 0 | 0.0 | 90 ms | 0 |
| Fri 10 | 0 | 0.0 | 75 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Batch badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Batch yet. Outages of 10 minutes or more get their own page here.
Having trouble with Batch?
One report per service every 10 minutes from this network. No account.
Follow Batch
Get an email when Batch goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Batch alerts to Slack, Discord or a webhook — free.
About Batch
We track Batch (batch.com) as part of the Productivity group. Batch is the only CEP with AI Decisioning. Personalize, predict and automate your Email, SMS and Push campaigns from one platform.
Batch publishes an official status page at status.batch.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 159 ms average, 74–258 ms range across 12 successful checks.
Questions
Is Batch down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Batch last down?
We have not recorded a public Batch incident since monitoring began 8 days ago.
What is Batch's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Batch respond?
159 ms on average over the last 24 hours (74–258 ms).
Does Batch have an official status page?
Yes, at https://status.batch.com.
Batch not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Batch here at once, the problem is on Batch's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Batch. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.