outages.live
Live
D

DNSimple

DNSimple is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

3

Days with an incident

4

Median duration

5 h 26 min

Longest incident

11 h 4 min

Components

13
Website Operational
90 days agoNo incidentsToday
Sandbox Website Operational
90 days ago2 days with an incidentToday
API Operational
90 days agoNo incidentsToday
Sandbox API Operational
90 days ago2 days with an incidentToday
Registrar Operational
90 days agoNo incidentsToday
Name Servers Operational
90 days ago2 days with an incidentToday
URL Redirector Operational
90 days agoNo incidentsToday
Zone deployment Operational
90 days agoNo incidentsToday
Secondary DNS Operational
90 days agoNo incidentsToday
SSL Certificates Operational
90 days agoNo incidentsToday
Webhooks Operational
90 days agoNo incidentsToday
Notifications Operational
90 days agoNo incidentsToday
Email Forwards Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 16, 2026

Duration11 h 4 min19:06 to 06:10Sandbox Environment – Intermittent Downtime During Hosting Provider MaintenanceNotice

This incident is resolved now, no system should be affected.

Sep 6, 2026

Duration2 h 45 min13:10 to 15:55Edge network disruption in Warsaw EU regionDegraded

The issue was resolved upstream, and the Warsaw region has been stable.

Aug 8, 2026

Duration5 h 26 min00:27 to 05:53Degraded service in London regionDegraded

This incident has been resolved.

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.

Prompt
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.

RSS
https://outages.cc/feed.xml?providers=dnsimple
Slack
/feed subscribe https://outages.cc/feed.xml?providers=dnsimple

Go from tracking outages to fixing production issues with Polylane.

Try Polylane