Mailgun Status: How to Check If Mailgun Is Down Right Now (2026)
Updated June 2026 · 7 min read · By API Status Check
Quick Answer: Check Mailgun Status Now
Mailgun is one of the most widely-used transactional email APIs — trusted by developers at companies ranging from startups to Fortune 500s to send billions of emails per month. When Mailgun experiences downtime or delivery degradation, the impact is immediate: password reset emails don't arrive, order confirmations go missing, and user notifications stack up in a queue. Knowing how to diagnose a Mailgun problem — and whether it's actually an outage or a deliverability issue — is essential for any developer relying on email infrastructure.
Understanding Mailgun's Status Page (status.mailgun.com)
Mailgun operates status.mailgun.com — its official status page powered by Atlassian Statuspage. Mailgun separates status by region and component, so you can pinpoint whether your specific integration is affected.
API (US Region)
The Mailgun REST API at api.mailgun.net — the primary integration endpoint for most developers. Issues here affect all programmatic email sends in the US region.
API (EU Region)
The Mailgun EU API at api.eu.mailgun.net — separate infrastructure for GDPR-compliant EU email sending. US region issues do not affect EU region and vice versa.
SMTP (US)
Sending email via smtp.mailgun.org — used by applications that integrate via SMTP relay rather than the REST API. Tracked separately from the API component.
SMTP (EU)
EU-based SMTP relay at smtp.eu.mailgun.org — independently tracked for EU region senders.
Webhooks
Mailgun webhook delivery for email events (delivered, opened, clicked, bounced, failed). Webhook delays affect your ability to track email engagement in real time.
Control Panel / Dashboard
The Mailgun web interface at app.mailgun.com for managing domains, viewing logs, and configuring settings. Dashboard issues typically don't affect email delivery.
What Mailgun Status Colors Mean
Monitor Mailgun email delivery automatically
Better Stack lets you create monitors for Mailgun and your entire email infrastructure. Get Slack, PagerDuty, or SMS alerts the moment Mailgun API calls start failing — before users notice missing transactional emails. Free plan available.
Try Better Stack Free →5 Ways to Check If Mailgun Is Down
status.mailgun.com (Official)
Mailgun's own status page. Updated by their engineering team during incidents. Can lag 10–20 minutes behind actual outages, especially for deliverability issues that manifest slowly in delivery metrics.
Check status.mailgun.com →API Status Check (Independent)
Third-party monitoring that continuously pings Mailgun API endpoints and reports independently of Mailgun's own status page. Shows infrastructure issues even before Mailgun engineers update their status page.
Check independent Mailgun status →X / Twitter
Search 'Mailgun down' or 'Mailgun not sending' on X. Developers report transactional email failures in real time. Useful for confirming widespread vs isolated issues.
Search X for 'Mailgun down' →Test the Mailgun API directly
Make a test API call to your Mailgun sending endpoint. A 200 response with a message ID means Mailgun accepted the email — check your inbox to verify actual delivery. Use your sandbox domain for safe testing.
curl -s --user 'api:YOUR_API_KEY' \
https://api.mailgun.net/v3/YOUR_DOMAIN/messages \
-F from='test@YOUR_DOMAIN' \
-F to='delivered@example.com' \
-F subject='Mailgun Test' \
-F text='Testing Mailgun status'Check Mailgun Logs Dashboard
Log in to app.mailgun.com → Logs. Filter by your domain and recent time window to see real-time event data: delivered, failed, bounced, queued. Mass 'failed' or 'queued' events without deliveries confirm an active issue.
Open Mailgun Logs Dashboard →Mailgun Error Codes: Outage vs. Deliverability Issue
The biggest source of confusion when Mailgun emails stop arriving: is it a Mailgun infrastructure outage or a deliverability problem? Here's how to tell the difference by HTTP status code and log event:
"HTTP 200 (Queued/Accepted) — no email arrives"Mailgun accepted the email but delivery is delayed or filtered by the receiving inbox provider. Check your Logs dashboard for 'failed' or 'bounced' events. This is NOT a Mailgun infrastructure outage."HTTP 401 Unauthorized"Invalid, expired, or missing API key. Not an outage — verify your API key in app.mailgun.com under Settings → API Keys. Make sure you're using the correct key for your sending region (US vs EU)."HTTP 400 Bad Request"Malformed request — missing required fields (from, to, subject, text/html). Not an outage — check your API call structure against the Mailgun docs."HTTP 429 Too Many Requests"You've hit Mailgun's rate limit. Not an outage — implement exponential backoff and respect the Retry-After header in the response."HTTP 500 / 503 Internal Server Error"Mailgun API servers are temporarily unavailable. This IS a real outage signal — check status.mailgun.com immediately and queue emails locally for retry."Logs show 'failed' with error code 550"Hard bounce — the destination address doesn't exist or permanently rejected the message. Not an outage — remove this address from your mailing list immediately."Logs show 'failed' with error code 421"The receiving mail server temporarily rejected the message (soft bounce). Could be their spam filter or a rate limit on their end. Mailgun will typically retry these automatically.Mailgun US vs EU Region: Which Are You On?
A common source of confusion: Mailgun runs two completely independent infrastructure regions. If you're hitting API errors, make sure you're calling the right endpoint for your domain's region.
US Region
- API endpoint:
api.mailgun.net - SMTP:
smtp.mailgun.org - Default region for most accounts
- Tracked separately on status.mailgun.com
- Data stored in US data centers
EU Region
- API endpoint:
api.eu.mailgun.net - SMTP:
smtp.eu.mailgun.org - Must be explicitly selected during domain setup
- Required for GDPR compliance (EU data residency)
- Independent status from US region
Mailgun Reliability: What the Data Shows
True Mailgun infrastructure outages are uncommon. The more frequent problem is email deliverability degradation — emails accepted by Mailgun but filtered by Gmail, Yahoo, or Outlook. Monitor both your API acceptance rate AND your actual delivery and open rates to catch these earlier. Check our Mailgun monitoring for current and historical uptime data.
Get alerted when Mailgun goes down
Better Stack monitors Mailgun and your full email stack. When API calls start failing or delivery rates drop, you hear about it before users report missing emails. Set up independent monitoring in 2 minutes.
Try Better Stack Free →What to Do When Mailgun Is Down
If the API Is Returning Errors
- Confirm it's a Mailgun outage: check status.mailgun.com for your region
- Queue emails locally — don't discard them, retry when service recovers
- For critical transactional emails, consider AWS SES or Postmark as fallback
- Implement retry logic with exponential backoff (start at 1s, cap at 60s)
- Alert users proactively if time-sensitive emails (OTPs, resets) will be delayed
If Emails Aren't Delivering (But API Accepts)
- Check Mailgun Logs for event codes (bounced, failed, queued)
- Verify your sending domain's DKIM, SPF, and DMARC records
- Test delivery to multiple inbox providers (Gmail, Yahoo, Outlook)
- Check if your sending IP is on a blocklist via MXToolbox
- Review domain reputation in Google Postmaster Tools
Frequently Asked Questions
Where is the official Mailgun status page?
Mailgun's official status page is at status.mailgun.com. It shows real-time status for the Mailgun API, SMTP relay, webhooks, and control panel — separately for US and EU regions. You can subscribe to email or SMS incident notifications.
Why are Mailgun emails not arriving but the status page shows operational?
Most Mailgun 'outages' are actually deliverability issues. Mailgun accepts and sends the email, but Gmail, Yahoo, or another inbox provider filters it. Check your Mailgun Logs dashboard for bounce codes and event types. True infrastructure outages where the API rejects requests are much rarer.
Does a Mailgun outage mean emails are lost?
Not necessarily. Mailgun queues emails for retry during brief outages. If the API accepted your request (HTTP 200 with a message ID), Mailgun has the email and will attempt delivery. If the API is rejecting requests (5xx errors), queue emails in your own system and retry. Mailgun's default queue TTL is 24-48 hours.
What's the best Mailgun alternative when it's down?
For transactional email: AWS SES (lowest cost at scale), Postmark (best deliverability reputation), and SendGrid (most feature-rich) are the most common fallbacks. Many production systems use a primary provider + fallback strategy for critical transactional emails like password resets.
How do I get alerts when Mailgun goes down?
Subscribe to email or SMS notifications at status.mailgun.com, or use Better Stack or API Status Check Alert Pro for independent monitoring of Mailgun API availability. For the most complete coverage, also monitor your own delivery success rates — deliverability degradation often doesn't appear on Mailgun's status page.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Mailgun goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Mailgun + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial