Mailgun: SSL certificate update
Timeline of updates
- resolved
On January 22nd at around 5:00PM CT, Mailgun completed an update to the SSL certificates we use in order to correct numerous certificates that did not comply with the industry-developed CA/Browser Forum Baseline Requirements by Symantec’s PKI business. You can read more about this here - https://security.googleblog.com/2017/09/chromes-plan-to-distrust-symantec.html (opens in new tab). While this was intended to be a non-breaking change, we received multiple reports from clients utilizing Mailgun that they were receiving errors related to SSL. If you are receiving errors while attempting to send messages using Mailgun, you will need to update your local CA bundle. The steps for this vary depending on your OS, SMTP library or coding language that you are using and we recommend consulting the documentation for your application on how to update this locally. If you are still unsure, please reach out to our support team for assistance.
From Mailgun’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.mailgun.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Mailgun, started 2018-01-22 20:00 UTC, resolved after 0 min, 1 update(s).
- Title
- SSL certificate update
- Vendor
- Mailgun
- Date
- URL
- https://rewindex.com/company/mailgun/incidents/0y2g8f3cvvz5
Mailgun profileRecent Mailgun incidentsAll outages on January 22, 2018Mailgun in January 2018MarkdownJSON