Kisi incident

API is experiencing issues

Critical Resolved View vendor source →

Kisi experienced a critical incident on February 3, 2022 affecting Endpoints, lasting 13m. The incident has been resolved; the full update timeline is below.

Started
Feb 03, 2022, 11:50 AM UTC
Resolved
Feb 03, 2022, 12:04 PM UTC
Duration
13m
Detected by Pingoru
Feb 03, 2022, 11:50 AM UTC

Affected components

Endpoints

Update timeline

  1. investigating Feb 03, 2022, 10:41 AM UTC

    We are currently investigating an issue with the Kisi API.

  2. investigating Feb 03, 2022, 10:52 AM UTC

    Our engineers are continuing to investigate the issue.

  3. investigating Feb 03, 2022, 11:12 AM UTC

    Our engineers are continuing to investigate the issue.

  4. investigating Feb 03, 2022, 11:39 AM UTC

    Our engineers are continuing to investigate the issue.

  5. investigating Feb 03, 2022, 11:53 AM UTC

    Our engineers has found the issue and are working on bringing the system back up.

  6. resolved Feb 03, 2022, 12:07 PM UTC

    The system is now back up. We are constantly working on various resilience improvements to the API. As part of one of our resilience improvement releases, a configuration error inadvertently denied some of our API traffic. We have taken steps to ensure this does not happen again.