Is Mailtrap Down?

No — Mailtrap is up

Mailtrap's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 837 ms

Right now

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

Mailtrap's status page

status.mailtrap.info · read 3 minutes ago · checked every 3 minutes

Operational

Mailtrap's components, as its status page reports them
Component	Status
API	Operational
SMTP	Operational
Tracking	Operational
SMTP	Operational
SMTP	Operational
POP3	Operational
Website	Operational

Open their status page

FlareWarden checks

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

Reachable

Regions up: 8 of 8
Response: 837 ms
Checked: 5 hours ago

By region

Ashburn reachable, 229 ms
Frankfurt reachable, 796 ms
Johannesburg reachable, 1775 ms
London reachable, 787 ms
Los Angeles reachable, 598 ms
Newark reachable, 207 ms
São Paulo reachable, 979 ms
Tokyo reachable, 1331 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	115 ms	1 ms	16 ms	220 ms
Frankfurt	27 ms	2 ms	9 ms	617 ms
Johannesburg	92 ms	1 ms	9 ms	1314 ms
London	22 ms	3 ms	17 ms	632 ms
Los Angeles	109 ms	2 ms	10 ms	475 ms
Newark	91 ms	2 ms	12 ms	194 ms
São Paulo	49 ms	2 ms	9 ms	478 ms
Tokyo	8 ms	1 ms	6 ms	974 ms

We check that mailtrap.io loads, not every feature behind it. Test it yourself

History

Incidents Mailtrap reported

Since Oct 27, 10 days · from status.mailtrap.info

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Mailtrap website availability

Measured by FlareWarden · mailtrap.io

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 763ms

Last 30 days

57-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

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

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

Test it yourself

Related services

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. 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 Mailtrap 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 Mailtrap 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 Mailtrap goes down

We check Mailtrap 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