История сбоев Honorlock

1. 21 октября 2026 г. в 13:41 UTCinvestigating

   Наша инженерная команда активно реагирует на недавно раскрытую уязвимость в масштабах всей отрасли, затрагивающую веб-инфраструктуру с открытым исходным кодом (CVE-2026-109618/109619). Несмотря на то, что наши основные службы прокторинга остаются в рабочем состоянии, мы временно ограничили несущественные вспомогательные системы и будем проводить целевое обновление обслуживания после официального выпуска патча в 10:00 утра по восточному времени.

2. 21 октября 2026 г. в 13:43 UTCinvestigating

   Мы продолжаем расследование этого вопроса.

3. 21 октября 2026 г. в 14:39 UTCidentified

   Этот вопрос был определен, и в настоящее время осуществляется исправление.

4. 21 октября 2026 г. в 17:10 UTCidentified

   Status Update: Select Honorlock sites have been temporarily taken offline as a preventative security measure. Proctoring services remain fully operational. Cause: Active global exploitation of two newly discovered zero-day vulnerabilities in PHP. Taking sites offline is the only complete safeguard until patches are applied. This is a widespread PHP issue, not an Honorlock system issue. Resolution Plan: Official PHP patches are expected today. We will deploy the fixes immediately upon release and bring all impacted sites back online.

5. 21 октября 2026 г. в 20:43 UTCresolved

   This incident has been resolved.

Автоматический перевод официального обновления инцидента.

1. 14 июня 2026 г. в 00:39 UTCinvestigating

   We are investigating reports of disruptions to the proctoring service and 504 timeout errors. Exam takers may be unable to load, navigate, or resume their exam.

2. 14 июня 2026 г. в 00:44 UTCmonitoring

   A fix has been implemented and we have received reports of improvements. We will continue to monitor the situation.

3. 14 июня 2026 г. в 01:01 UTCresolved

   This incident has been resolved.

1. 7 мая 2026 г. в 22:40 UTCinvestigating

   Honorlock is aware of the ongoing security incident affecting the Instructure (Canvas) platform. In response, all Canvas/Instructure integrations have been temporarily disabled to ensure the continued protection of all user data.

2. 8 мая 2026 г. в 15:33 UTCmonitoring

   Canvas Service Restored: Steps to Re-enable Honorlock. To ensure your institution's data remains protected following the recent Instructure incident, we have proactively disabled some integrations as a security precaution. How to restore your service: To re-activate Honorlock, please refresh your Canvas API credentials and reach out to your Technical CSM or our Support team ([email protected]) to assist with restoring access. For official incident updates from Instructure, visit: instructure.com/incident_update

3. 11 мая 2026 г. в 20:06 UTCresolved

   With account reactivation in the final stages, we are returning to normal status operations. How to restore your service: To re-activate Honorlock, please refresh your Canvas API credentials and reach out to your Technical CSM or our Support team ([email protected]) to assist with restoring access.

1. 25 февраля 2026 г. в 16:19 UTCmonitoring

   In continuation of last night's service outage, we have received reports of delayed or non-sending messages from the agent's end. Our third-party provider is aware and is investigating.

2. 26 февраля 2026 г. в 14:02 UTCresolved

   This incident has been resolved.

1. 25 февраля 2026 г. в 05:02 UTCidentified

   Our third party chat provider has identified the cause of the incident and are working to resolve the issue. In the meantime, support inquiries can be directed to [email protected] for immediate assistance.

2. 25 февраля 2026 г. в 05:29 UTCmonitoring

   We are starting to see improvements with our third party chat provider as agents are now able to receive chats. We will continue monitoring the situation for the time being.

3. 25 февраля 2026 г. в 06:56 UTCmonitoring

   We are continuing to monitor the incident as we have not received an update from our third party chat provider indicating the issue has been resolved. We encourage users unable to initiate a live chat to request assistance via email at [email protected]

4. 25 февраля 2026 г. в 07:29 UTCresolved

   Our third party chat provider has indicated improvements have been seen, which have been confirmed by our team. We will keep an eye out for further issues.

1. 10 февраля 2026 г. в 18:31 UTCinvestigating

   Blackboard has updated their status page to reflect the incident and more information can be found there: https://status.blackboard.com/

2. 10 февраля 2026 г. в 18:38 UTCmonitoring

   We have seen a reduction in support contacts on the Honorlock side, indicating a brief interruption in Blackboard service as they work through the incident.

3. 10 февраля 2026 г. в 19:37 UTCresolved

   We are closing out this incident as we have not received any additional reports of issues, but will continue to monitor the incident posted on Blackboards status page.

1. 15 января 2026 г. в 17:56 UTCinvestigating

   We are currently investigating reports of Blackboard Ultra users receiving a blank screen when attempting to begin an exam using Chrome v144

2. 15 января 2026 г. в 19:11 UTCidentified

   We have identified the root cause of the issue and are working on a solution.

3. 15 января 2026 г. в 21:49 UTCmonitoring

   A fix has been implemented and we are monitoring the results

4. 15 января 2026 г. в 23:39 UTCresolved

   This issue has been resolved.

1. 20 октября 2025 г. в 12:15 UTCmonitoring

   AWS service outage: Sporadic issues regarding launching and starting exams are still ongoing. AWS has made several improvements and are working through processing the backlog of SQS messages in Lambda queues.

2. 20 октября 2025 г. в 13:16 UTCmonitoring

   AWS has reported progress being made on restoring services in the US-EAST-1 Region

3. 20 октября 2025 г. в 15:29 UTCmonitoring

   Additional improvements have been made, the AWS team continue to investigate and restore services.

4. 20 октября 2025 г. в 18:18 UTCmonitoring

   AWS is applying mitigations to the remaining Availability Zones at which point they expect launch errors and network connectivity issues to subside.

5. 20 октября 2025 г. в 20:40 UTCresolved

   Honorlock Services are fully operational, and we will continue to monitor the situation until AWS services are fully restored.

1. 20 октября 2025 г. в 10:42 UTCmonitoring

   As of 3:11 am EST, Amazon Web Services reported increased error rates and latencies in the US-EAST-1 Region. These services prevented some exam takers from starting or continuing their exam, and access to their LMS was sporadically prevented. The majority of AWS services were restored at approximately 6:03 am EST, and they are currently monitoring the situation.

2. 20 октября 2025 г. в 11:00 UTCresolved

   AWS has confirmed this issue has been resolved through their status page.

1. 15 сентября 2025 г. в 01:14 UTCinvestigating

   We have received reports of 504 gateway errors and our engineering team is currently invesitgating the cause.

2. 15 сентября 2025 г. в 01:34 UTCidentified

   We have identified the issue and have implemented a fix.

3. 15 сентября 2025 г. в 01:39 UTCmonitoring

   Our engineering team has confirmed that services have been restored; however, some users may still be impacted. A refresh/reload of the webpage or relaunching of proctoring should correct any current problems. Our engineering team will continue to monitor the situation for the time being.

4. 15 сентября 2025 г. в 01:44 UTCresolved

   This incident has been resolved. All services have been restored.

1. 4 июля 2025 г. в 11:23 UTCmonitoring

   Our provider is currently monitoring the results of a fix they implemented. At this time, support agents are unable to receive chats and customers may experience difficulty initiating them. For now, assistance can be provided through [email protected].

2. 4 июля 2025 г. в 11:34 UTCmonitoring

   Update: Our provider implemented another fix that has brought back some services, users should now be able to initiate chats and connect through to agents.

3. 4 июля 2025 г. в 12:10 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 4 июля 2025 г. в 12:20 UTCresolved

   This incident has been resolved.

1. 27 мая 2025 г. в 10:46 UTCinvestigating

   Our provider is aware and is currently investigating the issue. Customers may be unable to initiate support chats or connect with a live agent. Please submit a ticket via email to [email protected] for assistance.

2. 27 мая 2025 г. в 10:52 UTCidentified

   Our provider has identified the issue and is working on implementing a fix.

3. 27 мая 2025 г. в 13:20 UTCidentified

   Our third party provider is continuing to work on a solution.

4. 27 мая 2025 г. в 15:48 UTCmonitoring

   A fix has been implemented and the results are being monitored by our third party provider. We have seen success with customers reaching support agents.

5. 27 мая 2025 г. в 16:20 UTCresolved

   This incident has been resolved.

1. 17 февраля 2025 г. в 22:51 UTCinvestigating

   We are currently investigating reports of exam takers unable to start their exam. At this time, we would recommend users attempting to start a new exam try again at a later time. Exams that have already started will continue to be proctored. We are actively investigating and will update this post once more information is available.

2. 17 февраля 2025 г. в 22:54 UTCinvestigating

   We are continuing to investigate this issue.

3. 17 февраля 2025 г. в 23:02 UTCidentified

   The issue has been identified and we are implementing a fix.

4. 17 февраля 2025 г. в 23:18 UTCmonitoring

   A fix has been implemented, and we are seeing improvements in exam takers' ability to start assessments.

5. 17 февраля 2025 г. в 23:27 UTCresolved

   This incident has been resolved

1. 16 августа 2024 г. в 11:00 UTCinvestigating

   Our chat provider is currently investigating an issue that is impacting our chat support availability. Due to this, we are unable to answer support chats at this time. We are working directly with our chat provider to resolve this issue as quickly as possible. If you need support assistance, please email [email protected] and we will address your issue once support functionality is restored.

2. 16 августа 2024 г. в 11:37 UTCmonitoring

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

3. 16 августа 2024 г. в 14:03 UTCresolved

   This incident has been resolved!

1. 8 августа 2024 г. в 18:15 UTCinvestigating

   Our chat provider is currently investigating an issue that is impacting our chat support availability. Due to this, we are unable to answer support chats at this time. We are working directly with our chat provider to resolve this issue as quickly as possible. If you need support assistance, please email [email protected] and we will address your issue once support functionality is restored.

2. 8 августа 2024 г. в 18:29 UTCidentified

   Our chat provider is currently investigating an issue that is impacting our chat support availability. The issue has been identified and a fix is currently being implemented. Due to this, we are unable to answer support chats at this time. We are working directly with our chat provider to resolve this issue as quickly as possible. If you need support assistance, please email [email protected] and we will address your issue once support functionality is restored.

3. 8 августа 2024 г. в 21:01 UTCmonitoring

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

4. 8 августа 2024 г. в 22:58 UTCresolved

   This incident has been resolved.

1. 13 июня 2024 г. в 23:19 UTCinvestigating

   We have received several reports of issues when attempting to make payments and are raising the issue with our third party provider. Support agents are available to help; however, their response may be delayed due to the high amount of volume generated from this issue. We appreciate your patience.

2. 13 июня 2024 г. в 23:59 UTCresolved

   This incident has been resolved.

1. 12 июня 2024 г. в 17:31 UTCinvestigating

   Instructure is aware and are currently investigating. Users may see a "This website is under heavy load" error message in Canvas when attempting to take an exam or navigate through Canvas.

2. 12 июня 2024 г. в 17:32 UTCidentified

   Instructure has identified the problem and are working on a fix.

3. 12 июня 2024 г. в 18:31 UTCresolved

   This incident has been resolved.

1. 4 июня 2024 г. в 15:16 UTCinvestigating

   Our third party chat provider is aware of the issue and is currently investigating. Users may be unable to begin a chat or connect with an agent. Please direct all support inquiries to the following email address: [email protected]

2. 4 июня 2024 г. в 15:39 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 4 июня 2024 г. в 16:19 UTCmonitoring

   A fix has been implemented. Our chat provider is monitoring the results. Agents have reported success receiving and responding to chats.

4. 4 июня 2024 г. в 18:37 UTCresolved

   This incident has been resolved.

1. 29 мая 2024 г. в 20:37 UTCidentified

   We’ve received reports that some users are having trouble installing the Honorlock Extension. This appears to be an issue with the Google Chrome store. We are closely monitoring the situation and will update our status page accordingly.

2. 29 мая 2024 г. в 21:21 UTCmonitoring

   Google Chrome Store services appear to be restored. Users are now reporting success when attempting to install extensions.

3. 29 мая 2024 г. в 21:49 UTCresolved

   This incident has been resolved.

1. 1 мая 2024 г. в 13:46 UTCinvestigating

   Users may be unable to begin chats or connect to an agent. Our chat provider is aware of the issue and is currently investigating. Please submit all support inquiries to [email protected] for assistance in the meantime.

2. 1 мая 2024 г. в 14:30 UTCidentified

   The issue has been identified and a fix is being implemented. Our support team is able to assist via [email protected].

3. 1 мая 2024 г. в 15:06 UTCmonitoring

   A fix has been implemented and the results are being monitored. Agents are now able to receive chats.

4. 1 мая 2024 г. в 15:58 UTCmonitoring

   We are continuing to monitor the results of the fix but have seen improvements.

5. 1 мая 2024 г. в 17:09 UTCresolved

   This issue has been resolved.