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

ExamSoft Outage History

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

There were 131 ExamSoft outages since August 2020. The 24 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor March 30, 2026

March 2026: Support Hold Times

Detected Mar 30, 2026 11:06 AM EDT · Resolved Apr 6, 2026 5:02 PM EDT · Duration 7 days

ExamSoft experienced higher than usual support wait times due to issues with NYLE exam registrations and payment processing problems that lasted 174 hours. The incident affected the Support queues and Legacy Portal, with users unable to complete payments for applicant registrations. The issue was resolved by implementing a PayPal checkout workaround for payments, and call volumes eventually returned to normal levels.

Minor March 19, 2026

March 2026: Examplify Monitored Exams Unable to be Reviewed

Detected Mar 19, 2026 12:18 PM EDT · Resolved Mar 25, 2026 4:02 PM EDT · Duration 6 days

ExamSoft experienced a 147.7-hour outage where Examplify monitored exams could not be reviewed by either AI or human reviewers, affecting both Legacy and Enterprise portals as well as Examplify services. The service was restored on March 19th with new monitored exams processing normally, while previously submitted videos that were safely stored during the outage were reprocessed. The incident was fully resolved on March 25th after all backlogged videos were successfully reprocessed.

Minor March 4, 2026

March 2026: Australian 03-8594-1209 Phone Line Issues

Detected Mar 4, 2026 2:39 PM EST · Resolved Mar 16, 2026 11:31 AM EDT · Duration 12 days

ExamSoft's Australian phone line (03-8594-1209) experienced intermittent issues that prevented users from reaching support services. The incident affected the Support component and lasted approximately 284 hours. The issue was resolved, and during the outage users were directed to alternative support channels including a different phone number, online chat, and email support.