ZeroBounce Outage History
8 incidents recorded over the last 365 days, 6 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded ZeroBounce Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 26, 2026 | File uploads issuesThe incident has been resolved. | 18 min | Resolved |
| Oct 1, 2026 | api.zerobounce.net outtageapi.zerobounce.net experienced a brief period of reduced availability in the EU lasting approximately 3 minutes. Automated safeguards identified the issue immediately, and full normal service was restored. All endpoints… | 11h 32m | Resolved |
| Sep 9, 2026 | Service Disruption: Members PlatformMembers Platform experienced a brief service disruption lasting approximately 6 minutes. During this period, members may have encountered connection errors or been unable to log in. The root cause was identified as a… | -200 min | Resolved |
| Jul 16, 2026 | New feature release - new ai_agent_mailbox substatus (no downtime)The scheduled maintenance has been completed. | 5 min | Scheduled |
| Mar 13, 2026 | Scheduled Maintenance: Customer Support Platform UpgradeThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Dec 19, 2025 | Cloudlfare - Network Performance IssuesCloudlflare have implemented a fix and we are monitoring the results. | 1h 27m | Resolved |
| Dec 5, 2025 | Cloudflare issues - different regionsOur services are back online, the cloudflare issues have been resolved. | 27 min | Resolved |
| Nov 18, 2025 | Cloudflare issues - different regionsThis incident has been resolved. | 3h 15m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next ZeroBounce incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This ZeroBounce Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before ZeroBounce acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single ZeroBounce outage in this window ran 11h 32m, against a mean recovery of 2h 35m. If you depend on ZeroBounce in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.