Next Identity incident

Issue with Next Identity API endpoints

Major Resolved View vendor source →

Next Identity experienced a major incident on June 8, 2022 affecting Journeys and Unify API and 1 more component, lasting 1h 48m. The incident has been resolved; the full update timeline is below.

Started
Jun 08, 2022, 09:15 PM UTC
Resolved
Jun 08, 2022, 11:04 PM UTC
Duration
1h 48m
Detected by Pingoru
Jun 08, 2022, 09:15 PM UTC

Affected components

JourneysUnify APIConnect SMS API

Update timeline

  1. investigating Jun 08, 2022, 08:18 PM UTC

    We are currently investigating a potential issue with the Next Identity API endpoints and will provide updates shortly.

  2. identified Jun 08, 2022, 09:15 PM UTC

    We have identified an issue with the IDP endpoints that is causing 502 errors on the Next Identity API service. We will implement a hotfix shortly.

  3. monitoring Jun 08, 2022, 09:33 PM UTC

    The fix has been implemented and we are monitoring the results.

  4. resolved Jun 08, 2022, 11:04 PM UTC

    This incident has been resolved. Please visit the incident postmortem for details.

  5. postmortem Jun 09, 2022, 05:03 PM UTC

    During the scheduled maintenance release for the Next Identity v1.3.21, an issue with the IDP endpoints caused a noticeable amount of 502 errors on the Next Identity API service. The engineering team investigated the issue and promptly applied a hotfix. After monitoring to ensure no further errors were being reported, the incident was considered resolved. The team is currently preparing the detailed report to give further details on the cause, as well as future preventive actions to be implemented. We will release the full report shortly. Thank you for your understanding. ‌ – The Next Reason team