How DNSimple Handles Incidents
Last updated
Table of Contents
- What happens during an incident?
- Does DNSimple publish postmortems?
- How can I protect my domains during an outage?
- Have more questions?
DNSimple posts service incidents on its public status page at dnsimplestatus.com, updates them until the issue is resolved, and publishes a postmortem on the DNSimple blog for significant incidents. To receive these updates automatically, subscribe to notifications by email, SMS, Slack, webhook, or feed.
What happens during an incident?
When DNSimple detects or is notified of a service disruption:
- An incident is created on the status page with the affected components identified.
- Updates are posted as the investigation progresses, including what is known and what is being done.
- When the issue is resolved, the incident is marked resolved with a summary of what happened.
The status page is hosted separately from DNSimple, so you can still follow updates if the DNSimple dashboard is unavailable. For what the page covers and what each component status means, see DNSimple Status Page.
Does DNSimple publish postmortems?
For significant incidents, DNSimple publishes a postmortem on the DNSimple blog. Postmortems typically include:
- A timeline of the incident.
- The root cause and contributing factors.
- What was done to resolve the issue.
- Steps being taken to prevent recurrence.
Postmortems are published after the engineering team completes its investigation. The timeline varies depending on the complexity of the incident.
How can I protect my domains during an outage?
To reduce the impact of any DNS provider outage, consider adding a secondary DNS provider as a resilience layer. Secondary DNS keeps your domains resolving even if one provider is temporarily unavailable.
Have more questions?
If you have any questions about how DNSimple handles incidents or want to report an issue, contact support, and we’ll be happy to help. You can also read more about reliability at DNSimple.