Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Renaissance Learning Outage History

Every past Renaissance Learning outage tracked by IsDown, with detection times, duration, and resolution details.

There were 87 Renaissance Learning outages since January 2022. The 18 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Major May 7, 2026

May 2026: Renaissance Webform Unavailable

Detected May 7, 2026 3:54 PM EDT · Resolved May 7, 2026 8:49 PM EDT · Duration about 5 hours

Renaissance Learning's customer support webform was unavailable for 4.9 hours, preventing customers from submitting support requests through this channel. The company worked with their vendor to resolve the issue while directing customers to use email, phone, or chat support as alternatives. The webform was fully restored and returned to normal operation.

Minor April 23, 2026

April 2026: DnA Online Testing Producing Errors

Detected Apr 23, 2026 3:30 PM EDT · Resolved Apr 27, 2026 4:10 PM EDT · Duration 4 days

Renaissance Learning's DnA Online Testing service experienced 504/503 errors and general slowness due to a configuration change that prevented the application from scaling properly during increased demand. The issue was resolved by rolling back the problematic configuration change, restoring normal performance. The incident lasted approximately 96.7 hours and affected users' ability to access the Online Testing application within DnA.

Minor March 25, 2026

March 2026: Items in Draft Item Bank Assessments Not Displaying Answer Choices

Detected Mar 25, 2026 9:43 AM EDT · Resolved Mar 26, 2026 8:17 AM EDT · Duration about 23 hours

A software change caused items in unpublished Item Bank assessments to display using earlier saved versions, resulting in question stems appearing without answer choices for many items. The issue affected the DnA component for 22.6 hours until the problematic change was reverted and item versions were restored. Items created between 6:30 AM and 10:00 AM EDT during the incident required re-authoring as their most recent versions could not be recovered.