Skip to main content
Mailjet logo

Is Mailjet Down?

No — Mailjet is up

Reachable from all 8 checked regions

Average response time: 1355ms

Last checked · checks run every 6 hours

Official status page: https://status.mailjet.com

Mailjet uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
1083ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 24 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

24-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: 100.00% uptime, 16 checks
Aug 29: 100.00% uptime, 32 checks
Aug 30: 100.00% uptime, 32 checks
Aug 31: 100.00% uptime, 32 checks
Sep 1: 100.00% uptime, 32 checks
Sep 2: 100.00% uptime, 32 checks
Sep 3: 100.00% uptime, 32 checks
Sep 4: 100.00% uptime, 32 checks
Sep 5: 100.00% uptime, 28 checks
Sep 6: 100.00% uptime, 21 checks
Sep 7: 100.00% uptime, 24 checks
Sep 8: 100.00% uptime, 38 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: 100.00% uptime, 31 checks
Sep 11: 100.00% uptime, 35 checks
Sep 12: 100.00% uptime, 31 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 31 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 31 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 16 checks
Aug 22 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
394ms
DNS 137ms TCP 9ms TLS 15ms TTFB 358ms
arn
898ms
DNS 248ms TCP 24ms TLS 30ms TTFB 802ms
bom
1669ms
DNS 216ms TCP 60ms TLS 67ms TTFB 1427ms
cdg
400ms
DNS 138ms TCP 10ms TLS 16ms TTFB 356ms
sin
1923ms
DNS 858ms TCP 1ms TLS 11ms TTFB 1909ms
sjc
1953ms
DNS 625ms TCP 67ms TLS 76ms TTFB 1683ms
syd
2569ms
DNS 782ms TCP 2ms TLS 12ms TTFB 2556ms
yyz
1036ms
DNS 342ms TCP 19ms TLS 29ms TTFB 961ms

What Mailjet does

Mailjet sends both transactional and marketing email, offering an HTTPS API, an SMTP relay and a drag-and-drop campaign editor. Businesses use it for order confirmations and password resets alongside newsletters, which means one incident can touch automated application mail and a scheduled campaign at the same time. It is part of the Sinch group.

What an outage looks like

Send calls fail or time out, and SMTP connections are refused or hang after the handshake. Mailjet separates SEND API, REST API, Event API, Incoming SMTP and Outgoing SMTP, so the path your code uses decides what you see. A distinct and confusing case is Statistics Display failing while mail flows normally, which makes a healthy send look like a dead one.

What to do about it

Check status.mailjet.com and match the component to the integration you actually use. Open rates and delivery counts come from Statistics Display and the Event API, both listed apart from the sending components, so treat missing numbers as a reporting problem until sending itself is reported down. Pause scheduled campaigns rather than resending them, and avoid retrying transactional mail that may already have been accepted.

Is it down for everyone, or just you?

If this page says Mailjet is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Brevo
Brevo
SendGrid (Twilio)
SendGrid (Twilio)
Mailgun
Mailgun
Postmark
Postmark

Mailjet outage FAQ

My Mailjet statistics are empty. Did my campaign fail?
Probably not. Statistics Display is its own component on Mailjet's status page, separate from SEND API, REST API and the SMTP components that actually move mail. During an incident scoped to reporting, messages continue to be sent and delivered while the dashboard shows nothing. Confirm with a test address before resending a campaign to a full list.
Is the Mailjet API down or just the website?
They are tracked separately. Mailjet lists Website (Mailjet.com) and Mailjet App apart from SEND API, REST API and Event API. The marketing site or the app interface can be unavailable while the sending APIs are healthy, which is why an application can keep delivering transactional mail during an incident that stops you logging in to check on it.
Should I switch to SMTP if the API is failing?
It can help, because Mailjet reports Outgoing SMTP and Incoming SMTP as components distinct from the SEND API. If the status page shows the API degraded and SMTP operational, an application that supports both can be repointed. Check the page first rather than switching blindly, since an incident affecting shared infrastructure will show both paths degraded together.
Will queued campaign emails send after the outage?
Mailjet does not publish queue-drain behaviour on its status page, so do not assume either outcome for a campaign scheduled during an incident. Check the campaign's own state in the app once the relevant components are reported operational, and send to a small test segment before re-running anything, since a duplicate send to a full list cannot be recalled.
Does a Mailjet outage affect transactional and marketing mail equally?
Not necessarily, because it depends which component is affected. Transactional mail typically goes through SEND API or Outgoing SMTP, while campaigns also involve the Email Editor, Email Content and Form Builder components. An incident scoped to the editor stops you building a newsletter without touching the automated mail your application sends.

How we measure this

  • We request Mailjet's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Mailjet publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Mailjet goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required