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

Honorlock Outage History

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

There were 61 Honorlock outages since June 2019. The 9 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Major May 7, 2026

May 2026: Service Suspended for Canvas Integrations (Security Precaution)

Detected May 7, 2026 6:40 PM EDT · Resolved May 11, 2026 4:07 PM EDT · Duration 4 days

Honorlock temporarily disabled all Canvas integrations for 93.4 hours as a security precaution in response to an ongoing security incident affecting the Instructure (Canvas) platform. The suspension affected Canvas proctoring services to protect user data during the security event. The service was restored after Canvas resolved their incident, requiring institutions to refresh their Canvas API credentials and contact Honorlock support to reactivate their integrations.

Minor February 25, 2026

February 2026: 3rd party chat provider experiencing service outage.

Detected Feb 25, 2026 11:19 AM EST · Resolved Feb 26, 2026 9:05 AM EST · Duration about 22 hours

Honorlock's third-party chat provider experienced a service outage that caused delayed or non-sending messages from support agents. The incident affected the Support component and lasted 21.8 hours. The issue was resolved after the third-party provider completed their investigation and repairs.

Major February 25, 2026

February 2026: 3rd party chat provider experiencing service outage.

Detected Feb 25, 2026 12:02 AM EST · Resolved Feb 25, 2026 2:31 AM EST · Duration about 2 hours

Honorlock's third-party chat provider experienced a service outage that prevented users from initiating live chat support for 2.5 hours. The support component was affected, requiring users to contact support via email during the incident. The chat provider identified and resolved the underlying issue, with improvements confirmed and chat functionality restored.