The first post in my developer diary, in which I'm going to tell you about changes we're making to our infrastructure. Today, we're looking at DNS.
After the recent AWS outages took us (and most other status page providers) down, we're upping our commitment to building a service which is as resilient as possible.
Starting at the top of our stack and working our way down we're looking at any areas where we could do better. Each Monday I'll be writing a little about our thoughts and activities.
Today that means I've been looking into DNS, the technology which tells the internet where your status pages are located. If this component fails, nobody knows where "status.yourdomain.com" is to be found.
Our current setup
We currently use Dyn.com to host our DNS, they have an exceedingly strong reputation, providing the backbone for companies like Twitter and Netflix. However, nobody is immune from the occasional hiccup.
What we're changing
We're going to add a second DNS provider (and possibly a third down the line), likely in the form of DNSimple or AWS Route 53 to split the risk. Ensuring that even if one of these services goes down, traffic is still routed to us, keeping your status pages online.
I'll be sure to keep you posted. If you have any questions, let me know.