Skip to content

Outage tracker / Mailgun

Is Mailgun down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Mailgun from all 10 regions we check.

As of Oct 5, 2026, 9:03 PM UTC, Mailgun answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

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

our independent probeslive · checked Oct 5, 2026, 9:03 PM UTC
US-East523 msOperational
US-West1134 msOperational
Europe755 msOperational
Asia-Pacific989 msOperational
US-Central284 msOperational
Canada182 msOperational
UK704 msOperational
Southeast Asia1515 msOperational
Australia1250 msOperational
South America652 msOperational
their status pagetheir claim, not our reading

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

from Mailgun's own status page, checked Oct 5, 2026, 8:58 PM 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
760msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 560ms2026-09-07 UTC: p95 587ms2026-09-08 UTC: p95 532ms2026-09-09 UTC: p95 563ms2026-09-10 UTC: p95 572ms2026-09-11 UTC: p95 580ms2026-09-12 UTC: p95 602ms2026-09-13 UTC: p95 641ms2026-09-14 UTC: p95 624ms2026-09-15 UTC: p95 608ms2026-09-16 UTC: p95 748ms2026-09-17 UTC: p95 846ms2026-09-18 UTC: p95 815ms2026-09-19 UTC: p95 797ms2026-09-20 UTC: p95 704ms2026-09-21 UTC: p95 653ms2026-09-22 UTC: p95 668ms2026-09-23 UTC: p95 645ms2026-09-24 UTC: p95 731ms2026-09-25 UTC: p95 551ms2026-09-26 UTC: p95 566ms2026-09-27 UTC: p95 619ms2026-09-28 UTC: p95 581ms2026-09-29 UTC: p95 606ms2026-09-30 UTC: p95 555ms2026-10-01 UTC: p95 562ms2026-10-02 UTC: p95 591ms2026-10-03 UTC: p95 681ms2026-10-04 UTC: p95 717ms2026-10-05 UTC: p95 760ms
Sep 6Sep 20Oct 5
US-West
1.1sp95 · 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-09-06 UTC: p95 671ms2026-09-07 UTC: p95 727ms2026-09-08 UTC: p95 634ms2026-09-09 UTC: p95 445ms2026-09-10 UTC: p95 400ms2026-09-11 UTC: p95 409ms2026-09-12 UTC: p95 440ms2026-09-13 UTC: p95 420ms2026-09-14 UTC: p95 405ms2026-09-15 UTC: p95 559ms2026-09-16 UTC: p95 568ms2026-09-17 UTC: p95 558ms2026-09-18 UTC: p95 567ms2026-09-19 UTC: p95 550ms2026-09-20 UTC: p95 607ms2026-09-21 UTC: p95 549ms2026-09-22 UTC: p95 589ms2026-09-23 UTC: p95 526ms2026-09-24 UTC: p95 589ms2026-09-25 UTC: p95 645ms2026-09-26 UTC: p95 637ms2026-09-27 UTC: p95 596ms2026-09-28 UTC: p95 571ms2026-09-29 UTC: p95 549ms2026-09-30 UTC: p95 598ms2026-10-01 UTC: p95 549ms2026-10-02 UTC: p95 535ms2026-10-03 UTC: p95 495ms2026-10-04 UTC: p95 588ms2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
Europe
678msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 702ms2026-09-07 UTC: p95 633ms2026-09-08 UTC: p95 685ms2026-09-09 UTC: p95 668ms2026-09-10 UTC: p95 675ms2026-09-11 UTC: p95 722ms2026-09-12 UTC: p95 735ms2026-09-13 UTC: p95 717ms2026-09-14 UTC: p95 903ms2026-09-15 UTC: p95 911ms2026-09-16 UTC: p95 665ms2026-09-17 UTC: p95 698ms2026-09-18 UTC: p95 696ms2026-09-19 UTC: p95 759ms2026-09-20 UTC: p95 755ms2026-09-21 UTC: p95 737ms2026-09-22 UTC: p95 748ms2026-09-23 UTC: p95 686ms2026-09-24 UTC: p95 757ms2026-09-25 UTC: p95 819ms2026-09-26 UTC: p95 809ms2026-09-27 UTC: p95 845ms2026-09-28 UTC: p95 831ms2026-09-29 UTC: p95 823ms2026-09-30 UTC: p95 750ms2026-10-01 UTC: p95 800ms2026-10-02 UTC: p95 760ms2026-10-03 UTC: p95 699ms2026-10-04 UTC: p95 680ms2026-10-05 UTC: p95 678ms
Sep 6Sep 20Oct 5
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-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 964ms2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 967ms2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 940ms2026-09-20 UTC: p95 957ms2026-09-21 UTC: p95 871ms2026-09-22 UTC: p95 985ms2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 965ms2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 954ms2026-09-29 UTC: p95 968ms2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5
US-Central
658msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 783ms2026-09-07 UTC: p95 734ms2026-09-08 UTC: p95 597ms2026-09-09 UTC: p95 548ms2026-09-10 UTC: p95 601ms2026-09-11 UTC: p95 614ms2026-09-12 UTC: p95 667ms2026-09-13 UTC: p95 612ms2026-09-14 UTC: p95 609ms2026-09-15 UTC: p95 588ms2026-09-16 UTC: p95 614ms2026-09-17 UTC: p95 556ms2026-09-18 UTC: p95 602ms2026-09-19 UTC: p95 593ms2026-09-20 UTC: p95 580ms2026-09-21 UTC: p95 565ms2026-09-22 UTC: p95 581ms2026-09-23 UTC: p95 565ms2026-09-24 UTC: p95 608ms2026-09-25 UTC: p95 590ms2026-09-26 UTC: p95 580ms2026-09-27 UTC: p95 608ms2026-09-28 UTC: p95 570ms2026-09-29 UTC: p95 666ms2026-09-30 UTC: p95 698ms2026-10-01 UTC: p95 642ms2026-10-02 UTC: p95 640ms2026-10-03 UTC: p95 490ms2026-10-04 UTC: p95 607ms2026-10-05 UTC: p95 658ms
Sep 6Sep 20Oct 5
Canada
418msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 558ms2026-09-07 UTC: p95 558ms2026-09-08 UTC: p95 489ms2026-09-09 UTC: p95 476ms2026-09-10 UTC: p95 629ms2026-09-11 UTC: p95 633ms2026-09-12 UTC: p95 573ms2026-09-13 UTC: p95 564ms2026-09-14 UTC: p95 502ms2026-09-15 UTC: p95 448ms2026-09-16 UTC: p95 470ms2026-09-17 UTC: p95 457ms2026-09-18 UTC: p95 463ms2026-09-19 UTC: p95 474ms2026-09-20 UTC: p95 461ms2026-09-21 UTC: p95 452ms2026-09-22 UTC: p95 479ms2026-09-23 UTC: p95 457ms2026-09-24 UTC: p95 557ms2026-09-25 UTC: p95 420ms2026-09-26 UTC: p95 498ms2026-09-27 UTC: p95 577ms2026-09-28 UTC: p95 561ms2026-09-29 UTC: p95 479ms2026-09-30 UTC: p95 580ms2026-10-01 UTC: p95 554ms2026-10-02 UTC: p95 592ms2026-10-03 UTC: p95 467ms2026-10-04 UTC: p95 477ms2026-10-05 UTC: p95 418ms
Sep 6Sep 20Oct 5
UK
1.0sp95 · 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-09-06 UTC: p95 696ms2026-09-07 UTC: p95 574ms2026-09-08 UTC: p95 572ms2026-09-09 UTC: p95 599ms2026-09-10 UTC: p95 617ms2026-09-11 UTC: p95 584ms2026-09-12 UTC: p95 582ms2026-09-13 UTC: p95 620ms2026-09-14 UTC: p95 621ms2026-09-15 UTC: p95 618ms2026-09-16 UTC: p95 752ms2026-09-17 UTC: p95 663ms2026-09-18 UTC: p95 681ms2026-09-19 UTC: p95 699ms2026-09-20 UTC: p95 827ms2026-09-21 UTC: p95 866ms2026-09-22 UTC: p95 810ms2026-09-23 UTC: p95 915ms2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 957ms2026-09-26 UTC: p95 866ms2026-09-27 UTC: p95 994ms2026-09-28 UTC: p95 921ms2026-09-29 UTC: p95 938ms2026-09-30 UTC: p95 980ms2026-10-01 UTC: p95 982ms2026-10-02 UTC: p95 913ms2026-10-03 UTC: p95 725ms2026-10-04 UTC: p95 931ms2026-10-05 UTC: p95 1.0s
Sep 6Sep 20Oct 5
Southeast Asia
1.8sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.6s2026-09-07 UTC: p95 1.7s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.5s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 996ms2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.0s2026-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.9s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.6s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.9s2026-10-05 UTC: p95 1.8s
Sep 6Sep 20Oct 5
Australia
2.0sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.7s2026-09-07 UTC: p95 1.7s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.7s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.5s2026-09-16 UTC: p95 1.8s2026-09-17 UTC: p95 1.6s2026-09-18 UTC: p95 1.6s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.9s2026-10-05 UTC: p95 2.0s
Sep 6Sep 20Oct 5
South America
1.0sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 938ms2026-09-10 UTC: p95 981ms2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 936ms2026-09-13 UTC: p95 1.0s2026-09-14 UTC: p95 813ms2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.5s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.5s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 891ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.8s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.8s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.0s
Sep 6Sep 20Oct 5

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: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Mailgun go down, and when it is back

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.

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

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 523msstatus code: 401checked: Oct 5, 2026, 8:55 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
      Operationallatency: 1134msstatus code: 401checked: Oct 5, 2026, 9:03 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
      Operationallatency: 284msstatus code: 401checked: Oct 5, 2026, 8:54 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
      Operationallatency: 182msstatus code: 401checked: Oct 5, 2026, 8:54 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
    Operationallatency: 652msstatus code: 401checked: Oct 5, 2026, 8:52 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 755msstatus code: 401checked: Oct 5, 2026, 8:56 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
      Operationallatency: 704msstatus code: 401checked: Oct 5, 2026, 9:02 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 989msstatus code: 401checked: Oct 5, 2026, 8:58 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
      Operationallatency: 1515msstatus code: 401checked: Oct 5, 2026, 9:02 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
      Operationallatency: 1250msstatus code: 401checked: Oct 5, 2026, 8:46 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 outages

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
Email Delivery Failures to Microsoft 365 Domains, 1mdeclared on their status page2026-08-17

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

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 last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 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 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.