Störungsverlauf von Zamzar

1. 13. Juli 2026 um 19:53 UTCinvestigating

   Wir untersuchen derzeit ein Problem mit intermittierenden Ausfällen. Wir werden hier mit allen Updates aktualisieren.

2. 13. Juli 2026 um 21:18 UTCinvestigating

   Wir untersuchen weiterhin ein intermittierendes Netzwerkproblem. Wir sind in Kontakt mit unserem Hosting-Provider und werden weitere Updates zur Verfügung stellen, sobald wir sie erhalten.

3. 13. Juli 2026 um 22:04 UTCmonitoring

   Der Fix wurde identifiziert und wir überwachen jetzt.

4. 13. Juli 2026 um 22:14 UTCresolved

   Wir haben eine Bestätigung von unserem Hosting-Unternehmen erhalten, dass das Problem jetzt behoben ist und wir keine Wiederholung des Problems gesehen haben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 3. Juli 2026 um 20:15 UTCinvestigating

   Wir beobachten erhöhte Warteschlangenzeiten für API-Konvertierungsjobs für einige Kunden. Unser Ingenieurteam untersucht derzeit, sobald wir ein Update haben, das wir hier veröffentlichen werden.

2. 3. Juli 2026 um 20:16 UTCidentified

   Das Problem wurde identifiziert und wir arbeiten daran, es zu lösen.

3. 3. Juli 2026 um 20:28 UTCmonitoring

   Die Warteschlangenzeiten kommen jetzt herunter, wir werden hier erneut aktualisieren, sobald der Vorfall behoben ist.

4. 3. Juli 2026 um 20:53 UTCresolved

   Dieser Vorfall ist nun behoben - die Warteschlangenzeiten sind wieder normal.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 21. Oktober 2025 um 15: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. 8. Oktober 2025 um 06: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. 8. Oktober 2025 um 07: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. 8. Oktober 2025 um 07: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. 8. Oktober 2025 um 08:28 UTCresolved

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

1. 2. Februar 2025 um 08:31 UTCinvestigating

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

2. 2. Februar 2025 um 09:07 UTCinvestigating

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

3. 2. Februar 2025 um 10:16 UTCmonitoring

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

4. 2. Februar 2025 um 16: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. 23. Januar 2025 um 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. 23. Januar 2025 um 11:11 UTCidentified

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

3. 23. Januar 2025 um 11:37 UTCmonitoring

   A fix has been implemented and we are now monitoring.

4. 23. Januar 2025 um 13:12 UTCresolved

   This incident has now been resolved.

1. 23. Januar 2024 um 15: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. 23. Januar 2024 um 15: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. 23. Januar 2024 um 15:23 UTCmonitoring

   Website is now operational.

4. 23. Januar 2024 um 17:16 UTCresolved

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

1. 9. März 2022 um 20: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. 9. März 2022 um 22:24 UTCresolved

   This incident has now been resolved.

1. 20. Juli 2021 um 06: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. 20. Juli 2021 um 07: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. 20. Juli 2021 um 08:11 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 20. Juli 2021 um 09: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. 9. Juni 2020 um 22: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. 10. Juni 2020 um 00: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. 10. Juni 2020 um 00:20 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 10. Juni 2020 um 07:38 UTCresolved

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

1. 1. Juli 2019 um 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. 1. Juli 2019 um 16: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. 27. Juni 2019 um 14: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. 27. Juni 2019 um 14:48 UTCmonitoring

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

3. 27. Juni 2019 um 20:40 UTCresolved

   This is now resolved.

1. 21. Juni 2019 um 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. 21. Juni 2019 um 11:07 UTCmonitoring

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

3. 21. Juni 2019 um 14:04 UTCresolved

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

1. 3. Mai 2019 um 13: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. 3. Mai 2019 um 14:02 UTCmonitoring

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

3. 3. Mai 2019 um 20:07 UTCresolved

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

1. 1. April 2019 um 07: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. 1. April 2019 um 07: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. 1. April 2019 um 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. 20. Februar 2019 um 09: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. 20. Februar 2019 um 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. 29. November 2018 um 20: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. 29. November 2018 um 20: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. 29. November 2018 um 21: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. 30. November 2018 um 08:12 UTCresolved

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

1. 10. März 2018 um 13: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. 10. März 2018 um 15: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. 10. März 2018 um 13: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. 10. März 2018 um 15: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. 10. März 2018 um 16:17 UTCresolved

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

1. 8. März 2018 um 20: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.