Mailgun incident: Automatic Sender Security Records Not Provisioning

Affected components

• Control Panel

1. resolvedMay 7, 2026, 18:42 UTC

   This incident has been resolved.

2. monitoringMay 7, 2026, 12:40 UTC

   A fix has been implemented and we are monitoring the results.

3. identifiedMay 6, 2026, 19:46 UTC

   We are continuing to work on a fix for this issue.

4. identifiedMay 6, 2026, 15:40 UTC

   Customers creating domains with Automatic Sender Security may have CNAME records with no corresponding TXT records reflecting DKIM keys. A fix for this issue is being prepared.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Mailgun's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• CircleCI: Some Pipelines are being lostMajor · May 6, 2026, 19:42 UTC
• LiveKit: Outbound SRTP calls are failingMajor · May 6, 2026, 19:46 UTC
• Pinecone: [AWS][us-east-1] 5xx errors for some requests on some indexesMajor · May 6, 2026, 20:02 UTC
• Render: HA Postgres UnavailabilityMajor · May 7, 2026, 02:00 UTC
• MongoDB Atlas: AWS Cluster DNS Changes Degraded PerformanceMajor · May 7, 2026, 15:17 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Netlify: Elevated Errors and LatencyMinor · May 6, 2026, 15:29 UTC
• Snyk: Snyk Recurring Tests DelayedMinor · May 6, 2026, 15:32 UTC
• Mux: Elevated rebuffering and playback failuresMinor · May 6, 2026, 16:36 UTC
• Convex: Elevated latency for function calls for some deploymentsMinor · May 6, 2026, 17:43 UTC

How often does Mailgun have incidents?

Mailgun reported 10 incidents in the last 90 days, 5 of them major or critical. A typical incident lasted 1h 17m. See Mailgun's uptime and incident history