Codehs driftsforstyrrelser

1. 5. oktober 2026 kl. 13.31 UTCinvestigating

   "Vores ingeniørteam fortsætter med at undersøge det spørgsmål, der påvirker codehs.com og arbejder på at genoprette service så hurtigt som muligt. Vi undskylder for afbrydelsen af undervisning og læring og vil fortsætte med at sende regelmæssige opdateringer her, så snart vi ved mere"

2. 5. oktober 2026 kl. 13.56 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål.

3. 5. oktober 2026 kl. 13.58 UTCinvestigating

   "Denne hændelse er blevet løst og codehs.com er fuldt operationel. Hvis du stadig oplever problemer, skal du prøve en hård opdatering og rydde din browser cache, eller nå ud til vores team på support @ codehs.com."

4. 5. oktober 2026 kl. 14.00 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 23. september 2026 kl. 15.32 UTCmonitoring

   Vi er klar over et problem, der påvirker codehs.com og nogle brugere kan se fejl eller sider undlader at indlæse. Et fix er blevet indsat og codehs.com er lastning normalt igen. Vi overvåger nøje for at bekræfte, at spørgsmålet er helt løst.

2. 23. september 2026 kl. 15.41 UTCresolved

   Denne hændelse er blevet løst, og codehs.com er fuldt operationel. Hvis du stadig oplever problemer, skal du prøve en hård opdatering og rydde din browser cache, eller nå ud til vores team på support @ codehs.com.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 1. oktober 2025 kl. 16.57 UTCidentified

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

2. 1. oktober 2025 kl. 17.02 UTCmonitoring

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

3. 1. oktober 2025 kl. 17.09 UTCresolved

   This incident has been resolved.

1. 29. september 2025 kl. 14.02 UTCidentified

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

2. 29. september 2025 kl. 14.03 UTCidentified

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

3. 29. september 2025 kl. 14.08 UTCmonitoring

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

4. 29. september 2025 kl. 14.37 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 29. september 2025 kl. 14.39 UTCresolved

   This incident has been resolved.

1. 25. august 2025 kl. 14.41 UTCinvestigating

   We are currently investigating.

2. 25. august 2025 kl. 16.38 UTCmonitoring

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

3. 26. august 2025 kl. 15.12 UTCresolved

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

1. 3. marts 2025 kl. 15.44 UTCinvestigating

   We are currently investigating this issue.

2. 3. marts 2025 kl. 15.55 UTCmonitoring

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

3. 3. marts 2025 kl. 15.55 UTCresolved

   This incident has been resolved.

1. 28. januar 2025 kl. 21.43 UTCresolved

   Teachers and students reporting 500 errors across the CodeHS Site.

1. 5. september 2024 kl. 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 kl. 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 kl. 19.23 UTCidentified

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

3. 28. august 2024 kl. 19.33 UTCresolved

   This incident has been resolved.

1. 26. juli 2024 kl. 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 kl. 14.30 UTCresolved

   This incident has been resolved.

1. 16. juni 2024 kl. 21.06 UTCinvestigating

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

2. 16. juni 2024 kl. 21.13 UTCresolved

   This incident has been resolved.

3. 16. juni 2024 kl. 21.13 UTCpostmortem

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

1. 28. november 2023 kl. 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 kl. 16.19 UTCinvestigating

   We are currently investigating this issue.

2. 6. september 2023 kl. 16.23 UTCidentified

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

3. 6. september 2023 kl. 17.08 UTCresolved

   This incident has been resolved.

1. 7. juni 2023 kl. 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. marts 2023 kl. 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. december 2022 kl. 22.57 UTCresolved

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

1. 2. december 2022 kl. 22.48 UTCmonitoring

   We're monitoring errors happening during a code update.

2. 2. december 2022 kl. 23.04 UTCresolved

   Resolved

1. 18. maj 2022 kl. 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. maj 2022 kl. 16.15 UTCmonitoring

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

3. 18. maj 2022 kl. 16.22 UTCresolved

   Incident resolved. Code saving should be working again

1. 8. februar 2022 kl. 18.38 UTCmonitoring

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

2. 8. februar 2022 kl. 21.45 UTCresolved

   This incident has been resolved.

1. 7. februar 2022 kl. 17.29 UTCidentified

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

2. 7. februar 2022 kl. 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 kl. 21.37 UTCresolved

   This incident has been resolved.