The corrective actions completed on Tuesday, March 23, have restored normal operating levels. Degraded performance on the database server instances led to the slow processing times and intermittent connectivity issues manifested in the applications. The execution of the re-boot process at 1:00 PM PDT ultimately resolved the issues. This incident is considered closed.
Mar 25, 18:32 PDT
Application restarts have been completed, a database configuration change to improve read/write performance has been applied, and database server re-boots have been performed. The environment is currently functioning as expected. We are actively monitoring.
Mar 23, 13:39 PDT
The applications have been online and stable since approximately 10:15am PDT and we continue to monitor their status. We will continue performing restarts, in an effort to further stabilize the environment, and until a solution has been identified.
Mar 23, 12:29 PDT
We are continuing to investigate this issue.
Mar 23, 11:24 PDT
The applications have been online and stable for approximately 40 minutes. We are going to perform some addition restarts in an effort to further stabilize the environment.
Mar 23, 09:56 PDT
We continue to experience intermittent connectivity and service degradation are investigating while working to maintain service availability.
Mar 23, 09:47 PDT
Application instances have been restarted and service has been restored. We continue to monitor and investigate the degradation.
Mar 23, 09:45 PDT
We are currently experiencing performance degradation and intermittent connectivity disruption on FlexNet Operations ALM and are investigating it.
Mar 23, 08:07 PDT