Codetree incident

Issues with DNS resolution

Major Resolved View vendor source →

Codetree experienced a major incident on October 21, 2016, lasting 4h 33m. The incident has been resolved; the full update timeline is below.

Started
Oct 21, 2016, 05:55 PM UTC
Resolved
Oct 21, 2016, 10:28 PM UTC
Duration
4h 33m
Detected by Pingoru
Oct 21, 2016, 05:55 PM UTC

Update timeline

  1. identified Oct 21, 2016, 05:55 PM UTC

    We have confirmed an outage with our DNS provider, DynDNS. The issue is intermittently affecting DNS resolution for codetree.com. The issue is being worked on by both DynDNS and Heroku. You can track status here https://status.heroku.com/incidents/965 and here https://www.dynstatus.com/incidents/nlr4yrr162t8.

  2. monitoring Oct 21, 2016, 09:28 PM UTC

    The DNS resolution mitigations Heroku has made seem to have corrected the issue. We'll continue monitoring.

  3. resolved Oct 21, 2016, 10:28 PM UTC

    Based on the latest update from from DynDNS this issue has been resolved.