Histórico de interrupções do Codehs

1. 5 Here 2026 da 13:31 UTCinvestigating

   "Nossa equipe de engenharia continua investigando o problema afetando codehs.com e está trabalhando para restaurar o serviço o mais rápido possível. Pedimos desculpas pela interrupção do ensino e aprendizagem e continuaremos a postar atualizações regulares aqui assim que soubermos mais."

2. 5 Here 2026 da 13:56 UTCinvestigating

   Continuamos a investigar esta questão.

3. 5 Here 2026 da 13:58 UTCinvestigating

   "Este incidente foi resolvido e codehs.com está totalmente operacional. Se você ainda tiver problemas, tente atualizar e limpar o cache do seu navegador ou contate nossa equipe em [email protected]."

4. 5 Here 2026 da 14:00 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 23 Gwengolo 2026 da 15:32 UTCmonitoring

   Estamos cientes de um problema que afeta codehs.com e alguns usuários podem ver erros ou páginas falhando em carregar. Uma correção foi implantada e codehs.com está carregando normalmente novamente. Estamos a acompanhar de perto para confirmar que a questão está totalmente resolvida.

2. 23 Gwengolo 2026 da 15:41 UTCresolved

   Este incidente foi resolvido e codehs.com está totalmente operacional. Se ainda tiver problemas, tente atualizar e limpar o cache do seu navegador ou contate nossa equipe em [email protected].

Traduzido automaticamente da atualização oficial do incidente.

1. 1 Here 2025 da 16:57 UTCidentified

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

2. 1 Here 2025 da 17:02 UTCmonitoring

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

3. 1 Here 2025 da 17:09 UTCresolved

   This incident has been resolved.

1. 29 Gwengolo 2025 da 14:02 UTCidentified

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

2. 29 Gwengolo 2025 da 14:03 UTCidentified

   We are continuing to work on a fix for this issue.

3. 29 Gwengolo 2025 da 14:08 UTCmonitoring

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

4. 29 Gwengolo 2025 da 14:37 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 29 Gwengolo 2025 da 14:39 UTCresolved

   This incident has been resolved.

1. 25 Eost 2025 da 14:41 UTCinvestigating

   We are currently investigating.

2. 25 Eost 2025 da 16:38 UTCmonitoring

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

3. 26 Eost 2025 da 15:12 UTCresolved

   This incident has been resolved and site performance has been stabilized.

1. 3 Meurzh 2025 da 15:44 UTCinvestigating

   We are currently investigating this issue.

2. 3 Meurzh 2025 da 15:55 UTCmonitoring

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

3. 3 Meurzh 2025 da 15:55 UTCresolved

   This incident has been resolved.

1. 28 Genver 2025 da 21:43 UTCresolved

   Teachers and students reporting 500 errors across the CodeHS Site.

1. 5 Gwengolo 2024 da 19:06 UTCresolved

   Access to site was down for approximately 20 minutes due to a DDOS attack. Service should be restored, and we are investigating the incident.

1. 28 Eost 2024 da 19:18 UTCinvestigating

   We've identified an issue causing a spike in 500 errors on certain assignment pages and are monitoring the fix.

2. 28 Eost 2024 da 19:23 UTCidentified

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

3. 28 Eost 2024 da 19:33 UTCresolved

   This incident has been resolved.

1. 26 Gouere 2024 da 14:28 UTCinvestigating

   We've identified an issue causing a spike in 500 errors on certain assignment pages and are monitoring the fix.

2. 26 Gouere 2024 da 14:30 UTCresolved

   This incident has been resolved.

1. 16 Mezheven 2024 da 21:06 UTCinvestigating

   Our DNS provider is experiencing downtime. We're monitoring the situation

2. 16 Mezheven 2024 da 21:13 UTCresolved

   This incident has been resolved.

3. 16 Mezheven 2024 da 21:13 UTCpostmortem

   Namecheap had downtime which impacted the availability of the [codehs.com](http://codehs.com) domain

1. 28 Du 2023 da 17:30 UTCresolved

   There was site degradation to to a DDOS attack between 11:05am and 11:25am Central time today until it was resolved. Pages were slow to load or would result in a 504 error.

1. 6 Gwengolo 2023 da 16:19 UTCinvestigating

   We are currently investigating this issue.

2. 6 Gwengolo 2023 da 16:23 UTCidentified

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

3. 6 Gwengolo 2023 da 17:08 UTCresolved

   This incident has been resolved.

1. 7 Mezheven 2023 da 13:56 UTCresolved

   We've identified an issue causing a spike in 500 errors when accessing CodeHS pages. This has now subsided and services are now working as expected.

1. 10 Meurzh 2023 da 19:23 UTCresolved

   AWS had a bug with the database software. Once their fix was identified, we applied the patch. The site was unreachable for about 20-25 minutes over the course of an hour and a half.

1. 8 Kerzu 2022 da 22:57 UTCresolved

   DDoS Attack caused system unreliability that was resolved a few minutes later.

1. 2 Kerzu 2022 da 22:48 UTCmonitoring

   We're monitoring errors happening during a code update.

2. 2 Kerzu 2022 da 23:04 UTCresolved

   Resolved

1. 18 Mae 2022 da 16:07 UTCidentified

   We're having an issue with some student code not saving. Tell students to make sure to keep their page open until we get a fix, which is coming shortly.

2. 18 Mae 2022 da 16:15 UTCmonitoring

   Fix has been made and is in the process of being deployed. Saving code will start working again shortly.

3. 18 Mae 2022 da 16:22 UTCresolved

   Incident resolved. Code saving should be working again

1. 8 Cʼhwevrer 2022 da 18:38 UTCmonitoring

   We've identified an issue causing a spike in 500 errors and are monitoring the fix.

2. 8 Cʼhwevrer 2022 da 21:45 UTCresolved

   This incident has been resolved.

1. 7 Cʼhwevrer 2022 da 17:29 UTCidentified

   We're seeing slowness based on a DDoS attack that we're working to fix.

2. 7 Cʼhwevrer 2022 da 17:39 UTCmonitoring

   We've resolved the issue and the site is now operation. We're continuing to monitor to prevent further disruption.

3. 7 Cʼhwevrer 2022 da 21:37 UTCresolved

   This incident has been resolved.