PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Mailgun is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Mailgun. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Mailgun issues today?

As of Sep 21, 2026 13:51 UTC, 0 users had reported issues with Mailgun in the previous 24 hours.

How can I report a Mailgun outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Communication

Is Mailgun down right now?

NormalOfficial status last polled Sep 21, 2026 12:43 UTCwww.mailgun.com Official status page

Transactional email delivery and email API platform

Are you on the Mailgun team and see something inaccurate? Report it to us. We respond within one business day.

Is Mailgun down right now?

No. Mailgun has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Sep 21, 2026 13:51 UTC

Normal

Mailgun is operating normally

As of Sep 21, 2026 13:51 UTC

No elevated reports in the last 15 minutes. Baseline 4 reports/hour.

Reports 24h

Last incident

Sep 14, 2026 11:41 UTC

Trend

0/15m

Baseline

4/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Mailgun.

Incident days

No recorded incident

9h 50m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Mailgun. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

1 incident

Busiest day

9h 50m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Mailgun outage on May 4 19-minute disruption

May 4, 09:13 PM → May 4, 09:33 PM · 19 minutes · critical

On May 4, 2026, Mailgun experienced a critical service disruption. This incident, which began at approximately 21:13 UTC, was detected through user reports. Service was fully restored at approximately 21:33 UTC.

Peak reports

in 15 min

Total reports

during outage

Duration

19 minutes

until recovery

Impact

Users reported experiencing issues with Mailgun services during the 19-minute disruption. Although specific top issue types and impacted regions were not recorded, the incident was classified as critical due to its impact on service availability. These user reports were instrumental in detecting the outage.

Outage timeline

May 4, 09:13 PM
PulseWatch detected elevated report volume (critical severity)
May 4, 09:15 PM
Peak of 0 reports in 15 minutes (baseline 1.0)
May 4, 09:33 PM
Report volume returned to baseline — incident resolved

Official updates

May 4, 09:13 PM
Mailgun status page acknowledged the incident.
View official source

Reliability

Detected by PulseWatch

30-day uptime

98.6%

90-day uptime

99.50%

Calculated from Mailgun's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other communication services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedMedium

Mailgun: the vendor reports a partial disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

9/14/2026, 9:22:42 AM · 2h 18m

09:22 AM11:41 AM

Detection9/14/2026, 9:22:42 AM · 7d ago

Detected — medium severity

Mailgun: the vendor reports a partial disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

ResolvedMedium