Skip to main content
Mailtrap logo

Is Mailtrap Down?

No — Mailtrap is up

Reachable from all 8 checked regions

Average response time: 611ms

Last checked · checks run every 6 hours

Official status page: https://status.mailtrap.info

Mailtrap uptime

96.14%
Last 7 days
97.48%
Last 30 days
97.48%
Last 90 days
1071ms
Avg response, 30 days

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

30-day history

5-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: no data
Aug 29: no data
Aug 30: no data
Aug 31: no data
Sep 1: no data
Sep 2: no data
Sep 3: no data
Sep 4: no data
Sep 5: no data
Sep 6: no data
Sep 7: no data
Sep 8: no data
Sep 9: no data
Sep 10: 100.00% uptime, 16 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 31 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 66.67% uptime, 24 checks
Sep 16: 100.00% uptime, 31 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 24 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
344ms
DNS 139ms TCP 2ms TLS 27ms TTFB 332ms
arn
1189ms
DNS 187ms TCP 1ms TLS 14ms TTFB 948ms
bom
1441ms
DNS 32ms TCP 3ms TLS 11ms TTFB 1069ms
cdg
347ms
DNS 116ms TCP 2ms TLS 10ms TTFB 305ms
dfw
268ms
DNS 147ms TCP 1ms TLS 7ms TTFB 256ms
ewr
229ms
DNS 91ms TCP 4ms TLS 12ms TTFB 213ms
fra
823ms
DNS 133ms TCP 1ms TLS 9ms TTFB 649ms
yyz
252ms
DNS 84ms TCP 1ms TLS 10ms TTFB 201ms

What Mailtrap does

Mailtrap offers two things that fail very differently. Email Testing is a sandbox that captures messages from staging and development so teams can inspect them without mail reaching real people. Email Sending delivers production transactional and marketing mail over SMTP or an API, with open and click tracking and thirty days of logs. One serves engineering, the other serves customers.

What an outage looks like

On the testing side, automated tests and continuous integration jobs that assert on captured mail hang or fail, and messages stop appearing in the sandbox inbox during manual QA. On the sending side, production email stops reaching customers, applications calling the API or SMTP endpoint receive errors, and delivery logs stop updating so there is no record to check.

What to do about it

Read status.mailtrap.info, which publishes an overall state rather than a per-component breakdown, so it will not tell you which half of the product is affected. Establish that yourself: try a send on the path you care about and see which one fails. If testing is affected and sending is not, pause pipelines that gate on captured mail rather than letting them fail repeatedly.

Is it down for everyone, or just you?

If this page says Mailtrap 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

Postmark
Postmark
Mailgun
Mailgun
Resend
Resend
SendGrid (Twilio)
SendGrid (Twilio)

Mailtrap outage FAQ

Which part of Mailtrap is down, testing or sending?
The status page will not tell you directly. Mailtrap publishes an overall status rather than separate components for the sandbox and for production sending, so a single all-clear or a single incident notice covers both halves. Test each path yourself: send one message through the sandbox and one through your production sending credentials. Knowing which half is affected changes whether the problem is a blocked pipeline or missing customer email.
Are emails from my staging environment reaching real people during an outage?
They should not be, and the design is what protects you. The sandbox exists to capture messages so they never leave for real recipients, so a failure there means messages are not captured rather than that they escape. The risk to watch is a fallback in your own configuration that switches to a real sending route when the sandbox is unreachable. Check that your staging environment has no such fallback.
My CI pipeline hangs waiting for a test email. What should I do?
Stop the run rather than letting it retry. A pipeline that waits on a message appearing in the sandbox will sit until it times out, and repeated runs during an incident add load without changing the outcome. Pause the jobs that depend on captured mail, let unrelated jobs continue, and re-run the mail-dependent ones once the service recovers rather than marking them as genuine failures.
Will production email sent during a Mailtrap outage be lost?
A message that Mailtrap accepted before a delivery problem is generally retried onward, while a send attempt that returned an error to your application was never accepted. Mailtrap does not publish retry behaviour covering every failure mode, so check your own application logs for calls that failed and treat those specific messages as unsent. Its thirty days of email logs are the record to compare against on recovery.
Is it Mailtrap or my own credentials?
Compare scope. A wrong API token, an expired sandbox inbox credential or a blocked SMTP port affects one environment and returns a specific authentication or connection error, and the other environment keeps working. A Mailtrap incident affects both paths or a whole region of the service at once. Check the status page before rotating credentials, since rotating mid-incident leaves you unsure which change resolved it.

How we measure this

  • We request Mailtrap'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 Mailtrap 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 Mailtrap 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