Resolved after 11 hours 5 minutes, on October 21, 2016.
This incident has been resolved. Dyn has now resolved the issue. That said, we will continue to monitor the situation in case of a reoccurrence. We have configured our application to use a second DNS service in addition to Dyn. This change is currently propagating from the root DNS servers, and will complete within 48 hours. Once this change is completely propagated, should either service fail, DNS will automatically use the available service.
Update timeline
- identified Oct 21, 2016, 04:32 PM UTC
We are tracking issues with our DNS provider. This outage is causing disruptions between services on the platform. We are investigating. Status can also be tracked with our provider here- https://www.dynstatus.com/incidents/nlr4yrr162t8
- resolved Oct 22, 2016, 03:38 AM UTC
This incident has been resolved. Dyn has now resolved the issue. That said, we will continue to monitor the situation in case of a reoccurrence. We have configured our application to use a second DNS service in addition to Dyn. This change is currently propagating from the root DNS servers, and will complete within 48 hours. Once this change is completely propagated, should either service fail, DNS will automatically use the available service.
Your product runs on more than ReviewTrackers
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services