Störungsverlauf von Codehs

1. 5. Oktober 2026 um 13:31 UTCinvestigating

   "Unser Ingenieurteam untersucht weiterhin das Problem von codehs.com und arbeitet daran, den Service so schnell wie möglich wiederherzustellen." Wir entschuldigen uns für die Störung des Lehrens und Lernens und werden hier weiterhin regelmäßige Updates veröffentlichen, sobald wir mehr wissen

2. 5. Oktober 2026 um 13:56 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 5. Oktober 2026 um 13:58 UTCinvestigating

   "Dieser Vorfall wurde behoben und codehs.com ist voll funktionsfähig." Wenn Sie immer noch Probleme haben, versuchen Sie eine harte Aktualisierung und löschen Sie Ihren Browser-Cache oder wenden Sie sich an unser Team unter [email protected]

4. 5. Oktober 2026 um 14:00 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 23. September 2026 um 15:32 UTCmonitoring

   Wir sind uns eines Problems bewusst, das codehs.com betrifft, und einige Benutzer können Fehler oder Seiten sehen, die nicht geladen werden. Ein Fix wurde bereitgestellt und codehs.com wird wieder normal geladen. Wir beobachten genau, um zu bestätigen, dass das Problem vollständig gelöst ist.

2. 23. September 2026 um 15:41 UTCresolved

   Dieser Vorfall wurde behoben und codehs.com ist voll funktionsfähig. Wenn Sie immer noch Probleme haben, versuchen Sie eine harte Aktualisierung und löschen Sie Ihren Browser-Cache oder wenden Sie sich an unser Team unter [email protected].

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 1. Oktober 2025 um 16:57 UTCidentified

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

2. 1. Oktober 2025 um 17:02 UTCmonitoring

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

3. 1. Oktober 2025 um 17:09 UTCresolved

   This incident has been resolved.

1. 29. September 2025 um 14:02 UTCidentified

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

2. 29. September 2025 um 14:03 UTCidentified

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

3. 29. September 2025 um 14:08 UTCmonitoring

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

4. 29. September 2025 um 14:37 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 29. September 2025 um 14:39 UTCresolved

   This incident has been resolved.

1. 25. August 2025 um 14:41 UTCinvestigating

   We are currently investigating.

2. 25. August 2025 um 16:38 UTCmonitoring

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

3. 26. August 2025 um 15:12 UTCresolved

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

1. 3. März 2025 um 15:44 UTCinvestigating

   We are currently investigating this issue.

2. 3. März 2025 um 15:55 UTCmonitoring

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

3. 3. März 2025 um 15:55 UTCresolved

   This incident has been resolved.

1. 28. Januar 2025 um 21:43 UTCresolved

   Teachers and students reporting 500 errors across the CodeHS Site.

1. 5. September 2024 um 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 um 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 um 19:23 UTCidentified

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

3. 28. August 2024 um 19:33 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

1. 16. Juni 2024 um 21:06 UTCinvestigating

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

2. 16. Juni 2024 um 21:13 UTCresolved

   This incident has been resolved.

3. 16. Juni 2024 um 21:13 UTCpostmortem

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

1. 28. November 2023 um 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. September 2023 um 16:19 UTCinvestigating

   We are currently investigating this issue.

2. 6. September 2023 um 16:23 UTCidentified

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

3. 6. September 2023 um 17:08 UTCresolved

   This incident has been resolved.

1. 7. Juni 2023 um 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. März 2023 um 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. Dezember 2022 um 22:57 UTCresolved

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

1. 2. Dezember 2022 um 22:48 UTCmonitoring

   We're monitoring errors happening during a code update.

2. 2. Dezember 2022 um 23:04 UTCresolved

   Resolved

1. 18. Mai 2022 um 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 um 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 um 16:22 UTCresolved

   Incident resolved. Code saving should be working again

1. 8. Februar 2022 um 18:38 UTCmonitoring

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

2. 8. Februar 2022 um 21:45 UTCresolved

   This incident has been resolved.

1. 7. Februar 2022 um 17:29 UTCidentified

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

2. 7. Februar 2022 um 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. Februar 2022 um 21:37 UTCresolved

   This incident has been resolved.