tag:www.zamzarstatus.com,2005:/historyZamzar Status - Incident History2024-03-28T12:50:58ZZamzartag:www.zamzarstatus.com,2005:Incident/198070272024-01-23T17:16:32Z2024-01-23T17:16:32ZInvestigating issue with web traffic to www.zamzar.com<p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>17:16</var> UTC</small><br><strong>Resolved</strong> - We are happy that this incident is now resolved. Sorry for any inconvenience caused.</p><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>15:23</var> UTC</small><br><strong>Update</strong> - Website is now operational.</p><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>15:23</var> UTC</small><br><strong>Monitoring</strong> - We have now identified the issue and all services should be back. We are going to continue to monitor for the next couple of hours.</p><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>15:17</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating an issue affecting web traffic to www.zamzar.com. This may mean that you are unable to perform conversions at this time. Once we have an update to this we will post here.</p>tag:www.zamzarstatus.com,2005:Incident/159951452023-02-04T07:00:29Z2023-02-04T07:00:29ZAPI System Maintenance<p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>07:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>06:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>11:47</var> UTC</small><br><strong>Scheduled</strong> - This is a planned maintenance window for essential system upgrades to the Zamzar developer API.<br /><br />During the maintenance window the developer API may be unavailable for up to 5 minutes.<br /><br />At that time new file conversion jobs may be delayed, users may not be able to login to their user account at https://developers.zamzar.com and HTTP GET and POST requests to the API endpoints at https://api.zamzar.com or https://sandbox.zamzar.com may return an HTTP 503 (Service Unavailable) response code with the following error message in the body of the HTTP response:<br /><br />{"errors":[{"code":30,"message":"service temporarily unavailable","context":{"details":"We're working on it ! See https://twitter.com/zamzar for updates."}}]}</p>tag:www.zamzarstatus.com,2005:Incident/105299872022-07-18T01:00:35Z2022-07-18T01:00:35ZAPI System Maintenance<p><small>Jul <var data-var='date'>18</var>, <var data-var='time'>01:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jul <var data-var='date'>17</var>, <var data-var='time'>21:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jul <var data-var='date'>10</var>, <var data-var='time'>23:00</var> UTC</small><br><strong>Scheduled</strong> - This is a planned maintenance window for system upgrades to the Zamzar developer API.<br /><br />During the window the developer API may be unavailable for up to 20 minutes.<br /><br />At that time users may not be able to login to their user account at https://developers.zamzar.com and HTTP GET and POST requests to the API endpoints at https://api.zamzar.com or https://sandbox.zamzar.com may return an HTTP 503 (Service Unavailable) response code with the following error message in the body of the HTTP response:<br /><br />{"errors":[{"code":30,"message":"service temporarily unavailable","context":{"details":"We're working on it ! See https://twitter.com/zamzar for updates."}}]}</p>tag:www.zamzarstatus.com,2005:Incident/95015422022-03-09T22:24:58Z2022-03-09T22:24:58ZInterruption to API service<p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>22:24</var> UTC</small><br><strong>Resolved</strong> - This incident has now been resolved.</p><p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>20:57</var> UTC</small><br><strong>Investigating</strong> - We have observed an interruption to a number of requests to our API conversion service. Our team are currently investigating the underlying cause and will update further here once we know more.</p>tag:www.zamzarstatus.com,2005:Incident/91216022022-01-23T23:00:29Z2022-01-23T23:00:29ZAPI System Maintenance<p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>23:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>22:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>19</var>, <var data-var='time'>15:49</var> UTC</small><br><strong>Scheduled</strong> - This is a planned maintenance window for system upgrades to the Zamzar developer API.<br /><br />During the window the developer API may be unavailable for up to 10 minutes.<br /><br />At that time users may not be able to login to their user account at https://developers.zamzar.com and HTTP GET and POST requests to the API endpoints at https://api.zamzar.com or https://sandbox.zamzar.com may return an HTTP 503 (Service Unavailable) response code with the following error message in the body of the HTTP response:<br /><br />{"errors":[{"code":30,"message":"service temporarily unavailable","context":{"details":"We're working on it ! See https://twitter.com/zamzar for updates."}}]}</p>tag:www.zamzarstatus.com,2005:Incident/85461452021-11-21T23:00:32Z2021-11-21T23:00:32ZAPI System Maintenance<p><small>Nov <var data-var='date'>21</var>, <var data-var='time'>23:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Nov <var data-var='date'>21</var>, <var data-var='time'>22:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Nov <var data-var='date'>15</var>, <var data-var='time'>23:46</var> UTC</small><br><strong>Scheduled</strong> - This is a planned maintenance window for system upgrades to the Zamzar developer API.<br /><br />During the window the developer API may be unavailable for up to 10 minutes.<br /><br />At that time users may not be able to login to their user account at https://developers.zamzar.com and HTTP GET and POST requests to the API endpoints at https://api.zamzar.com or https://sandbox.zamzar.com may return an HTTP 503 (Service Unavailable) response code with the following error message in the body of the HTTP response:<br /><br />{"errors":[{"code":30,"message":"service temporarily unavailable","context":{"details":"We're working on it ! See https://twitter.com/zamzar for updates."}}]}</p>tag:www.zamzarstatus.com,2005:Incident/75536012021-07-20T09:26:04Z2021-07-20T09:26:04ZInterruption to API service<p><small>Jul <var data-var='date'>20</var>, <var data-var='time'>09:26</var> UTC</small><br><strong>Resolved</strong> - We can confirm this issue has now been resolved and new API requests submitted since 07:05 AM UTC today are processing normally. We will continue to perform enhanced monitoring of the service throughout the day.</p><p><small>Jul <var data-var='date'>20</var>, <var data-var='time'>08:11</var> UTC</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Jul <var data-var='date'>20</var>, <var data-var='time'>07:37</var> UTC</small><br><strong>Monitoring</strong> - Our team has identified that some requests to the API failed to be serviced between 05:45 AM UTC - 07:05 AM UTC today, instead returning an HTTP "500" error. The underlying problem causing those requests not to be processed has now been remediated and any ongoing requests submitted to the API will now function as expected. Any requests submitted during that timeframe which failed (including file conversion requests) will need to be re-submitted for processing.<br /><br />We will continue to closely monitor the service for any issues but are not anticipating any further problems.</p><p><small>Jul <var data-var='date'>20</var>, <var data-var='time'>06:29</var> UTC</small><br><strong>Investigating</strong> - We have observed an interruption to a number of requests to our API conversion service. Our team are currently investigating the underlying cause and will update further here once we know more.</p>tag:www.zamzarstatus.com,2005:Incident/74692672021-07-18T23:30:33Z2021-07-18T23:30:34ZSwitching off TLS 1.1<p><small>Jul <var data-var='date'>18</var>, <var data-var='time'>23:30</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jul <var data-var='date'>18</var>, <var data-var='time'>23:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jul <var data-var='date'>11</var>, <var data-var='time'>00:20</var> UTC</small><br><strong>Scheduled</strong> - In line with modern security best practices Zamzar will be switching off support for TLS v1.1, a cryptographic protocol used to secure communications between your web browser (or API client) and our systems.<br /><br />This change will not involve any downtime for Zamzar services, and customers will not observe an impact on their applications or usage of Zamzar's services, provided they are not using TLS v1.1 to connect.<br /><br />For more information please read our announcement at https://blog.zamzar.com/2021/07/11/even-better-security-dropping-support-for-tls-1-1/</p>tag:www.zamzarstatus.com,2005:Incident/66040002021-03-27T07:00:30Z2021-03-27T07:00:30ZAPI System Maintenance<p><small>Mar <var data-var='date'>27</var>, <var data-var='time'>07:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>27</var>, <var data-var='time'>06:30</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'>24</var>, <var data-var='time'>23:13</var> UTC</small><br><strong>Scheduled</strong> - This is a planned maintenance window for system upgrades to the Zamzar developer API.<br /><br />During the window the developer API may be unavailable for up to 5 minutes. We expect actual downtime to be much lower - in the region of 1-2 minutes.<br /><br />At that time users may not be able to login to their user account at https://developers.zamzar.com and HTTP GET and POST requests to the API endpoints at https://api.zamzar.com or https://sandbox.zamzar.com may return an HTTP 503 (Service Unavailable) response code with the following error message in the body of the HTTP response:<br /><br />{"errors":[{"code":30,"message":"service temporarily unavailable","context":{"details":"We're working on it ! See https://twitter.com/zamzar for updates."}}]}</p>tag:www.zamzarstatus.com,2005:Incident/43245442020-06-10T07:38:50Z2020-06-10T07:38:50ZNetwork connectivity issue on the Zamzar website<p><small>Jun <var data-var='date'>10</var>, <var data-var='time'>07:38</var> UTC</small><br><strong>Resolved</strong> - This network connectivity issue that affected the website at https://www.zamzar.com is now resolved. Apologies for the issues.</p><p><small>Jun <var data-var='date'>10</var>, <var data-var='time'>00:20</var> UTC</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Jun <var data-var='date'>10</var>, <var data-var='time'>00:15</var> UTC</small><br><strong>Monitoring</strong> - Network connectivity appears to have been restored by our datacenter provider, and the Zamzar website is available again. Our engineers will continue to monitor closely over the coming hours. Apologies for any inconvenience caused, whilst IBM worked to fix this issue.</p><p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>22:21</var> UTC</small><br><strong>Investigating</strong> - The Zamzar website (https://www.zamzar.com) is currently experiencing some network connectivity issues. Our engineers are actively working with our datacenter provider. Apologies for any inconvenience caused.</p>tag:www.zamzarstatus.com,2005:Incident/31649562019-11-14T11:00:31Z2019-11-14T11:00:31ZAPI System Maintenance<p><small>Nov <var data-var='date'>14</var>, <var data-var='time'>11:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Nov <var data-var='date'>14</var>, <var data-var='time'>10:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Oct <var data-var='date'>31</var>, <var data-var='time'>13:02</var> UTC</small><br><strong>Scheduled</strong> - This is a planned maintenance window for system upgrades to the Zamzar developer API.<br /><br />During the window the developer API may be unavailable for up to 5 minutes. We expect actual downtime to be much lower - in the region of 1-2 minutes.<br /><br />At that time users will not be able to login to their user account at https://developers.zamzar.com and any requests to the API endpoints at https://api.zamzar.com or https://sandbox.zamzar.com will return an HTTP 503 (Service Unavailable) response code with the following error message in the body of the HTTP response:<br /><br />{"errors":[{"code":30,"message":"service temporarily unavailable","context":{"details":"We're working on it ! See https://twitter.com/zamzar for updates."}}]}</p>tag:www.zamzarstatus.com,2005:Incident/26360262019-07-01T16:01:53Z2019-07-01T16:02:35ZBrief interruption to API service<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>16:01</var> UTC</small><br><strong>Resolved</strong> - We have been monitoring this over the past few hours and have not seen further issues, as such this is now resolved.</p><p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>12:57</var> UTC</small><br><strong>Monitoring</strong> - We have observed an interruption to a small number of requests to the API conversion service. A small number of clients may have received an HTTP 500 error when submitting requests to the API. This issue has now been resolved and our team are closely monitoring to ensure that no further issues arise.</p>tag:www.zamzarstatus.com,2005:Incident/26166282019-06-27T20:40:54Z2019-06-27T20:40:54ZFile Conversion Exports Delayed<p><small>Jun <var data-var='date'>27</var>, <var data-var='time'>20:40</var> UTC</small><br><strong>Resolved</strong> - This is now resolved.</p><p><small>Jun <var data-var='date'>27</var>, <var data-var='time'>14:48</var> UTC</small><br><strong>Monitoring</strong> - We are no longer seeing file conversion export delays. We will continue to monitor.</p><p><small>Jun <var data-var='date'>27</var>, <var data-var='time'>14:07</var> UTC</small><br><strong>Investigating</strong> - We are observing some file conversion exports being delayed for some customers.<br /><br />Our engineer team are currently investigating as soon as we have an update we will post here.</p>tag:www.zamzarstatus.com,2005:Incident/25833312019-06-21T14:04:43Z2019-06-21T14:04:51ZElevated queue times for API conversion jobs<p><small>Jun <var data-var='date'>21</var>, <var data-var='time'>14:04</var> UTC</small><br><strong>Resolved</strong> - Following continued monitoring of these elevated queue times - this is now resolved.</p><p><small>Jun <var data-var='date'>21</var>, <var data-var='time'>11:07</var> UTC</small><br><strong>Monitoring</strong> - We are no longer seeing elevated queue times for API conversion jobs. We will continue to monitor.</p><p><small>Jun <var data-var='date'>21</var>, <var data-var='time'>10:25</var> UTC</small><br><strong>Investigating</strong> - We are observing elevated queue times for API conversion jobs for some customers.<br /><br />Our engineer team are currently investigating as soon as we have an update we will post here.</p>tag:www.zamzarstatus.com,2005:Incident/23672762019-05-03T20:07:07Z2019-05-03T20:07:07ZElevated queue times for API conversion jobs<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>20:07</var> UTC</small><br><strong>Resolved</strong> - Following monitoring of these elevated queue times - this is now resolved.</p><p><small>May <var data-var='date'> 3</var>, <var data-var='time'>14:02</var> UTC</small><br><strong>Monitoring</strong> - We are no longer seeing elevated queue times for API conversion jobs. We will continue to monitor.</p><p><small>May <var data-var='date'> 3</var>, <var data-var='time'>13:20</var> UTC</small><br><strong>Investigating</strong> - We are observing elevated queue times for API conversion jobs for some customers.<br /><br />Our ops team have deployed more API resources to mitigate these issues. We will continue to monitor and update here with any status updates.</p>tag:www.zamzarstatus.com,2005:Incident/22998082019-04-01T10:38:18Z2019-04-01T10:38:18ZElevated queue times for API conversion job<p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>10:38</var> UTC</small><br><strong>Resolved</strong> - Our ops team have been monitoring the services closely for the last 2 hours and have not observed any elevated queue times for jobs submitted during this period. We are therefore closing this incident and will continue to monitor.</p><p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>07:50</var> UTC</small><br><strong>Monitoring</strong> - We are now seeing normal response times across all API jobs.<br /><br />We will continue to monitor the situation but do not expect to see increased queue times for future jobs.</p><p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>07:00</var> UTC</small><br><strong>Investigating</strong> - We are observing elevated queue times for API conversion jobs for some customers.<br /><br />Our ops team have deployed more API resources to mitigate these issues.<br /><br />We will continue to monitor the situation and update this ticket.</p>tag:www.zamzarstatus.com,2005:Incident/22159652019-02-20T11:36:59Z2019-02-20T11:36:59ZElevated queue times for API conversion jobs<p><small>Feb <var data-var='date'>20</var>, <var data-var='time'>11:36</var> UTC</small><br><strong>Resolved</strong> - Our ops team have been monitoring the services closely for the last 2 hours and have not observed any elevated queue times for jobs submitted during this period. We are therefore closing this incident and will continue to monitor.</p><p><small>Feb <var data-var='date'>20</var>, <var data-var='time'>09:17</var> UTC</small><br><strong>Monitoring</strong> - We are observing elevated queue times for API conversion jobs for some customers.<br /><br />Our ops team have deployed more API resources to mitigate these issues and are now seeing normal response times across all API jobs.<br /><br />We will continue to monitor the situation but do not expect to see increased queue times for future jobs.</p>tag:www.zamzarstatus.com,2005:Incident/20719562018-11-30T08:12:50Z2018-11-30T08:12:50ZNetwork connectivity issue on the Zamzar website<p><small>Nov <var data-var='date'>30</var>, <var data-var='time'>08:12</var> UTC</small><br><strong>Resolved</strong> - This network connectivity issue is now resolved. Apologies for the issues.</p><p><small>Nov <var data-var='date'>29</var>, <var data-var='time'>21:14</var> UTC</small><br><strong>Monitoring</strong> - Our hosting provider has advised that the network connectivity issues are resolved. We will continue to monitor over the next few hours. Apologies for the issues.</p><p><small>Nov <var data-var='date'>29</var>, <var data-var='time'>20:24</var> UTC</small><br><strong>Update</strong> - Our hosting provider have advised us they are experiencing a network connectivity issue in one of their datacenter's. We are actively working with them to resolve this and will update here as soon as we have anything further.</p><p><small>Nov <var data-var='date'>29</var>, <var data-var='time'>20:13</var> UTC</small><br><strong>Investigating</strong> - The Zamzar website (https://www.zamzar.com) is currently experiencing some network connectivity issues. Our engineers are actively working with our datacenter provider. Apologies for any inconvenience caused.</p>tag:www.zamzarstatus.com,2005:Incident/16361662018-03-10T16:17:36Z2018-03-10T16:17:36ZDelayed Conversions on the Zamzar API<p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>16:17</var> UTC</small><br><strong>Resolved</strong> - All conversion delays have now been cleared. Our team will continue to monitor for any further delays, but none are expected.</p><p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>15:40</var> UTC</small><br><strong>Monitoring</strong> - New jobs submitted to the /jobs endpoint at api.zamzar.com and sandbox.zamzar.com are no longer experiencing conversion delays. Some older jobs are still being converted. We will continue to monitor the system to ensure all older jobs are converted ok.</p><p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>13:00</var> UTC</small><br><strong>Investigating</strong> - Our team are currently investigating a number of delayed conversions on the Zamzar API. As soon as our team have any updates we will post them here.</p>tag:www.zamzarstatus.com,2005:Incident/16361722018-03-10T15:36:46Z2018-03-10T15:37:16ZAPI endpoints unavailable for almost 3 minutes<p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>15:36</var> UTC</small><br><strong>Resolved</strong> - No further downtime has been experienced. There was an outage of just under 3 minutes between 12:53:23 YTC and 12:56:19 UTC, which resulted in HTTP 503 "Service Unavailable" responses being returned to some client requests to api.zamzar.com and sandbox.zamzar.com. The underlying cause of this issue was identified by our engineers and has now been fixed.</p><p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>13:02</var> UTC</small><br><strong>Investigating</strong> - We are investigating a short period of downtime on the the Zamzar Developer API at the api.zamzar.com and sandbox.zamzar.com endpoints.</p>tag:www.zamzarstatus.com,2005:Incident/16338272018-03-08T20:55:28Z2018-03-08T20:55:28ZSome requests to /jobs endpoint previously failed with HTTP 422 error<p><small>Mar <var data-var='date'> 8</var>, <var data-var='time'>20:55</var> UTC</small><br><strong>Resolved</strong> - Our operations team have observed that a small number of HTTP POST requests to submit files for conversion to the /v1/jobs API endpoint resulted in an "HTTP 422 Unprocessable" error between March 7th 2018, 14:59:00 UTC and March 8th 2018, 11:53:59 UTC. Additionally the following unexpected response message may have been received by some clients during that time:
<br />
<br />{"errors":[{"context":{"parameter":"source_file","reason":"binary data was not successfully received"},"code":11,"message":"an invalid value was specified for a parameter"}]}
<br />
<br />This problem which is now resolved was caused by an internal configuration issue within the Zamzar API. The root cause of that problem has been identified and a fix has been put in place to ensure this issue does not reoccur.
<br />
<br />Thanks for your patience whilst this issue was ongoing.</p>tag:www.zamzarstatus.com,2005:Incident/15247302017-12-04T14:34:18Z2017-12-04T14:34:18ZElevated Queue Times<p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>14:34</var> UTC</small><br><strong>Resolved</strong> - There are no longer any elevated queue times for conversions.</p><p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>11:04</var> UTC</small><br><strong>Monitoring</strong> - There are no longer any elevated queue times for conversions. Our team will continue to monitor performance closely.</p><p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>10:36</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating elevated queue times for file conversions - our team are investigating and will update once they have further information.</p>tag:www.zamzarstatus.com,2005:Incident/14542942017-11-01T14:54:03Z2017-11-01T14:54:03ZIntermittent HTTP 503 responses from https://api.zamzar.com/<p><small>Nov <var data-var='date'> 1</var>, <var data-var='time'>14:54</var> UTC</small><br><strong>Resolved</strong> - 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.
<br />
<br />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.
<br />
<br />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.</p>tag:www.zamzarstatus.com,2005:Incident/14505192017-10-30T17:05:27Z2017-10-30T17:05:27ZAPI Issue resulting in a Bad Request 400 Error<p><small>Oct <var data-var='date'>30</var>, <var data-var='time'>17:05</var> UTC</small><br><strong>Resolved</strong> - This issue is now resolved.</p><p><small>Oct <var data-var='date'>30</var>, <var data-var='time'>14:06</var> UTC</small><br><strong>Monitoring</strong> - Our engineering and support teams will now monitor the API over the coming few hours to ensure everything is working as expected.</p><p><small>Oct <var data-var='date'>30</var>, <var data-var='time'>14:04</var> UTC</small><br><strong>Identified</strong> - Our engineering team has identified the issue and have released a fix which will now be monitored.</p><p><small>Oct <var data-var='date'>30</var>, <var data-var='time'>13:58</var> UTC</small><br><strong>Investigating</strong> - We are currently experiencing an issue on the Zamzar API which results in a Bad Request 400 error.
<br />
<br />Our engineering team are working on identifying the issue and resolving this. As soon as we have an update we will post it here.</p>tag:www.zamzarstatus.com,2005:Incident/12992262017-07-22T07:00:14Z2019-10-31T12:54:32ZAPI System Maintenance<p><small>Jul <var data-var='date'>22</var>, <var data-var='time'>07:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jul <var data-var='date'>22</var>, <var data-var='time'>06:30</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jul <var data-var='date'>18</var>, <var data-var='time'>11:42</var> UTC</small><br><strong>Scheduled</strong> - This is a planned maintenance window for system upgrades on the Zamzar developer API.
<br />
<br />During the window the developer API may be unavailable for up to 5 minutes. We expect actual downtime to be much lower - in the region of 1-2 minutes.
<br />
<br />At that time users will not be able to login to their user account at https://developers.zamzar.com and any requests to the API endpoints at https://api.zamzar.com or https://sandbox.zamzar.com will return an HTTP 503 (Service Unavailable) response code with the following error message in the body of the HTTP response:
<br />
<br />{"errors":[{"code":30,"message":"service temporarily unavailable","context":{"details":"We're working on it ! See https://twitter.com/zamzar for updates."}}]}</p>