Apideck incident

Unavailable GraphQL API

Notice Resolved View vendor source →

Apideck experienced a notice incident on May 16, 2019, lasting —. The incident has been resolved; the full update timeline is below.

Started
May 16, 2019, 01:17 PM UTC
Resolved
May 15, 2019, 03:45 PM UTC
Duration
Detected by Pingoru
May 16, 2019, 01:17 PM UTC

Update timeline

  1. resolved May 16, 2019, 01:17 PM UTC

    Because of a dependency version mismatch, our GraphQL API was unavailable.

  2. postmortem May 16, 2019, 01:21 PM UTC

    All of us at Apideck would like to sincerely apologise for the impact this caused. While deploying a new version, we encountered an error. The origin of the problem can be found with the mismatch of the environments of the development, testing, staging and CI/CD environments. This caused the GraphQL API to become unavailable for an extended amount of time. We are adding checks in our staging CI/CD pipeline to make sure that these kind of errors do not occur again.