Identity service inaccessible
Incident Report for Soomo Learning
On Saturday, September 8, starting at 4:12 p.m. MDT, and ending at 4:48 p.m. MDT, our identity service, which is called "glue" internally, experienced degradation in connectivity to its primary database. This prevented some users from progressing from our core platform, which was unaffected, to our legacy platform at

During the period of degradation, we observed requests from 40 distinct IP addresses attempting to pass through the identity service to the Soomo Learning Environment. Some of these requests may have succeeded, but most users during this period of time would have noticed either slowness, or an inability to enter the legacy platform.

We continue to monitor the service closely, and have acted to limit the impact of future connection degradation by increasing the minimum parallelism of the service. Where we had previously been running at minimum a single service instance, we now ensure that at least 2 are running at all times.
Posted about 1 year ago. Sep 08, 2018 - 18:48 EDT