Degraded service in London region
This incident has been resolved.
The latest update from DNSimple.
State
Resolved
Started
86 d ago
2026-08-08 00:27 UTC
Lasted
5 h 26 min
until 2026-08-08 05:53 UTC
Worst impact
Degraded
Timeline
5 updatesInvestigating
2 h 19 min 43%
Identified
2 h 27 min 45%
Monitoring
39 min 12%
Updates
Times in UTCAs posted by DNSimple
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are continuing to investigate this issue.
We are currently investigating this issue.
Affected components
1DNSimple in the last 90 days
Full historyIncidents in 90 days
3
Days with an incident
4
Median duration
5 h 26 min
This incident
About the median
Other DNSimple incidents
All incidentsDNSimple·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.
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.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