Skip to main content
Mailgun logo

Is Mailgun Down?

No — Mailgun is up

Reachable from all 8 checked regions

Average response time: 431ms

Last checked · checks run every 6 hours

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

Mailgun uptime

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

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

30-day history

61-day clean streak
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 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, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 31 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 31 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
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: no data
Sep 13 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
507ms
DNS 57ms TCP 6ms TLS 296ms TTFB 507ms
lhr
402ms
DNS 113ms TCP 3ms TLS 190ms TTFB 402ms
nrt
681ms
DNS 58ms TCP 1ms TLS 415ms TTFB 681ms
ord
144ms
DNS 26ms TCP 21ms TLS 65ms TTFB 144ms
sin
774ms
DNS 151ms TCP 1ms TLS 414ms TTFB 774ms
sjc
151ms
DNS 25ms TCP 12ms TLS 76ms TTFB 151ms
syd
558ms
DNS 135ms TCP 1ms TLS 281ms TTFB 558ms
yyz
232ms
DNS 41ms TCP 1ms TLS 127ms TTFB 232ms

What Mailgun does

Mailgun is a transactional email service that applications call by API or SMTP to send password resets, receipts and notifications. Its status page separates the sending path from the deliverability tools, listing API, SMTP, Outbound Delivery, Inbound email processing, Events and Logs and Stats and Analytics apart from Email Validation, Inbox Placement and the Spam Trap Network.

What an outage looks like

Send calls fail or time out at the API or SMTP boundary, so the application knows immediately that the message did not leave. Harder to spot: accepted messages that sit undelivered when Outbound Delivery degrades, where the API returns success and recipients get nothing. Click and open tracking can fail on its own while delivery continues normally.

What to do about it

Read status.mailgun.com and separate acceptance from delivery: an API or SMTP incident means your sends failed and can be retried, while an Outbound Delivery incident means they were accepted and are queued. Do not re-send messages Mailgun already accepted until delivery recovers, or recipients get duplicates. Events and Logs is where you confirm which of the two happened.

Is it down for everyone, or just you?

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

Mailgun outage FAQ

Mailgun accepted my message but it never arrived. Is that an outage?
Acceptance and delivery are separate components. The API returning success means Mailgun took the message, not that it reached the recipient, and an Outbound Delivery incident leaves accepted mail queued. Check the Outbound Delivery line on status.mailgun.com and then the Events and Logs view for that message before assuming it was lost.
Should I retry sends that failed during an outage?
Retry the ones that failed at the API or SMTP boundary, since those messages never entered Mailgun. Do not retry messages Mailgun accepted, because they are queued and will send once delivery recovers, producing duplicates. The response your application received at send time is what distinguishes the two, so check your own logs first.
Why did open and click tracking stop when email is still sending?
Tracking is handled separately from delivery, and Mailgun reported a Click and Open Tracking degradation in the US regions in August 2026 while sending continued. A tracking incident means your engagement numbers for that window are understated, not that recipients failed to receive the mail. Treat the gap as a measurement gap rather than a delivery problem.
Does a Mailgun outage affect inbound email and validation too?
Not necessarily. Inbound email processing, Email Validation, Inbox Placement and the Spam Trap Network are listed as their own components, separate from the outbound path. Inbound routing can fail while sending works, and validation can be down while both work. Read the specific line for the feature you depend on rather than the top-level banner.

How we measure this

  • We request Mailgun'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 Mailgun 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 Mailgun goes down

This page refreshes every 6 hours. 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