Skip to content

Outage tracker / Mailgun

Is Mailgun down?

I'm having a problem

Operationalchecked 4 minutes ago

We reached Mailgun from all 4 regions we check.

Functional endpoints verified

No outage recorded in the 10 days we have measured Mailgun (since Aug 22, 2026).

our independent probeslive · checked Sep 1, 2026, 4:06 AM UTC
US-East192 msOperational
US-West218 msOperational
Europe558 msOperational
Asia-Pacific1202 msOperational
their status pagetheir claim, not our reading

Mailgun reports: All systems operational (“All Systems Operational”)

from Mailgun's own status page, checked Sep 1, 2026, 3:27 AM UTC
Our probes and Mailgun's own status page agree: both show Mailgun as reachable right now.

Mailgun's own component breakdown, as they publish it

  • APIOperational
  • Control PanelOperational
  • Email ValidationOperational
  • Inbox PlacementOperational
  • SMTPOperational
  • Outbound DeliveryOperational
  • Spam Trap NetworkOperational
  • Email PreviewsOperational
  • Inbound email processingOperational
  • Events & LogsOperational
  • Stats and AnalyticsOperational

These are Mailgun's components, named and scored by Mailgun. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Mailgun's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Mailgun response time, by region

US-East
597msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 856ms2026-08-23 UTC: p95 1.3s2026-08-24 UTC: p95 796ms2026-08-25 UTC: p95 818ms2026-08-26 UTC: p95 792ms2026-08-27 UTC: p95 588ms2026-08-28 UTC: p95 704ms2026-08-29 UTC: p95 834ms2026-08-30 UTC: p95 850ms2026-08-31 UTC: p95 737ms2026-09-01 UTC: p95 597ms
Aug 3Aug 17Sep 1
US-West
535msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 316ms2026-08-23 UTC: p95 363ms2026-08-24 UTC: p95 533ms2026-08-25 UTC: p95 740ms2026-08-26 UTC: p95 849ms2026-08-27 UTC: p95 776ms2026-08-28 UTC: p95 647ms2026-08-29 UTC: p95 760ms2026-08-30 UTC: p95 879ms2026-08-31 UTC: p95 784ms2026-09-01 UTC: p95 535ms
Aug 3Aug 17Sep 1
Europe
672msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 563ms2026-08-23 UTC: p95 686ms2026-08-24 UTC: p95 751ms2026-08-25 UTC: p95 886ms2026-08-26 UTC: p95 928ms2026-08-27 UTC: p95 785ms2026-08-28 UTC: p95 1.0s2026-08-29 UTC: p95 724ms2026-08-30 UTC: p95 654ms2026-08-31 UTC: p95 706ms2026-09-01 UTC: p95 672ms
Aug 3Aug 17Sep 1
Asia-Pacific
1.2sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 700ms2026-08-23 UTC: p95 1.1s2026-08-24 UTC: p95 1.1s2026-08-25 UTC: p95 1.2s2026-08-26 UTC: p95 1.1s2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 1.1s2026-08-29 UTC: p95 1.1s2026-08-30 UTC: p95 952ms2026-08-31 UTC: p95 1.0s2026-09-01 UTC: p95 1.2s
Aug 3Aug 17Sep 1

Is it Mailgun, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Mailgun -- it cannot diagnose Mailgun's own systems.

What we measured, function by function

Mailgun answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • US-East
    Operationallatency: 192msstatus code: 401checked: Sep 1, 2026, 4:05 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Mailgun normally. We do not have enough reports from US-East to say anything about what people there are seeing.
  • US-West
    Operationallatency: 218msstatus code: 401checked: Sep 1, 2026, 4:02 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Mailgun normally. We do not have enough reports from US-West to say anything about what people there are seeing.
  • Europe
    Operationallatency: 558msstatus code: 401checked: Sep 1, 2026, 4:06 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Mailgun normally. We do not have enough reports from Europe to say anything about what people there are seeing.
  • Asia-Pacific
    Operationallatency: 1202msstatus code: 401checked: Sep 1, 2026, 4:01 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Mailgun normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
  • US-Central
    Not monitored from this regionMailgun is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionMailgun is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionMailgun is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionMailgun is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionMailgun is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionMailgun is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Mailgun, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Mailgun yet, which is not evidence that nothing is wrong.

Recent outages

Event Log Delays in US Region, 7h 14mdeclared on their status page2026-08-31
EU Messaging Outage, 37mdeclared on their status page2026-08-27
GCP Reporting Multi Service Outage in US-West1, 1h 12mdeclared on their status page2026-08-20
Email Delivery Failures to Microsoft 365 Domains, 1mdeclared on their status page2026-08-17
Click and Open Tracking Degraded (US Regions), 1h 35mdeclared on their status page2026-08-11
Route delays in EU Region, 1h 22mdeclared on their status page2026-07-24
US Email Validation 500's and Mailgun Control Panel Unavailable, 1h 32mdeclared on their status page2026-07-13
Mailgun Control Panel Unavailable For Some Users, 2h 4mdeclared on their status page2026-07-10

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Mailgun since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Mailgun covering any window you pick, with our measurements and Mailgun's own claim at the time, side by side.

Full availability history for Mailgun: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Mailgun, and again when they can reach it again. That is our own measurement from ten regions, not Mailgun's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Mailgun uptime measured by RealUptimeLive, from this page's own readings.
[![Mailgun uptime measured by RealUptime](https://realuptime.io/outages/mailgun/badge.svg?days=30)](https://realuptime.io/outages/mailgun)
<a href="https://realuptime.io/outages/mailgun"><img src="https://realuptime.io/outages/mailgun/badge.svg?days=30" alt="Mailgun uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Mailgun's SLA implies, from our measurement

At or above your target

We measured none of downtime for Mailgun over the 244h 10m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 14 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Mailgun's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.mailgun.net/v3/domains
secondary
https://www.mailgun.com/
secondary
https://status.mailgun.com/api/v2/status.json
RealUptime is not affiliated with Mailgun; the name identifies what we measured, and nothing here speaks for Mailgun's own team. We send a single web request to Mailgun from 4 regions on our own schedule and time the response. We do not see inside Mailgun's systems, do not use an account or real transaction, and are not the same signal Mailgun's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Mailgun is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Mailgun operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on August 22, 2026 (10 of 14 days so far, 14546 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.