One Identity Starling incident

Starling Connect - New subscriptions may be inaccessible

Major Resolved View vendor source →

One Identity Starling experienced a major incident on February 27, 2020 affecting Connect, lasting 10d 20h. The incident has been resolved; the full update timeline is below.

Started
Feb 27, 2020, 01:01 PM UTC
Resolved
Mar 09, 2020, 10:01 AM UTC
Duration
10d 20h
Detected by Pingoru
Feb 27, 2020, 01:01 PM UTC

Affected components

Connect

Update timeline

  1. investigating Feb 27, 2020, 01:01 PM UTC

    We are experiencing an issue with Starling Connect where newly created subscriptions may be inaccessible. Existing subscriptions are not affected. Our engineers are working to resolve the issue.

  2. investigating Feb 28, 2020, 02:22 AM UTC

    We are continuing to investigate this issue.

  3. identified Feb 28, 2020, 10:48 AM UTC

    We are experiencing an issue with Starling Connect where newly created subscriptions may be inaccessible. Existing subscriptions are not affected. The issue has been identified and our engineers are working on a fix.

  4. identified Mar 03, 2020, 11:18 AM UTC

    We now have a fix for the issue which is currently undergoing QA testing prior to release.

  5. identified Mar 04, 2020, 02:37 PM UTC

    QA testing of the fix is complete, release is planned for 5th March 2020.

  6. monitoring Mar 05, 2020, 11:27 AM UTC

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

  7. resolved Mar 09, 2020, 10:01 AM UTC

    This incident has been resolved.