One Identity Starling incident
Starling Connect - New subscriptions may be inaccessible
Resolved after 10 days 20 hours, affecting Connect, on February 27, 2020.
The fix has been implemented and we are monitoring the results.
Affected components
Update timeline
- 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.
- investigating Feb 28, 2020, 02:22 AM UTC
We are continuing to investigate this issue.
- 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.
- 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.
- identified Mar 04, 2020, 02:37 PM UTC
QA testing of the fix is complete, release is planned for 5th March 2020.
- monitoring Mar 05, 2020, 11:27 AM UTC
The fix has been implemented and we are monitoring the results.
- resolved Mar 09, 2020, 10:01 AM UTC
This incident has been resolved.
Your product runs on more than One Identity Starling
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services