Zamzar incident

API endpoints unavailable for almost 3 minutes

Resolved after 2 hours 34 minutes, on March 10, 2018.

resolved Mar 10, 2018, 03:36 PM UTC

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.

Started
Mar 10, 2018, 01:02 PM UTC
Resolved
Mar 10, 2018, 03:36 PM UTC
Duration
2h 34m
Detected by Pingoru
Mar 10, 2018, 01:02 PM UTC

Update timeline

  1. investigating Mar 10, 2018, 01:02 PM UTC

    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. resolved Mar 10, 2018, 03:36 PM UTC

    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.

Your product runs on more than Zamzar

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →