Sandbox Environment – Intermittent Downtime During Hosting Provider Maintenance
This incident is resolved now, no system should be affected.
The latest update from DNSimple.
State
Resolved
Started
16 d ago
2026-10-16 19:06 UTC
Lasted
11 h 4 min
until 2026-10-17 06:10 UTC
Worst impact
Notice
Timeline
3 updatesInvestigating
16 min 2%
Monitoring
10 h 48 min 98%
Updates
Times in UTCAs posted by DNSimple
This incident is resolved now, no system should be affected.
The hosting provider’s maintenance is complete and the sandbox web application is available. We are monitoring for further issues. If you still see errors, please contact support.
Our hosting provider is performing emergency platform-wide maintenance that requires rolling restarts of its servers in all regions. As a result, the sandbox web application may be intermittently unavailable or slow to respond. Each restart is expected to cause roughly 15–20 minutes of downtime, and more than one interruption may occur while the rollout continues. Production environments are not affected. No action is needed on your part. If a request fails, please retry after a few minutes. Data in the sandbox is not expected to be lost. We are tracking the provider’s progress and will post an update when maintenance is complete and the sandbox is stable.
Affected components
2DNSimple in the last 90 days
Full historyIncidents in 90 days
3
Days with an incident
4
Median duration
5 h 26 min
This incident
2.0× the median
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