Scheduled Maintenance: DNS Infrastructure Upgrades in the US (IAD / ORD / SV1)
We will be performing scheduled maintenance on our DNS infrastructure in the Ashburn (IAD), Chicago (ORD) and San Jose (SV1) regions, as part of our ongoing infrastructure modernization. Only regional records in the IAD, ORD and SV1 regions are affected. We will work on one region at a time, and each region may be affected for up to 1 hour during the window. All other DNS traffic will fall back to nearby regions while this work is underway and will not be affected. You don't need to do anything. We will post updates here when the maintenance begins and when it is complete. If you have questions, please contact 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
We will be performing scheduled maintenance on our DNS infrastructure in the Ashburn (IAD), Chicago (ORD) and San Jose (SV1) regions, as part of our ongoing infrastructure modernization. Only regional records in the IAD, ORD and SV1 regions are affected. We will work on one region at a time, and each region may be affected for up to 1 hour during the window. All other DNS traffic will fall back to nearby regions while this work is underway and will not be affected. You don't need to do anything. We will post updates here when the maintenance begins and when it is complete. If you have questions, please contact support@dnsimple.com.
Affected components
1DNSimple in the last 90 days
Full historyIncidents in 90 days
4
Days with an incident
3
Median duration
6 h 54 min
This incident
Not comparable
Other DNSimple incidents
All incidents
DNSimple·Sandbox Environment – Intermittent Downtime During Hosting Provider Maintenance
This incident is resolved now, no system should be affected.

DNSimple·Sandbox Environment – Intermittent Downtime During Hosting Provider Maintenance
This incident is resolved now, no system should be affected.

DNSimple·Edge network disruption in Warsaw EU region
The issue was resolved upstream, and the Warsaw region has been stable.

DNSimple·Edge network disruption in Warsaw EU region
The issue was resolved upstream, and the Warsaw region has been stable.
Follow 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.live/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.live/feed.xml?providers=dnsimple/feed subscribe https://outages.live/feed.xml?providers=dnsimpleFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane