Our status page is moving on November 10
On Tuesday, November 10, 2026 at 20:00 UTC, we are moving our status page. The address (https://dnsimplestatus.com) will stay the same, but the underlying provider is changing. This move does not affect any DNSimple services. What you need to do depends on how you get notifications from us: - Email: On November 10, you will get a confirmation email from Datadog (no-reply@dtdg.co). Please click the link in that email to keep getting notifications. If you do not confirm, your notifications will stop. - Slack: After the move, please go to https://dnsimplestatus.com and subscribe again. - SMS: We will no longer send SMS notifications. After the move, please go to https://dnsimplestatus.com and subscribe by email, Slack, Microsoft Teams, or RSS. The old address, dnsimple.statuspage.io, will no longer be updated after the move and will close soon after. Please use https://dnsimplestatus.com going forward. If you have questions, please email support@dnsimple.com.
The latest update from DNSimple.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by DNSimple
On Tuesday, November 10, 2026 at 20:00 UTC, we are moving our status page. The address (https://dnsimplestatus.com) will stay the same, but the underlying provider is changing. This move does not affect any DNSimple services. What you need to do depends on how you get notifications from us: - Email: On November 10, you will get a confirmation email from Datadog (no-reply@dtdg.co). Please click the link in that email to keep getting notifications. If you do not confirm, your notifications will stop. - Slack: After the move, please go to https://dnsimplestatus.com and subscribe again. - SMS: We will no longer send SMS notifications. After the move, please go to https://dnsimplestatus.com and subscribe by email, Slack, Microsoft Teams, or RSS. The old address, dnsimple.statuspage.io, will no longer be updated after the move and will close soon after. Please use https://dnsimplestatus.com going forward. If you have questions, please email support@dnsimple.com.
Affected components
13DNSimple in the last 90 days
Full historyIncidents in 90 days
2
Days with an incident
3
Median duration
6 h 54 min
This incident
Not comparable
Other DNSimple incidents
All incidentsFollow DNSimple
Your coding agent knows when DNSimple is down, and tells you when a failure is theirs, not yours. You can also get DNSimple incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "dnsimple" and tell me if DNSimple has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=dnsimple/feed subscribe https://outages.cc/feed.xml?providers=dnsimpleFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane