Apideck incident

Unavailable GraphQL API

Critical Resolved View vendor source →

Apideck experienced a critical incident on February 18, 2020 affecting Ecosystems and Web application, lasting 42m. The incident has been resolved; the full update timeline is below.

Started
Feb 18, 2020, 12:41 AM UTC
Resolved
Feb 18, 2020, 01:24 AM UTC
Duration
42m
Detected by Pingoru
Feb 18, 2020, 12:41 AM UTC

Affected components

EcosystemsWeb application

Update timeline

  1. investigating Feb 18, 2020, 12:41 AM UTC

    We are currently investigating this issue.

  2. identified Feb 18, 2020, 12:48 AM UTC

    The issue has been identified as being caused by one of our subprocessors, Prisma. We're reaching out to them to resolve the problem asap.

  3. resolved Feb 18, 2020, 01:24 AM UTC

    This incident has been resolved.

  4. postmortem Feb 18, 2020, 01:47 PM UTC

    Due to an issue with Prisma Cloud, we have experienced a major outage. This third party vendor is critical to our infrastructure. To make sure that a similar incident with Prisma Cloud does not occur, we will be looking to proxy this service for all customer-related infrastructure. This will be done in phases, because of the critical nature of the vendor.