User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 22 min ago. Last stored result reached it in 15 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 219 ms | 0 |
| Mon 22 | 0 | 0.0 | 27 ms | 0 |
| Tue 00 | 0 | 0.0 | 15 ms | 0 |
| Tue 02 | 0 | 0.0 | 17 ms | 0 |
| Tue 04 | 0 | 0.0 | 20 ms | 0 |
| Tue 06 | 0 | 0.0 | 71 ms | 0 |
| Tue 08 | 0 | 0.0 | 29 ms | 0 |
| Tue 11 | 0 | 0.0 | 18 ms | 0 |
| Tue 13 | 0 | 0.0 | 17 ms | 0 |
| Tue 15 | 0 | 0.0 | 14 ms | 0 |
| Tue 17 | 0 | 0.0 | 33 ms | 0 |
| Tue 19 | 0 | 0.0 | 93 ms | 0 |
| Tue 22 | 0 | 0.0 | 27 ms | 0 |
| Wed 00 | 0 | 0.0 | 180 ms | 0 |
| Wed 02 | 0 | 0.0 | 23 ms | 0 |
| Wed 04 | 0 | 0.0 | 13 ms | 0 |
| Wed 07 | 0 | 0.0 | 129 ms | 0 |
| Wed 09 | 0 | 0.0 | 330 ms | 0 |
| Wed 10 | 0 | 0.0 | 215 ms | 0 |
| Wed 13 | 0 | 0.0 | 141 ms | 0 |
| Wed 15 | 0 | 0.0 | 32 ms | 0 |
| Wed 17 | 0 | 0.0 | 37 ms | 0 |
| Wed 19 | 0 | 0.0 | 20 ms | 0 |
| Wed 21 | 0 | 0.0 | 20 ms | 0 |
| Wed 23 | 0 | 0.0 | 23 ms | 0 |
| Thu 02 | 0 | 0.0 | 11 ms | 0 |
| Thu 04 | 0 | 0.0 | 11 ms | 0 |
| Thu 06 | 0 | 0.0 | 224 ms | 0 |
| Thu 08 | 0 | 0.0 | 18 ms | 0 |
| Thu 10 | 0 | 0.0 | 14 ms | 0 |
| Thu 12 | 0 | 0.0 | 17 ms | 0 |
| Thu 14 | 0 | 0.0 | 31 ms | 0 |
| Thu 16 | 0 | 0.0 | 6 ms | 0 |
| Thu 18 | 0 | 0.0 | 91 ms | 0 |
| Thu 19 | 0 | 0.0 | 12 ms | 0 |
| Thu 21 | 0 | 0.0 | 38 ms | 0 |
| Thu 23 | 0 | 0.0 | 131 ms | 0 |
| Fri 01 | 0 | 0.0 | 23 ms | 0 |
| Fri 03 | 0 | 0.0 | 11 ms | 0 |
| Fri 05 | 0 | 0.0 | 249 ms | 0 |
| Fri 07 | 0 | 0.0 | 11 ms | 0 |
| Fri 09 | 0 | 0.0 | 15 ms | 0 |
| Fri 11 | 0 | 0.0 | 18 ms | 0 |
| Fri 13 | 0 | 0.0 | 18 ms | 0 |
| Fri 15 | 0 | 0.0 | 10 ms | 0 |
| Fri 16 | 0 | 0.0 | 16 ms | 0 |
| Fri 18 | 0 | 0.0 | 17 ms | 0 |
| Fri 19 | 0 | 0.0 | 15 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Mailjet yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Mailjet goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Mailjet alerts to Slack, Discord or a webhook — free.
We track Mailjet (mailjet.com) as part of the AI group. Design, deliver, and automate marketing & transactional emails together with built-in deliverability, GDPR compliance, and developer-ready email APIs
Mailjet publishes an official status page at status.mailjet.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 42 ms average, 10–249 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Mailjet incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
42 ms on average over the last 24 hours (10–249 ms).
Yes, at https://status.mailjet.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Mailjet here at once, the problem is on Mailjet's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Mailjet. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.