Valimail Outage History
9 incidents recorded over the last 365 days, 3 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 Valimail Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 16, 2026 | Infrastructure MaintenanceThe scheduled maintenance has been completed. | 2h 59m | Scheduled |
| Sep 10, 2026 | Database MaintenanceThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Sep 9, 2026 | Database MaintenanceScheduled maintenance is currently in progress. We will provide updates as necessary. | 2h 59m | Scheduled |
| Jun 10, 2026 | Database MaintenanceThe scheduled maintenance has been completed. | 2h 59m | Scheduled |
| Apr 7, 2026 | Email alerts being sent for SPF record changesThe issue related to the alert notifications has been addressed. | 146h 21m | Resolved |
| Mar 12, 2026 | Infrastructure MaintenanceThe scheduled maintenance has been completed. | 2h 59m | Scheduled |
| Mar 6, 2026 | BIMI Logo Not Displayed in the RecordThis incident has been resolved. The BIMI logo is now fully available in the BIMI record, and systems are operating normally. Thank you for your patience while we worked to address this issue. | 1h 43m | Resolved |
| Jan 9, 2026 | Support outageThis incident has been resolved. We appreciate your patience! | 1h 37m | Resolved |
| Dec 11, 2025 | Infrastructure MaintenanceThe scheduled maintenance has been completed. | 2h 59m | Scheduled |
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 Valimail 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 Valimail 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 Valimail 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 Valimail outage in this window ran 6d 2h, against a mean recovery of 18h 37m. If you depend on Valimail 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.