Skip to content

Outage tracker / Mailgun

Is Mailgun down?

I'm having a problem

Vendor reports no incidentWhat Mailgun reports

Mailgun reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:01 UTC.

Mailgun's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 2 minutes ago

Our checks of Mailgun pass from all 10 regions we check.

As of Nov 5, 2026, 3:18 PM UTC, RealUptime's checks of Mailgun passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:18 PM UTC
US-East581 msChecks passing
US-West1284 msChecks passing
Europe447 msChecks passing
Asia-Pacific1932 msChecks passing
US-Central563 msChecks passing
Canada713 msChecks passing
UK385 msChecks passing
Southeast Asia2024 msChecks passing
Australia2120 msChecks passing
South America1787 msChecks passing
their status pagetheir claim, not our reading

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

from Mailgun's own status page, checked Nov 5, 2026, 2:26 PM UTC
Mailgun's own status page shows no incident, and our checks of Mailgun pass 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
1.3sp95 · 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-10-07 UTC: p95 699ms2026-10-08 UTC: p95 680ms2026-10-09 UTC: p95 603ms2026-10-10 UTC: p95 635ms2026-10-11 UTC: p95 655ms2026-10-12 UTC: p95 626ms2026-10-13 UTC: p95 664ms2026-10-14 UTC: p95 613ms2026-10-15 UTC: p95 706ms2026-10-16 UTC: p95 792ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.6s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 977ms2026-10-29 UTC: p95 975ms2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
US-West
1.7sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 655ms2026-10-08 UTC: p95 587ms2026-10-09 UTC: p95 567ms2026-10-10 UTC: p95 547ms2026-10-11 UTC: p95 519ms2026-10-12 UTC: p95 634ms2026-10-13 UTC: p95 602ms2026-10-14 UTC: p95 641ms2026-10-15 UTC: p95 624ms2026-10-16 UTC: p95 580ms2026-10-17 UTC: p95 866ms2026-10-18 UTC: p95 997ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.0s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 2s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5
Europe
1.5sp95 · 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-10-07 UTC: p95 675ms2026-10-08 UTC: p95 661ms2026-10-09 UTC: p95 767ms2026-10-10 UTC: p95 816ms2026-10-11 UTC: p95 745ms2026-10-12 UTC: p95 781ms2026-10-13 UTC: p95 755ms2026-10-14 UTC: p95 809ms2026-10-15 UTC: p95 783ms2026-10-16 UTC: p95 707ms2026-10-17 UTC: p95 896ms2026-10-18 UTC: p95 982ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 904ms2026-10-21 UTC: p95 865ms2026-10-22 UTC: p95 893ms2026-10-23 UTC: p95 763ms2026-10-24 UTC: p95 688ms2026-10-25 UTC: p95 707ms2026-10-26 UTC: p95 816ms2026-10-27 UTC: p95 938ms2026-10-28 UTC: p95 830ms2026-10-29 UTC: p95 972ms2026-10-30 UTC: p95 1.0s2026-10-31 UTC: p95 1.0s2026-11-01 UTC: p95 971ms2026-11-02 UTC: p95 1.0s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5
Asia-Pacific
2.7sp95 · latest
10s5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.1s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 2.1s2026-10-23 UTC: p95 2.4s2026-10-24 UTC: p95 2.0s2026-10-25 UTC: p95 2.0s2026-10-26 UTC: p95 2.7s2026-10-27 UTC: p95 6.2s2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 3.0s2026-11-04 UTC: p95 2.8s2026-11-05 UTC: p95 2.7s
Oct 7Oct 21Nov 5
US-Central
1.2sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 621ms2026-10-08 UTC: p95 614ms2026-10-09 UTC: p95 578ms2026-10-10 UTC: p95 512ms2026-10-11 UTC: p95 617ms2026-10-12 UTC: p95 717ms2026-10-13 UTC: p95 752ms2026-10-14 UTC: p95 782ms2026-10-15 UTC: p95 775ms2026-10-16 UTC: p95 820ms2026-10-17 UTC: p95 927ms2026-10-18 UTC: p95 833ms2026-10-19 UTC: p95 648ms2026-10-20 UTC: p95 881ms2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 711ms2026-10-23 UTC: p95 892ms2026-10-24 UTC: p95 835ms2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 956ms2026-10-28 UTC: p95 832ms2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 929ms2026-11-01 UTC: p95 978ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
Canada
1.1sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 462ms2026-10-08 UTC: p95 545ms2026-10-09 UTC: p95 609ms2026-10-10 UTC: p95 626ms2026-10-11 UTC: p95 734ms2026-10-12 UTC: p95 927ms2026-10-13 UTC: p95 762ms2026-10-14 UTC: p95 734ms2026-10-15 UTC: p95 790ms2026-10-16 UTC: p95 781ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 809ms2026-10-23 UTC: p95 732ms2026-10-24 UTC: p95 665ms2026-10-25 UTC: p95 1.0s2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 880ms2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
UK
760msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 942ms2026-10-08 UTC: p95 908ms2026-10-09 UTC: p95 868ms2026-10-10 UTC: p95 690ms2026-10-11 UTC: p95 747ms2026-10-12 UTC: p95 690ms2026-10-13 UTC: p95 690ms2026-10-14 UTC: p95 575ms2026-10-15 UTC: p95 561ms2026-10-16 UTC: p95 563ms2026-10-17 UTC: p95 744ms2026-10-18 UTC: p95 802ms2026-10-19 UTC: p95 905ms2026-10-20 UTC: p95 951ms2026-10-21 UTC: p95 815ms2026-10-22 UTC: p95 991ms2026-10-23 UTC: p95 916ms2026-10-24 UTC: p95 931ms2026-10-25 UTC: p95 901ms2026-10-26 UTC: p95 915ms2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 971ms2026-10-29 UTC: p95 766ms2026-10-30 UTC: p95 997ms2026-10-31 UTC: p95 1.0s2026-11-01 UTC: p95 808ms2026-11-02 UTC: p95 860ms2026-11-03 UTC: p95 824ms2026-11-04 UTC: p95 774ms2026-11-05 UTC: p95 760ms
Oct 7Oct 21Nov 5
Southeast Asia
2.5sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.7s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 2.5s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 2.1s2026-10-24 UTC: p95 1.9s2026-10-25 UTC: p95 1.9s2026-10-26 UTC: p95 2.4s2026-10-27 UTC: p95 2.4s2026-10-28 UTC: p95 2.5s2026-10-29 UTC: p95 2.3s2026-10-30 UTC: p95 2.5s2026-10-31 UTC: p95 2.1s2026-11-01 UTC: p95 2.7s2026-11-02 UTC: p95 2.6s2026-11-03 UTC: p95 3.0s2026-11-04 UTC: p95 2.4s2026-11-05 UTC: p95 2.5s
Oct 7Oct 21Nov 5
Australia
3.0sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 1.9s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 939ms2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 2.0s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 1.9s2026-10-24 UTC: p95 2.0s2026-10-25 UTC: p95 2.1s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 2.2s2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.9s2026-11-01 UTC: p95 2.1s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 4.4s2026-11-04 UTC: p95 3.3s2026-11-05 UTC: p95 3.0s
Oct 7Oct 21Nov 5
South America
2.6sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.7s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 2.6s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 2.4s2026-10-23 UTC: p95 8.4s2026-10-24 UTC: p95 2.1s2026-10-25 UTC: p95 2.1s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 2.3s2026-10-28 UTC: p95 2.7s2026-10-29 UTC: p95 2.3s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.2s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 2.6s2026-11-04 UTC: p95 2.5s2026-11-05 UTC: p95 2.6s
Oct 7Oct 21Nov 5

Check your own site while you wait on Mailgun

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Control PanelUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • DocumentationUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Email ValidationUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • EU APIUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Mailgun reports an incident on its status page, and again when it reports it resolved.

Get an email when Mailgun reports an incident

Email me when Mailgun reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Mailgun's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 581msstatus code: 401checked: Nov 5, 2026, 3:15 PM 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
      Checks passinglatency: 1284msstatus code: 401checked: Nov 5, 2026, 3:11 PM 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.
    • US-Central
      Checks passinglatency: 563msstatus code: 401checked: Nov 5, 2026, 3:12 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Mailgun normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 713msstatus code: 401checked: Nov 5, 2026, 3:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Mailgun normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1787msstatus code: 401checked: Nov 5, 2026, 3:18 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Mailgun normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 447msstatus code: 401checked: Nov 5, 2026, 3:10 PM 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.
    • UK
      Checks passinglatency: 385msstatus code: 401checked: Nov 5, 2026, 3:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Mailgun normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1932msstatus code: 401checked: Nov 5, 2026, 3:00 PM 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.
    • Southeast Asia
      Checks passinglatency: 2024msstatus code: 401checked: Nov 5, 2026, 3:12 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Mailgun normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 2120msstatus code: 401checked: Nov 5, 2026, 3:12 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Mailgun normally. We do not have enough reports from Australia to say anything about what people there are seeing.

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 probe events

Route delays in EU Region, 1h 4mdeclared on their status page2026-10-28
Route delays in EU Region, 42mdeclared on their status page2026-09-30
Route delays in EU Region, 58mdeclared on their status page2026-09-14
EU Messaging Outage, 17mdeclared on their status page2026-09-04
Microsoft Incident Resulting in Delivery Issues to M365, 34mdeclared on their status page2026-09-04
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

check 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 check readings and Mailgun's own claim at the time, side by side.

Full check history for Mailgun: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Mailgun uptime by RealUptime's checksLive, from this page's own readings.
[![Mailgun uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Mailgun down?", https://realuptime.io/outages/mailgun. The readings change with every check, so give the date you read them.

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
secondary
https://app.mailgun.com/
secondary
https://api.mailgun.net/v4/address/validate
secondary
https://api.eu.mailgun.net/v3/domains
secondary
https://documentation.mailgun.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.mailgun.net

RealUptime is not affiliated with Mailgun; the name identifies what we checked, and nothing here speaks for Mailgun's own team. We send a single web request to Mailgun from 10 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.