WireDrive incident

Widespread internet issues causing Wiredrive service interruption.

Critical Resolved View vendor source →

WireDrive experienced a critical incident on October 21, 2016 affecting Site Availability and Video Playback and 1 more component, lasting 6h 5m. The incident has been resolved; the full update timeline is below.

Started
Oct 21, 2016, 04:36 PM UTC
Resolved
Oct 21, 2016, 10:42 PM UTC
Duration
6h 5m
Detected by Pingoru
Oct 21, 2016, 04:36 PM UTC

Affected components

Site AvailabilityVideo PlaybackPresentation AvailabilityEmail Delivery

Update timeline

  1. monitoring Oct 21, 2016, 04:36 PM UTC

    A major DNS service provider, Dyn, is experiencing a denial of service attack that is affecting our customers' ability to access Wiredrive. This is a widespread issue affecting wide swaths of websites including Twitter, Spotify, and Reddit to name a few. We are monitoring the situation and will provide further updates.

  2. monitoring Oct 21, 2016, 06:49 PM UTC

    Wiredrive is continuing to monitor the DDoS attack to a major DNS service provider, Dyn. This is a widespread issue affecting services nationwide including Twitter, Spotify, GitHub and Reddit to name a few. We are monitoring the situation and will provide further updates once received. Please subscribe above for email updates or for additional status updates from the DNS provider directly please subscribe to https://www.dynstatus.com/

  3. monitoring Oct 21, 2016, 09:56 PM UTC

    All Wiredrive services are currently operational. We will continue to monitor DYN's status as they have not provided an update to the status of the DDoS attacks they have encountered. Should you experience any delays please contact our support team so that we can confirm any additional DDoS attacks to the DYN service provider.

  4. resolved Oct 21, 2016, 10:42 PM UTC

    Wiredrive has confirmed with our DNS service provider DYN that the service interruption caused by a DDoS attack to DYN has been resolved. This attack had no effect on Wiredrive systems data or security integrity and only affected to resolve connections to our domains. For additional information on the cause and solution from DYN please go to https://www.dynstatus.com/incidents/5r9mppc1kb77 for further details. Please feel free to reach out to our support team if you have any other questions.