EmailOctopus Outage History
4 incidents recorded over the last 365 days, 4 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 EmailOctopus Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | Service is restoredThe campaign backlog is now cleared, and with that we're closing this incident. Thank you again for your patience and understanding while we worked to deploy this important update. | 1h 18m | Resolved |
| Oct 21, 2026 | EmailOctopus is offline while we apply an important updateAll services are now back online and our campaign backlog is now cleared. With that we're closing this incident. Thank you again for your patience and understanding while we worked to deploy this important security… | 4h 39m | Resolved |
| Oct 21, 2026 | Short maintenance to install a security updateAll services are now back online and our campaign backlog is now cleared. With that we're closing this incident. Thank you again for your patience and understanding while we worked to deploy this important security… | 6h 19m | Resolved |
| Dec 5, 2025 | 500 errors via CloudflareFollowing Cloudflare’s fix, the EmailOctopus website and Dashboard have now been loading reliably for an extended period of time. We’ve seen no further errors and all systems are operating normally. | 21 min | 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 EmailOctopus 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 EmailOctopus 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 EmailOctopus 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 EmailOctopus outage in this window ran 6h 19m, against a mean recovery of 3h 9m. If you depend on EmailOctopus 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.