Omnisend Outage History
12 incidents recorded over the last 365 days, 12 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 Omnisend Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| May 26, 2026 | A/B Campaign Date Change IssueThis incident has been resolved. | 6h 42m | Resolved |
| Apr 30, 2026 | Login issuesWe've confirmed that the issue has been fully resolved and all services are back to normal. Logins are working as expected. Thank you for your patience. | 9 min | Resolved |
| Apr 20, 2026 | "Something went wrong. Please reload the page or contact support"This incident has been resolved. | 18 min | Resolved |
| Apr 10, 2026 | Data Update DelayA fix has been implemented, and everything is now fully restored. | 3h 42m | Resolved |
| Mar 16, 2026 | Problem with the Email BuilderThis incident has been resolved. | 1h 9m | Resolved |
| Mar 13, 2026 | Degraded Performance in Sending Email Messages and functionality of Campaing and Automations tabsWe’ve confirmed the issue has been fully resolved and services are back to normal. | 1h 41m | Resolved |
| Mar 2, 2026 | http://app.omnisend.com/ has degraded performanceThis incident has been resolved. | 14h 22m | Resolved |
| Jan 29, 2026 | Degraded Performance in Campaing TrackingThis incident has been resolved. Performance is back to normal. | 1h 10m | Resolved |
| Jan 9, 2026 | Customer Message Delivery DelaysThis incident has been resolved. | 1h 14m | Resolved |
| Jan 5, 2026 | Inbound Message Delivery DisruptionThe incident has been resolved, our support messaging app is fully function now. All other services were unaffected during this period. | 46 min | Resolved |
| Dec 5, 2025 | Cloudflare Dashboard and API service IssuesAn outage related to Cloudflare server maintenance has been identified and resolved. We will be monitoring the issue in case any other problems come up. Thank you for your patience during this time. | 0 min | Resolved |
| Nov 21, 2025 | Forms AI generation not workingThis incident has been resolved. | 22 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 Omnisend 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 Omnisend 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 Omnisend 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 Omnisend outage in this window ran 14h 22m, against a mean recovery of 2h 38m. If you depend on Omnisend 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.