Zamzar incident

Intermittent HTTP 503 responses from https://api.zamzar.com/

Notice Resolved View vendor source →

Zamzar experienced a notice incident on November 1, 2017, lasting —. The incident has been resolved; the full update timeline is below.

Started
Nov 01, 2017, 02:54 PM UTC
Resolved
Nov 01, 2017, 02:54 PM UTC
Duration
—
Detected by Pingoru
Nov 01, 2017, 02:54 PM UTC

Update timeline

  1. resolved Nov 01, 2017, 02:54 PM UTC

    Our engineers observed an increase in HTTP 503 errors for requests to https://api.zamzar.com/ and https://sandbox.zamzar.com/ between 08.16-09:09 UTC today. These errors were intermittent in nature, so only affected a small number of requests to these endpoints. The root cause of this problem was determined to be an upstream DNS resolution issue with our hosting provider which has now been resolved. Requests to these endpoints were back to normal by 09:09 UTC. We are now taking steps to ensure our infrastructure is more tolerant of any future DNS resolution issues as part of our commitment to providing a highly available file conversion API for our customers.