Zamzar incident

API Issue resulting in a Bad Request 400 Error

Notice Resolved View vendor source →

Zamzar experienced a notice incident on October 30, 2017, lasting 3h 7m. The incident has been resolved; the full update timeline is below.

Started
Oct 30, 2017, 01:58 PM UTC
Resolved
Oct 30, 2017, 05:05 PM UTC
Duration
3h 7m
Detected by Pingoru
Oct 30, 2017, 01:58 PM UTC

Update timeline

  1. investigating Oct 30, 2017, 01:58 PM UTC

    We are currently experiencing an issue on the Zamzar API which results in a Bad Request 400 error. Our engineering team are working on identifying the issue and resolving this. As soon as we have an update we will post it here.

  2. identified Oct 30, 2017, 02:04 PM UTC

    Our engineering team has identified the issue and have released a fix which will now be monitored.

  3. monitoring Oct 30, 2017, 02:06 PM UTC

    Our engineering and support teams will now monitor the API over the coming few hours to ensure everything is working as expected.

  4. resolved Oct 30, 2017, 05:05 PM UTC

    This issue is now resolved.