Email on Acid Outage History
5 incidents recorded over the last 365 days, 2 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 Email on Acid Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 18, 2026 | Email Previews MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jun 25, 2026 | Issue with email previewsThis incident has been resolved. | 1h 9m | Resolved |
| Apr 27, 2026 | Apple DevicesThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Mar 25, 2026 | Apple DevicesThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Nov 5, 2025 | Apple/iOS Device OutageThis incident has been resolved. | 2h 7m | 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 Email on Acid 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 Email on Acid 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 Email on Acid 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 Email on Acid outage in this window ran 3h, against a mean recovery of 2h 3m. If you depend on Email on Acid 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.