Mailjet outage history

Starting around 08:00 UTC, Microsoft began experiencing an incident causing an increased volume of deferred emails across all M365 regions. The affected responses are returning "451 4.7.500 Server busy". Our teams are actively monitoring the situation. Sending to other email providers is not affected.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Lag are identified we are investigating the issue

The issue has been identified and our team is working on a fix.

The fix is under review.

The fix is now under testing.

A fix has been implemented and we are monitoring the results.

We'll be monitoring the situation throughout the night until 9am CET to ensure stable service delivery.

We are continuing to monitor for any further issues.

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

A fix has been implemented and we are monitoring the results.

We are continuing to monitor for any further issues. Events are being processed and the service is catching up on missing events.

We are continuing to monitor for any further issues.

We are continuing to actively monitor the system.

This incident has been resolved.

We are currently investigating an issue impacting email processing along with app.mailjet.com login issues, reflecting into "wrong password" errors.

We are continuing to investigate this issue.

We have identified the root cause of the issue. While we are working on getting this resolved, clients will experience inability to log into app.mailjet.com as well as experience email processing delays.

We are continuing to work on a fix for this issue.

A fix has been implemented and we are monitoring the results.

The incident has been resolved. Any missing statistics during the incident haven't been lost and will show up in the statistics page later today.

We are currently investigating this issue.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

We are continuing to work on a fix for this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Our team is currently investigating a potential issue impacting some customers on webhook connection.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating issues with our Event API partially sending events.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating login issues on app

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

The issue has been identified and we are currently working through the fix

The mitigation of the DDoS attack to our application is still in progress.

A fix has been implemented and we are monitoring the results.

We have implemented measures to mitigate the DDoS attack on our application and are continuously making adjustments to better withstand the attack. Some customers may report intermittent periods where the application experiences slowness or becomes unresponsive.

We are continuing to monitor for any further issues.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

We are continuing to work through the fix for this issue

The mitigation of the DDoS attack to our application is still in progress.

The service is back but we're continuing to monitor its state to ensure there's no further issues.

The service is back to normal.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

Different fixes are being implemented and we are monitoring the results.

Remediation is still in progress and outbound mail continues to be delayed.

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Mailjet Engineering is investigating an email sending delay.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Some customers may report that scheduled campaigns are not being sent. Our teams are currently investigating this issue.

The issue has been identified and a fix is being implemented.

Some customers may report degraded performance on sending campaigns or campaigns scheduled not being sent. Our teams are currently investigating this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.