Is Mailgun down right now?

No. Our checks are finding no problems with Mailgun right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Mailgun continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

The problems visitors report most often on this page are email not arriving, API errors, webhooks not firing, no response / timing out, 5xx error pages, can't connect and rate limited. Those are the options the report button offers for Mailgun, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Mailgun specifically, Mailgun has regional endpoints and separate inbound/outbound infrastructure, so your sending region or webhook receiver may be affected while other regions work, and inbound mail handling can fail independently of outbound delivery. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

For Mailgun, send one message from the dashboard, then open the Logs tab. Mailgun records the receiving server's own response there, which tells a message it never accepted apart from one the recipient's provider bounced, deferred or filtered after delivery. A problem that follows you across networks and devices is very unlikely to be yours.

If this page shows evidence of problems, the fault is most likely on Mailgun's side. Specifically: do not retry sends in a tight loop. Failed attempts still count against your quota, and the duplicates all arrive together the moment the queue drains. Hold the failures and retry with exponential backoff once delivery recovers. Reporting it here helps other people see they are not alone.

Continuously, around the clock. Mailgun publishes a machine-readable status feed, so our first check reads it directly and reports what Mailgun itself says. If that feed is unreachable we fall back to a direct HTTP probe, then an ICMP ping, then reports from visitors. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

Yes, at status.mailgun.com, and it is linked further up this page. That is Mailgun's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Mailgun or mailgun.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Mailgun's own support, not us.