Mailjet Outage History
5 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 Mailjet Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 23, 2026 | Infrastructure MaintenanceScheduled maintenance is currently in progress. We will provide updates as necessary. | 1h 0m | Scheduled |
| Sep 4, 2026 | Microsoft Incident Resulting in Delivery Issues to M365This incident has been resolved. | 31 min | Resolved |
| Jun 5, 2026 | Support Ticket Creation FailuresThis incident has been resolved. | 31 min | Resolved |
| Apr 16, 2026 | Infrastructure MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Oct 14, 2025 | Lag on Event APIThis incident has been resolved. | 14h 12m | 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 Mailjet 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 Mailjet 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 Mailjet 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 Mailjet outage in this window ran 14h 12m, against a mean recovery of 3h 27m. If you depend on Mailjet 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.