Renaissance Learning Outage History

A fix has been implemented and we are monitoring the results.

We are continuing to monitor for any further issues.

A final fix was applied today 5/11, while the initial fix significantly mitigated occurrence, we identified a narrow scenario where the experience may be impacted by a cached session which the current fix addressed. We will continue to monitor system performance and behavior for the next 24 hours. We expect to close this incident post conclusion of the monitoring activity.

Earlier today, DnA Online Testing was experiencing errors, including 504/503 and general slowness. Online Testing is now back online after reverting a scheduled maintenance update. Our Engineering teams are continuing to closely monitor the situation, and updates will be posted here as they become available. We apologize for any inconvenience this may have caused.

We experienced an issue affecting the Online Testing application within DnA. During a period of increased demand, the service did not scale as expected, which resulted in degraded performance and a failure of the Online Testing application. Our engineering team identified that a recent configuration change unintentionally impacted the application’s ability to scale. Once identified, the change was promptly rolled back, and performance returned to normal. We are now implementing additional safeguards, including enhanced monitoring and alerting, to help prevent this type of issue in the future and to ensure faster detection and response should a similar scaling condition arise again. We apologize for the inconvenience this may have caused and appreciate your patience as we continue to improve the reliability and resilience of our systems.

A fix has been implemented and we are monitoring the results.

Overnight, Renaissance released a change that unexpectedly caused an issue affecting unpublished Item Bank assessments in DnA. As a result, some items were displayed using an earlier saved version rather than the most recent one. In many cases, this meant the question stem appeared without its answer choices. We’ve identified and reverted the change that introduced this issue and have restored the latest versions of all items authored prior to today. Unfortunately, for items authored between 6:30 AM and 10:00 AM EDT today, we’re unable to restore the most recent version. Items created during this window will need to be reauthored or edited. We sincerely apologize for the inconvenience this caused and appreciate your understanding. If you have questions or need assistance, our Customer Support team is here to help.

The resolution has been deployed and the verification has been completed. Our Engineers will continue to monitor the issue for any further instances.

Due to the AWS outage, Renaissance programs are being affected at this time. We are seeing issues with logging in, item banks not loading, and blank white pages. Our Teams are continuing to monitor Renaissance programs while AWS works to resolve the outage. We will provide updates on this page as soon as they are made available.

We are beginning to see improvements for item banks and logins but these improvements can be sporadic. Our Teams are continuing to monitor Renaissance programs while AWS works to resolve the outage. We will provide updates on this page as soon as they are made available.

AWS is beginning to see recovery with their services. Renaissance Teams are showing that DnA item banks have recovered and RGP issues are recovering gradually. We will continue to provide updates as they are made available.

Service recovery across all AWS services continues to improve. Renaissance Teams will continue to monitor the health status of AWS and Renaissance programs through to resolution of this outage.

AWS has deemed this outage as resolved. Our Teams have verified that Renaissance programs are working as expected at this time. Renaissance will be monitoring the programs overnight and into the morning for any behavior that could be an issue resulting from this outage.

Some administrators using Ren Next for Leaders had received a 500 error message when logging into RGP. This issue was identified and a fix was implemented. We will continue to monitor this issue for the remainder of today and then move this page to resolved.

A fix has been implemented and we are monitoring the results.

A fix has been implemented and we are monitoring the results.

A fix has been implemented and we are monitoring the results.

We are continuing to monitor for any further issues.