Resolved -
This incident has been resolved.
Nov 22, 09:32 PST
Update -
The issue has been fixed, and we will continue monitoring for the next 24 hours.
Nov 21, 04:58 PST
Monitoring -
A fix has been implemented and we are monitoring the results.
Nov 21, 01:46 PST
Identified -
The issue has been identified and a fix is being implemented.
Nov 21, 01:36 PST
Update -
The intensity and duration of intermittent issues have been reducing significantly over time. We are working with our cloud vendor to identify the root cause.
Nov 20, 23:28 PST
Update -
Our team is diligently exploring alternative solutions and will provide updates as soon as they become available. We appreciate your patience and understanding as we work to stabilize the affected environments.
Nov 20, 20:45 PST
Investigating -
We’ve identified that the recent fix did not fully resolve the issue. Our team is actively investigating alternative solutions and will share updates as soon as possible. Thank you for your patience and understanding as we work to stabilize the affected environments.
Nov 20, 11:48 PST
Identified -
We have identified the cause of the issue and a potential solution. We are working to deploy and validate the fix in the affected environments. We will update the status based on the results.
Nov 20, 07:52 PST
Update -
We are continuing to investigate the underlying cause. We remain focused on achieving full resolution. We will provide further updates as soon as new details become available.
Nov 20, 07:31 PST
Update -
We are continuing to investigate the underlying cause. We remain focused on achieving full resolution. We will provide further updates as soon as new details become available.
Nov 20, 06:43 PST
Update -
We are continuing to investigate the underlying cause. We remain focused on achieving full resolution. We will provide further updates as soon as new details become available.
Nov 20, 06:12 PST
Update -
We are continuing to investigate the underlying cause. We remain focused on achieving full resolution. We will provide further updates as soon as new details become available.
Nov 20, 05:31 PST
Update -
We are continuing to investigate the cause of the issue and will keep you informed as we make progress toward full resolution.
Nov 20, 03:34 PST
Investigating -
We are currently experiencing intermittent disruptions impacting FlexNet Operations functionalities, resulting in 502 Bad Gateway errors. Our engineering teams are actively investigating this issue with the highest priority and will provide timely updates as progress is made.
Nov 20, 01:18 PST