All Systems Operational

About This Site

Welcome to Soomo Learning's status page. Your friends at Soomo keep a close eye on the systems behind the scenes. Any interruptions planned or otherwise will be noted here. If you are experiencing any sort of trouble with Soomo Learning webtexts, please give us a heads up by emailing support@soomolearning.com or calling our friendly help desk staff at 888.240.0314. Thanks!

Soomolearning.com   ? Operational
Webtexts.com   ? Operational
Mobile Services   ? Operational
Soomo Messenger   ? Operational
LMS Grade Updates   ? Operational
Link Checking   ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Core App Response Time ?
Fetching
System Availability ?
Fetching
Past Incidents
Sep 22, 2018

No incidents reported today.

Sep 21, 2018

No incidents reported.

Sep 20, 2018

No incidents reported.

Sep 19, 2018

No incidents reported.

Sep 18, 2018

No incidents reported.

Sep 17, 2018

No incidents reported.

Sep 16, 2018

No incidents reported.

Sep 15, 2018

No incidents reported.

Sep 14, 2018

No incidents reported.

Sep 13, 2018

No incidents reported.

Sep 12, 2018

No incidents reported.

Sep 11, 2018

No incidents reported.

Sep 10, 2018

No incidents reported.

Sep 9, 2018

No incidents reported.

Sep 8, 2018
Resolved - 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 courses.soomopublishing.com.

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.
Sep 8, 18:48 EDT