# How to Monitor Mailgun Uptime

> Mailgun is a transactional email API service used to send password resets, receipts, notifications, and other critical emails programmatically.

*Source: https://monitoristic.com/monitor/mailgun*

---

## Why Monitor Mailgun?

Email is invisible until it stops. When Mailgun's API is unreachable or your sending breaks, password resets don't arrive, receipts go missing, and signup confirmations vanish — and there's no error page to warn you. By the time customers complain that they 'never got the email,' the failure has been running for hours. Monitoring the API endpoint your app calls closes that gap.

## What to Monitor

- `api.mailgun.net` — Mailgun's API host that your app sends through
- `your-app.com/api/health/email` — An app endpoint that verifies the email pipeline is reachable
- `status.mailgun.com` — Mailgun's platform status for service-level incidents

## What You Should Actually Do

1. Monitor api.mailgun.net — the API host your app actually sends through
2. Add a health endpoint in your app that verifies the email pipeline is reachable, and monitor it
3. Set up alerts on an independent channel — don't rely on email to tell you email is down
4. Watch for slow responses from the API — degraded send latency often precedes outright failures
5. Bookmark Mailgun's status page for platform incidents, but trust your own monitor for integration-specific breaks

## Mailgun's Official Status Page

Mailgun publishes real-time status at https://status.mailgun.com. Your own monitor complements it by catching connection-level issues, often before the status page updates.

## Takeaway

Transactional email fails quietly — no error page, no crash, just users who never get the message. By the time 'I didn't get the email' tickets arrive, the failure has been running for hours. You can't watch Mailgun's servers, but you can monitor the API host your app sends through and a health endpoint that exercises the email path. That turns a silent, hours-long outage into a 60-second alert.

## Frequently Asked Questions

### Can I monitor whether Mailgun is sending my emails?

You can monitor the Mailgun API host (api.mailgun.net) for reachability, and build a health endpoint in your app that verifies the email pipeline is working. Together these catch both Mailgun-side outages and integration breaks that stop your sends.

### Why didn't my app error when email sending broke?

Most apps handle email sending asynchronously and don't crash when a send fails — that's good for stability but means email failures are silent. Monitoring the API host and an email-path health endpoint surfaces the failure that your app intentionally swallowed.

### What's the best way to get alerted about email failures?

Use an alert channel that doesn't depend on email — Telegram or a webhook. If your only alert path is email and email is the thing that's broken, you won't get the notification.

### How is this different from Mailgun's status page?

Mailgun's status page reports platform-wide incidents. It won't tell you that your API key expired, your domain's sending was suspended, or your specific integration broke after a code change. Only monitoring your own email path catches those.