DNSimple

First posted only after it was over

0% 0 of the 49 incidents we have in full detailbetterworse

The first update already said resolved. Typical vendor: 6%.

DNSimple: lower than most vendors.

Time to resolve

1 h 42 min median; 9 in 10 within 5 h 26 minbetterworse

From the vendor’s own start and resolve times, last 365 days. Typical vendor: 2 h.

DNSimple: around the middle.

Major or critical incidents

0.3 a month 4 in the last 365 daysbetterworse

Impact as the vendor labels it. Typical vendor: 1.2 a month.

DNSimple: lower than most vendors.

Rewrites caught

None so far

Counts, not a rate: 10-minute tracking began Oct 17, so there are too few events to compare yet.

DNSimple depends on

Outage events: Microsoft Azure west us, Jul 23 (timing), Heroku, Aug 23, 2022 (timing), Cloudflare, Jul 17, 2020 (timing).

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.

Full DNSimple change history

Each change links to its diff: the changed passages with a few words of context, never a full copy of the page.

DNSimple incidents, last 90 daysJSONMarkdown