Zamzar 장애 기록

1. 2026년 7월 13일 오후 7:53 UTCinvestigating

   우리는 현재 intermittent outages를 가진 문제점을 조사하고 있습니다. 우리는 모든 업데이트로 여기에 업데이트됩니다.

2. 2026년 7월 13일 오후 9:18 UTCinvestigating

   우리는 intermittent 네트워크 문제점을 조사하는 것을 계속합니다. 우리는 우리의 호스팅 공급자와 접촉하고 우리가 그(것)들을 얻는 것과 같이 더 새롭게 제공할 것입니다.

3. 2026년 7월 13일 오후 10:04 UTCmonitoring

   수정이 확인되었습니다. 우리는 이제 모니터링하고 있습니다.

4. 2026년 7월 13일 오후 10:14 UTCresolved

   우리는 우리의 호스팅 회사에서 확인이 문제가 지금 해결되고 우리는 문제의 재발을 본 적이 없습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 3일 오후 8:15 UTCinvestigating

   우리는 일부 고객에게 API 변환 작업에 대한 높은 큐 시간을 관찰하고 있습니다. 우리의 엔지니어 팀은 현재 우리가 여기에서 포스트할 갱신이 있기 때문에 투자됩니다.

2. 2026년 7월 3일 오후 8:16 UTCidentified

   문제는 확인되고 우리는 해결하기 위해 노력하고 있습니다.

3. 2026년 7월 3일 오후 8:28 UTCmonitoring

   현재 대기 중입니다. 일단 사건이 해결되면 다시 업데이트됩니다.

4. 2026년 7월 3일 오후 8:53 UTCresolved

   이 사건은 이제 해결되었습니다 - 대기 시간은 정상으로 돌아갑니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2025년 10월 21일 오후 3:24 UTCresolved

   The Zamzar API was not able to process new conversions for approximately 90 minutes due to an issue with our service provider (Amazon Web Services), as widely reported in the press. During this time the API returned an HTTP 503 "Service Unavailable" error and was not able to accept new conversion jobs or allow logins to the API user dashboard. The issue was resolved 90 minutes after it started, with new conversions then possible. For more information on the AWS outage please see https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_BA540_514A652BE1A

1. 2025년 10월 8일 오전 6:54 UTCinvestigating

   Our engineers are investigating an issue with our Developer API where there are delays when completing some API jobs. All jobs are being accepted ok, but some jobs are taking longer than usual to complete.

2. 2025년 10월 8일 오전 7:20 UTCidentified

   Our team has identified the cause of this issue and have implemented a fix which should now result in minimal to no delays for any new jobs submitted to the API for conversion.

3. 2025년 10월 8일 오전 7:36 UTCmonitoring

   Our team has implemented a fix for the conversion delays and API service has now returned to normal. We will continue to monitor for any further issues, but any new jobs submitted for conversion are not experiencing any delays.

4. 2025년 10월 8일 오전 8:28 UTCresolved

   No further issues have been detected, and the API is operating as normal - this incident has been resolved.

1. 2025년 2월 2일 오전 8:31 UTCinvestigating

   Our team are currently investigating an issue where we aren't processing conversions.

2. 2025년 2월 2일 오전 9:07 UTCinvestigating

   As a further update our team are still investigating the underlying issue.

3. 2025년 2월 2일 오전 10:16 UTCmonitoring

   We have identified the issue and have rolled a fix for this.

4. 2025년 2월 2일 오후 4:50 UTCresolved

   This incident has been resolved - all conversions should now be possible again, thanks for your patience whilst we worked to resolve this.

1. 2025년 1월 23일 오전 10:56 UTCinvestigating

   We are seeing some performance issues with www.zamzar.com and our team are currently investigating. We will update here once we have further updates.

2. 2025년 1월 23일 오전 11:11 UTCidentified

   We have identified the issue and a fix has been prepared. Further updates will be posted here.

3. 2025년 1월 23일 오전 11:37 UTCmonitoring

   A fix has been implemented and we are now monitoring.

4. 2025년 1월 23일 오후 1:12 UTCresolved

   This incident has now been resolved.

1. 2024년 1월 23일 오후 3:17 UTCinvestigating

   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.

2. 2024년 1월 23일 오후 3:23 UTCmonitoring

   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.

3. 2024년 1월 23일 오후 3:23 UTCmonitoring

   Website is now operational.

4. 2024년 1월 23일 오후 5:16 UTCresolved

   We are happy that this incident is now resolved. Sorry for any inconvenience caused.

1. 2022년 3월 9일 오후 8:57 UTCinvestigating

   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.

2. 2022년 3월 9일 오후 10:24 UTCresolved

   This incident has now been resolved.

1. 2021년 7월 20일 오전 6:29 UTCinvestigating

   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.

2. 2021년 7월 20일 오전 7:37 UTCmonitoring

   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. We will continue to closely monitor the service for any issues but are not anticipating any further problems.

3. 2021년 7월 20일 오전 8:11 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2021년 7월 20일 오전 9:26 UTCresolved

   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.

1. 2020년 6월 9일 오후 10:21 UTCinvestigating

   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.

2. 2020년 6월 10일 오전 12:15 UTCmonitoring

   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.

3. 2020년 6월 10일 오전 12:20 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2020년 6월 10일 오전 7:38 UTCresolved

   This network connectivity issue that affected the website at https://www.zamzar.com is now resolved. Apologies for the issues.

1. 2019년 7월 1일 오후 12:57 UTCmonitoring

   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.

2. 2019년 7월 1일 오후 4:01 UTCresolved

   We have been monitoring this over the past few hours and have not seen further issues, as such this is now resolved.

1. 2019년 6월 27일 오후 2:07 UTCinvestigating

   We are observing some file conversion exports being delayed for some customers. Our engineer team are currently investigating as soon as we have an update we will post here.

2. 2019년 6월 27일 오후 2:48 UTCmonitoring

   We are no longer seeing file conversion export delays. We will continue to monitor.

3. 2019년 6월 27일 오후 8:40 UTCresolved

   This is now resolved.

1. 2019년 6월 21일 오전 10:25 UTCinvestigating

   We are observing elevated queue times for API conversion jobs for some customers. Our engineer team are currently investigating as soon as we have an update we will post here.

2. 2019년 6월 21일 오전 11:07 UTCmonitoring

   We are no longer seeing elevated queue times for API conversion jobs. We will continue to monitor.

3. 2019년 6월 21일 오후 2:04 UTCresolved

   Following continued monitoring of these elevated queue times - this is now resolved.

1. 2019년 5월 3일 오후 1:20 UTCinvestigating

   We are observing elevated queue times for API conversion jobs for some customers. Our ops team have deployed more API resources to mitigate these issues. We will continue to monitor and update here with any status updates.

2. 2019년 5월 3일 오후 2:02 UTCmonitoring

   We are no longer seeing elevated queue times for API conversion jobs. We will continue to monitor.

3. 2019년 5월 3일 오후 8:07 UTCresolved

   Following monitoring of these elevated queue times - this is now resolved.

1. 2019년 4월 1일 오전 7:00 UTCinvestigating

   We are observing elevated queue times for API conversion jobs for some customers. Our ops team have deployed more API resources to mitigate these issues. We will continue to monitor the situation and update this ticket.

2. 2019년 4월 1일 오전 7:50 UTCmonitoring

   We are now seeing normal response times across all API jobs. We will continue to monitor the situation but do not expect to see increased queue times for future jobs.

3. 2019년 4월 1일 오전 10:38 UTCresolved

   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.

1. 2019년 2월 20일 오전 9:17 UTCmonitoring

   We are observing elevated queue times for API conversion jobs for some customers. Our ops team have deployed more API resources to mitigate these issues and are now seeing normal response times across all API jobs. We will continue to monitor the situation but do not expect to see increased queue times for future jobs.

2. 2019년 2월 20일 오전 11:36 UTCresolved

   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.

1. 2018년 11월 29일 오후 8:13 UTCinvestigating

   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.

2. 2018년 11월 29일 오후 8:24 UTCinvestigating

   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.

3. 2018년 11월 29일 오후 9:14 UTCmonitoring

   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.

4. 2018년 11월 30일 오전 8:12 UTCresolved

   This network connectivity issue is now resolved. Apologies for the issues.

1. 2018년 3월 10일 오후 1:02 UTCinvestigating

   We are investigating a short period of downtime on the the Zamzar Developer API at the api.zamzar.com and sandbox.zamzar.com endpoints.

2. 2018년 3월 10일 오후 3:36 UTCresolved

   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.

1. 2018년 3월 10일 오후 1:00 UTCinvestigating

   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.

2. 2018년 3월 10일 오후 3:40 UTCmonitoring

   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.

3. 2018년 3월 10일 오후 4:17 UTCresolved

   All conversion delays have now been cleared. Our team will continue to monitor for any further delays, but none are expected.

1. 2018년 3월 8일 오후 8:55 UTCresolved

   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: {"errors":[{"context":{"parameter":"source_file","reason":"binary data was not successfully received"},"code":11,"message":"an invalid value was specified for a parameter"}]} 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. Thanks for your patience whilst this issue was ongoing.