Internal Server Error when accessing SpringAhead
Incident Report for SpringAhead
There was a SpringAhead outage starting at about 1:45am PDT and the service was restored a little over 7am PDT. Our recent periods of SpringAhead downtime concern us greatly, as SpringAhead is traditionally the most stable and reliable platform that our company operates, out of about 8 other SaaS platforms. As a result, our development team worked swiftly this morning to research and address the underlying issues, beyond just ensuring the system was back up and running. It appears that SpringAhead’s track record of stability created a risk factor for us as its instances on Amazon Web Services had been running for so long without a relaunch that the underlying infrastructure was not performing as well as it should have been and caused database performance degradation. We’ve cleared out expired jobs and tasks that might have contributed to the degradation and will be executing a planned system downtime to do a complete relaunch.
Posted Oct 03, 2019 - 01:45 PDT