Apideck incident

Ecosystem downtime

Critical Resolved View vendor source →

Apideck experienced a critical incident on May 11, 2021 affecting Ecosystems, lasting 24m. The incident has been resolved; the full update timeline is below.

Started
May 11, 2021, 06:44 AM UTC
Resolved
May 11, 2021, 07:08 AM UTC
Duration
24m
Detected by Pingoru
May 11, 2021, 06:44 AM UTC

Affected components

Ecosystems

Update timeline

  1. investigating May 11, 2021, 06:44 AM UTC

    We are currently investigating this issue.

  2. resolved May 11, 2021, 07:08 AM UTC

    This incident has been resolved.

  3. postmortem May 11, 2021, 07:57 AM UTC

    Between 08.40 and 09:08, multiple ecosystems were affected by downtime. The event was triggered by a problem after a rollback of our production branch. The event was immediately detected, and the team had identified and fixed the issue. The root cause of the problem is being investigated, but it is related to our migration to Vercel. We recommend all customers who have not yet updated the CNAME to do that in [https://app.apideck.com/settings/custom-domain](https://app.apideck.com/settings/custom-domain). This will ensure you get the latest version of Apideck, and we can speed up our migration process. – Jake Prins