Zipline incident

Outage due to a configuration error

Critical Resolved View vendor source →

Zipline experienced a critical incident on August 25, 2020 affecting Core Platform and Login/SSO and 1 more component, lasting 1h 28m. The incident has been resolved; the full update timeline is below.

Started
Aug 25, 2020, 11:29 PM UTC
Resolved
Aug 26, 2020, 12:58 AM UTC
Duration
1h 28m
Detected by Pingoru
Aug 25, 2020, 11:29 PM UTC

Affected components

Core PlatformLogin/SSOSearchPublishingNotificationsFiles

Update timeline

  1. investigating Aug 25, 2020, 11:29 PM UTC

    We are currently fixing the issue and should have everything back up and running within 3 minutes.

  2. monitoring Aug 25, 2020, 11:31 PM UTC

    Service has been restored. We are monitoring the situation but expect no other issues at this time.

  3. resolved Aug 26, 2020, 12:58 AM UTC

    We have seen no new issues with the site. The issue was due to a configuration value being changed in a regular deploy that was incompatible with our application. We were able to immediately identify the change, revert it, and bring the site back up. The delay was due to the fix being sent to all of our servers through our zero-downtime deploy process. Thank you for your patience and we apologize for the blip in service.