CodeHS Outage History

CodeHS is up right now

CodeHS had 3 outages in the last 2 years totaling 25h 20m of downtime — averaging 0.1 incidents per month.

There were 3 CodeHS outages since August 25, 2025 totaling 25h 20m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.codehs.com

Major October 1, 2025

Users Experiencing 503

Detected by Pingoru
Oct 01, 2025, 04:57 PM UTC
Resolved
Oct 01, 2025, 05:09 PM UTC
Duration
11m
Affected: Main WebsiteCode ServerCodeHS Lite
Timeline · 3 updates
  1. identified Oct 01, 2025, 04:57 PM UTC

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

  2. monitoring Oct 01, 2025, 05:02 PM UTC

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

  3. resolved Oct 01, 2025, 05:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 29, 2025

504 Errors sitewide

Detected by Pingoru
Sep 29, 2025, 02:02 PM UTC
Resolved
Sep 29, 2025, 02:39 PM UTC
Duration
36m
Affected: Main WebsiteCode ServerCodeHS Lite
Timeline · 7 updates
  1. identified Sep 29, 2025, 02:02 PM UTC

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

  2. identified Sep 29, 2025, 02:03 PM UTC

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

  3. monitoring Sep 29, 2025, 02:08 PM UTC

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

  4. monitoring Sep 29, 2025, 02:08 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Sep 29, 2025, 02:12 PM UTC

    We are continuing to monitor for any further issues.

  6. monitoring Sep 29, 2025, 02:37 PM UTC

    We are continuing to monitor for any further issues.

  7. resolved Sep 29, 2025, 02:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 25, 2025

Users experiencing 504 errors and page load delays

Detected by Pingoru
Aug 25, 2025, 02:41 PM UTC
Resolved
Aug 26, 2025, 03:12 PM UTC
Duration
1d
Affected: Main Website
Timeline · 3 updates
  1. investigating Aug 25, 2025, 02:41 PM UTC

    We are currently investigating.

  2. monitoring Aug 25, 2025, 04:38 PM UTC

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

  3. resolved Aug 26, 2025, 03:12 PM UTC

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

Read the full incident report →