Istoricul incidentelor Codehs

1. 5 octombrie 2026 la 13:31 UTCinvestigating

   "Echipa noastră de inginerie continuă să investigheze problema care afectează codehs.com și lucrează pentru a restabili serviciul cât mai repede posibil. Ne cerem scuze pentru perturbarea predării și învățării și vom continua să postăm actualizări periodice aici de îndată ce vom ști mai multe."

2. 5 octombrie 2026 la 13:56 UTCinvestigating

   Continuăm să investigăm această problemă.

3. 5 octombrie 2026 la 13:58 UTCinvestigating

   "Acest incident a fost rezolvat și codehs.com este pe deplin operațional. Dacă sunteți încă confruntă cu probleme, încercați o reîmprospătare și compensare greu cache browser-ul, sau ajunge la echipa noastră la [email protected]."

4. 5 octombrie 2026 la 14:00 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 23 septembrie 2026 la 15:32 UTCmonitoring

   Suntem conștienți de o problemă care afectează codehs.com și unii utilizatori pot vedea erori sau pagini care nu se încarcă. Un fix a fost implementat și codehs.com se încarcă din nou în mod normal. Monitorizăm îndeaproape pentru a confirma că problema este pe deplin rezolvată.

2. 23 septembrie 2026 la 15:41 UTCresolved

   Acest incident a fost rezolvat și codehs.com este pe deplin operațional. Dacă sunteți încă confruntă cu probleme, încercați o reîmprospătare și compensare greu cache browser-ul, sau ajunge la echipa noastră la [email protected].

Traducere automată din actualizarea oficială a incidentului.

1. 1 octombrie 2025 la 16:57 UTCidentified

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

2. 1 octombrie 2025 la 17:02 UTCmonitoring

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

3. 1 octombrie 2025 la 17:09 UTCresolved

   This incident has been resolved.

1. 29 septembrie 2025 la 14:02 UTCidentified

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

2. 29 septembrie 2025 la 14:03 UTCidentified

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

3. 29 septembrie 2025 la 14:08 UTCmonitoring

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

4. 29 septembrie 2025 la 14:37 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 29 septembrie 2025 la 14:39 UTCresolved

   This incident has been resolved.

1. 25 august 2025 la 14:41 UTCinvestigating

   We are currently investigating.

2. 25 august 2025 la 16:38 UTCmonitoring

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

3. 26 august 2025 la 15:12 UTCresolved

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

1. 3 martie 2025 la 15:44 UTCinvestigating

   We are currently investigating this issue.

2. 3 martie 2025 la 15:55 UTCmonitoring

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

3. 3 martie 2025 la 15:55 UTCresolved

   This incident has been resolved.

1. 28 ianuarie 2025 la 21:43 UTCresolved

   Teachers and students reporting 500 errors across the CodeHS Site.

1. 5 septembrie 2024 la 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 august 2024 la 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 august 2024 la 19:23 UTCidentified

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

3. 28 august 2024 la 19:33 UTCresolved

   This incident has been resolved.

1. 26 iulie 2024 la 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 iulie 2024 la 14:30 UTCresolved

   This incident has been resolved.

1. 16 iunie 2024 la 21:06 UTCinvestigating

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

2. 16 iunie 2024 la 21:13 UTCresolved

   This incident has been resolved.

3. 16 iunie 2024 la 21:13 UTCpostmortem

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

1. 28 noiembrie 2023 la 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 septembrie 2023 la 16:19 UTCinvestigating

   We are currently investigating this issue.

2. 6 septembrie 2023 la 16:23 UTCidentified

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

3. 6 septembrie 2023 la 17:08 UTCresolved

   This incident has been resolved.

1. 7 iunie 2023 la 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 martie 2023 la 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 decembrie 2022 la 22:57 UTCresolved

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

1. 2 decembrie 2022 la 22:48 UTCmonitoring

   We're monitoring errors happening during a code update.

2. 2 decembrie 2022 la 23:04 UTCresolved

   Resolved

1. 18 mai 2022 la 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 mai 2022 la 16:15 UTCmonitoring

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

3. 18 mai 2022 la 16:22 UTCresolved

   Incident resolved. Code saving should be working again

1. 8 februarie 2022 la 18:38 UTCmonitoring

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

2. 8 februarie 2022 la 21:45 UTCresolved

   This incident has been resolved.

1. 7 februarie 2022 la 17:29 UTCidentified

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

2. 7 februarie 2022 la 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 februarie 2022 la 21:37 UTCresolved

   This incident has been resolved.