On August 4th at 22:20 UTC, Mailgun was alerted to numerous reports of DNS resolution failures for our mailgun.net domain name, which is the primary domain name we use for our API. As we began investigating, we discovered that our domain had been placed in “client hold” state by our domain registrar, Dynadot.
This was originally reported on May 31, 2016. Mailgun recently incurred several separate incidents that impacted the availability of our services. We’d like to take this opportunity to provide our customers with visibility around the root cause of these incidents along with details on what we’ve done to address them and ensure they do not occur again in the future.
We’re excited to announce the integration of Mailgun with Form.io, an open‐source combined FORM and API creation and management platform designed specifically for application developers. Form.io embeds FORMS directly into distributed front-end and mobile applications with a single line of HTML code, while at the same time updating all API interfaces into legacy and 3rd-party systems in real-time.
This was originally announced on December 28, 2015. We didn’t want to close up 2015 without releasing one more feature for our customers. We’re pleased to announce Multi-User Access where users can now create multiple users for one account.
We know Mailgun users want to know what’s going on with their email. Back in May, we made some significant updates to our dashboard allowing users to check the delivery performance of their email. Today, we’re pleased to announce updates to our Stats API providing users the opportunity to capture more data about their emails.
Over a year ago Mailgun flipped on opportunistic TLS. This means whenever we connect to an MX server, we first try and upgrade the connection to a TLS connection to deliver your messages.
Our goal is to make things easier for developers, so we work on features that will enable our users to do things quickly and more effectively.
This was originally announced on March 23, 2015. We’ve made several performance and stability enhancements to our API recently. Because of the significance of the changes and also to keep our API consistent, we’re changing the default base URL to /v3.
Mailgun has completed patching all of our infrastructure against the recently announced GHOST security vulnerability.
One of the features we get complimented on a lot is our logs. Using our logs as a developer, you are able to understand what is happening to the messages you send and easily troubleshoot technical issues.
This was reported on October 2, 2014. We want to provide you a full report on the connectivity issues that have afflicted some of our Mailgun customers these past few days.
This was posted on August 28, 2014. Until recently, Mailgun has been in a managed colo environment hosted by our parent company, Rackspace, using bare metal servers.
