Is Mailgun down?
For agents
proceed
Proceed.
GET upbutler.com/status/mailgun/status.agent.json
MCP: upstream_status {"service":"mailgun"}
Email sending, routing and validation.
What Mailgun reports
Operational
Taken as is from Mailgun's own status page API. Incident titles and component names below are theirs.
Open status.mailgun.comUpButler's independent probe
There is no keyless endpoint of Mailgun that says anything useful, so UpButler does not probe it. To check your own Mailgun account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Mailgun components
11 operational
Email Services
- APIOperational
- SMTPOperational
- Outbound DeliveryOperational
- Inbound email processingOperational
- Events & LogsOperational
- Stats and AnalyticsOperational
Customer Tools
- Control PanelOperational
Deliverability Services
- Email ValidationOperational
- Inbox PlacementOperational
- Spam Trap NetworkOperational
- Email PreviewsOperational
Mailgun incidents, last 90 days
1 finished incident seen since UpButler started tracking on 2026-10-10.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| Route delays in EU Region | minor | 42 min |
Tell your outage from Mailgun's
Declare that your project depends on Mailgun. When one of your monitors fails while Mailgun has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- mailguncurl -s https://upbutler.com/status/mailgun/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "mailgun",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Mailgun down right now?
- No. As of 2026-10-10 05:12 UTC, Mailgun is operational. This page reads the status again every 2 minutes.
- Where does this status come from?
- From Mailgun's own status page API at https://status.mailgun.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Mailgun's words.
- How can my agent or app check Mailgun status?
- Fetch https://upbutler.com/status/mailgun/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"mailgun"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Mailgun's?
- Add "mailgun" to the dependencies of your UpButler workspace. When one of your monitors fails while Mailgun has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in email
UpButler is not affiliated with Mailgun. Status and incident text belong to Mailgun and are read from their public status source; the probe result is UpButler's own measurement.