EasyDmarc 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 EasyDmarc Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 14, 2026 | Partial Website OutageThis incident has been resolved. | 3h 9m | Resolved |
| Jul 9, 2026 | Data Migration Related IncidentData migration impacted the main EasyDMARC application and caused an outage on all services. | 0 min | Resolved |
| Jun 30, 2026 | DMARC Reporting Issue (EU Region)This incident has been fully resolved. The rua.easydmarc.eu and ruf.easydmarc.eu reporting addresses are now fully operational. As previously communicated, the disruption stemmed from a system glitch on Namecheap's end… | 28 min | Resolved |
| Jun 8, 2026 | Oracle-related outage impacting easydmarc.comThe issue affecting easydmarc.com due to the Oracle outage has been resolved. All services are now functioning normally. We apologize for any inconvenience this may have caused and appreciate your patience while we… | 14 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 EasyDmarc 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 EasyDmarc 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 EasyDmarc 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 EasyDmarc outage in this window ran 3h 9m, against a mean recovery of 58 min. If you depend on EasyDmarc 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.