Skip to main content
Mailjet logo

Is Mailjet Down?

No — Mailjet is up
Mailjet's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 891 ms

Right now

The verdict is the worse of these two. How we decide

Mailjet's status page

status.mailjet.com · read · checked every 3 minutes

Operational
Mailjet's components, as its status page reports them
ComponentStatus
Mailjet AppOperational
Website (Mailjet.com)Operational
SEND APIOperational
REST APIOperational
Event APIOperational
Incoming SMTPOperational
Outgoing SMTPOperational
Email EditorOperational
Email ContentOperational
Statistics DisplayOperational
Premium FeaturesOperational
Form BuilderOperational
2 more, all operational · show all 14
All of Mailjet's components
ComponentStatus
Mailjet AppOperational
Website (Mailjet.com)Operational
SEND APIOperational
REST APIOperational
Event APIOperational
Incoming SMTPOperational
Outgoing SMTPOperational
Email EditorOperational
Email ContentOperational
Statistics DisplayOperational
Premium FeaturesOperational
Form BuilderOperational
Mailjet EmbeddedOperational
SupportOperational

FlareWarden checks

api.mailjet.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
891 ms
Checked

By region

  • Amsterdam reachable, 439 ms
  • Dallas reachable, 1032 ms
  • Frankfurt reachable, 372 ms
  • Newark reachable, 805 ms
  • Paris reachable, 465 ms
  • Stockholm reachable, 725 ms
  • Sydney reachable, 2312 ms
  • Toronto reachable, 982 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam146 ms11 ms16 ms396 ms
Dallas226 ms32 ms37 ms905 ms
Frankfurt173 ms4 ms9 ms359 ms
Newark268 ms9 ms13 ms768 ms
Paris210 ms11 ms17 ms423 ms
Stockholm209 ms28 ms35 ms585 ms
Sydney796 ms2 ms7 ms2302 ms
Toronto251 ms20 ms38 ms900 ms
We check that api.mailjet.com loads, not every feature behind it. Test it yourself

History

Incidents Mailjet reported

Since Oct 22, 15 days · from status.mailjet.com

Incidents
0
Major or critical
0
Median to resolve
—

No incidents reported in this window.

Mailjet website availability

Measured by FlareWarden · api.mailjet.com

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

Last 30 days

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

Measured by FlareWarden's own checks of api.mailjet.com from multiple regions every 6 hours. Mailjet's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 70 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • 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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Mailjet itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Mailjet goes down

We check Mailjet every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required