Is Mailgun Down Right Now?
Emails not sending, webhooks gone silent, or API calls failing? This guide separates a real Mailgun platform outage from domain, DNS, and webhook configuration issues, with a step-by-step diagnostic playbook.
The average API outage costs $5,600 per minute
Gartner estimates downtime costs $5,600/min on average. 98% of organizations say a single hour of downtime costs over $100,000. Proactive monitoring catches issues in under 30 seconds.
📡 Monitor your APIs — know when they go down before your users do
Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.
Affiliate link — we may earn a commission at no extra cost to you
Check Mailgun Status Now
Mailgun publishes health for the Sending API, inbound routing, and webhooks across US and EU regions:
Mailgun Service Components
Mailgun is made up of several independently operating systems. A webhook delay does not mean the Sending API is down — narrow down which component is actually affected first.
Core transactional and marketing email send endpoint
Receives and routes mail to your application via webhooks
delivered, opened, clicked, bounced, complained event notifications
Real-time and bulk email address validation
Dashboard for domains, logs, templates, and analytics
Isolated EU sending infrastructure (api.eu.mailgun.net)
Monitor your transactional email pipeline end-to-end
Mailgun accepting a request is not the same as an email arriving. Better Stack lets you monitor the full send path and alert on delivery failures before customers complain.
Try Better Stack Free →Diagnostic Playbook
Work through these steps in order to isolate whether the problem is Mailgun's platform, your domain configuration, or a receiving-server issue.
Check status.mailgun.com
Look for active incidents on the Sending API, inbound routing, or webhooks — filtered by US or EU region.
→ Mailgun Status PageCheck the API response, not just "it didn't arrive"
A 200/202 from the Sending API means Mailgun accepted the message — the failure is downstream. A 4xx/5xx means Mailgun rejected the request itself; read the error body for the exact reason.
Check Logs for the specific message
In the Mailgun dashboard, search Logs by recipient or message ID to see delivered, bounced, or rejected events with the exact SMTP response from the receiving server.
Verify domain authentication
Go to Sending > Domains and confirm SPF, DKIM, and tracking CNAME all show "Verified". Unverified domains are the single most common cause of silent send failures.
Test the webhook endpoint directly
curl your webhook URL manually to confirm it returns 200 quickly. If it is slow or erroring, Mailgun will retry a few times then disable the webhook.
Platform Outage vs Deliverability Issue: Who Owns the Fix?
☁️ Mailgun Platform
- • Check status.mailgun.com for US/EU incidents
- • Subscribe to incident email or RSS updates
- • Open a support ticket for account-specific throttling
- • No fix on your end — wait for Mailgun to resolve it
- • SLA-backed uptime on paid plans
📬 Your Domain / Deliverability
- • Verify SPF, DKIM, and DMARC in Sending > Domains
- • Check Logs for bounce/reject reasons per message
- • Confirm domain is not still on the sandbox tier
- • Review sending reputation and complaint rate
- • Re-test webhook endpoint returns 200 quickly
Why Mailgun Emails Bounce or Never Arrive
An accepted API call is not a delivered email — these are the most common gaps between "sent" and "received".
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
Frequently Asked Questions
Is Mailgun down right now?
Check the official Mailgun status page at status.mailgun.com, which reports the health of the Sending API, inbound routing, webhooks, and the control panel by region (US and EU). If the status page is green but your emails still are not sending, the issue is almost always domain verification, API key, or DNS-related — not a platform outage.
Why are my Mailgun emails not sending?
Emails fail to send through Mailgun for several common reasons: (1) domain not verified — check SPF, DKIM, and CNAME records in the Mailgun dashboard, (2) using the wrong API base URL for your region (api.mailgun.net for US vs api.eu.mailgun.net for EU), (3) sending domain still on the sandbox tier, which only delivers to authorized recipients, (4) API key revoked or rate-limited, (5) recipient domain rejecting mail due to your sending reputation. Check the Mailgun Logs tab for the specific rejection reason on each message.
Why did my Mailgun webhook stop firing?
Mailgun webhooks (delivered, opened, clicked, bounced, complained) silently stop for these reasons: (1) your webhook endpoint started returning non-2xx responses and Mailgun disabled it after repeated failures — check Webhooks settings for a "disabled" flag, (2) the webhook signing key changed and your verification is rejecting valid requests, (3) your endpoint is timing out — Mailgun expects a fast response, not one that waits on downstream processing, (4) a firewall or WAF is blocking Mailgun's outbound IP ranges. Re-enable the webhook in the dashboard and confirm your endpoint returns a 200 within a few seconds.
What is the difference between a Mailgun outage and my own deliverability problem?
A Mailgun outage means the API itself is unreachable or returning 5xx errors for all customers — visible on status.mailgun.com. A deliverability problem is specific to your sending domain: poor sender reputation, missing SPF/DKIM/DMARC alignment, high bounce or complaint rates, or a recipient ISP throttling your traffic. The fastest way to tell them apart: if the API accepts your send request (200/202 response) but the message never arrives, that is deliverability, not an outage — check the message logs for the bounce or reject event.
How do I get alerted when Mailgun itself goes down?
Subscribe to status.mailgun.com directly, but also add independent monitoring since transactional email outages are business-critical. Options: (1) Better Stack — synthetic checks against the Mailgun API endpoint your app uses, with SMS/Slack/PagerDuty alerts, (2) API Status Check — tracks Mailgun status history so you can correlate send failures with real incidents, (3) an internal dead-man's-switch that alerts if no "delivered" webhook events arrive within an expected window.
🛠 Tools We Use & Recommend
Tested across our own infrastructure monitoring 200+ APIs daily
Uptime Monitoring & Incident Management
Used by 100,000+ websites
Monitors your APIs every 30 seconds. Instant alerts via Slack, email, SMS, and phone calls when something goes down.
“We use Better Stack to monitor every API on this site. It caught 23 outages last month before users reported them.”
Secrets Management & Developer Security
Trusted by 150,000+ businesses
Manage API keys, database passwords, and service tokens with CLI integration and automatic rotation.
“After covering dozens of outages caused by leaked credentials, we recommend every team use a secrets manager.”
SEO & Site Performance Monitoring
Used by 10M+ marketers
Track your site health, uptime, search rankings, and competitor movements from one dashboard.
“We use SEMrush to track how our API status pages rank and catch site health issues early.”