Loading status…
Loading status…
Mailgun status · Communication · checked (2s ago)
No — Mailgun is not down. All Mailgun systems are reported operational.
According to Mailgun's official status page, Mailgun was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Mailgun's feed reported no outage in 99.93% of our checks.
Everything above is read from Mailgun's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Mailgun in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Mailgun sends transactional email through an API and SMTP, with routing, validation and inbound parsing attached. Password resets, receipts and notifications are the traffic, so an outage is felt as email that silently does not arrive.
The status page separates the API from actual message delivery and from inbound routing and the dashboard. Delivery is the component that matters and the hardest one to read, because Mailgun accepting a message says nothing about whether a recipient's provider accepted it — the queue can be healthy while mail to one large mailbox provider is being deferred.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Mailgun's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Mailgun was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 2s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Mailgun's status endpoint.
Mailgun has published 33 incidents in the last 12 months, the 20 most recent shown here. Only what Mailgun posted itself — not every problem users hit.
resolved · Sep 14, 09:15 AM (5d ago)
resolved · Sep 4, 02:16 PM (15d ago)
resolved · Sep 4, 12:20 PM (15d ago)
resolved · Aug 31, 02:47 PM (19d ago)
resolved · Aug 27, 08:38 PM (23d ago)
resolved · Aug 20, 04:19 PM (30d ago)
resolved · Aug 17, 08:18 PM (33d ago)
resolved · Aug 11, 05:32 AM (40d ago)
resolved · Jul 24, 12:27 PM (57d ago)
resolved · Jul 13, 06:23 PM (68d ago)
resolved · Jul 10, 06:07 PM (71d ago)
resolved · Jun 25, 07:21 PM (86d ago)
resolved · Jun 23, 09:14 AM (88d ago)
resolved · Jun 18, 08:34 AM (93d ago)
resolved · Jun 16, 02:28 PM (95d ago)
resolved · Jun 5, 01:26 PM (106d ago)
resolved · Jun 4, 06:01 PM (107d ago)
resolved · May 25, 12:18 PM (117d ago)
resolved · May 6, 03:40 PM (136d ago)
resolved · Apr 17, 04:45 PM (155d ago)
Check the logs in the Mailgun dashboard for the specific message: a bounce, a suppression-list entry or a spam rejection is a delivery outcome, not an outage. Unverified sending domains and missing SPF, DKIM or DMARC records cause silent rejection at the recipient. Sandbox domains only send to pre-authorised addresses, which catches new integrations constantly.
Mailgun is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
Status shown for each is read from that provider's own feed, on the same schedule as this page.