CodeSignal Outage History

CodeSignal is up right now

CodeSignal had 3 outages in the last 2 years totaling 11h 16m of downtime — averaging 0.1 incidents per month.

There were 3 CodeSignal outages since July 7, 2025 totaling 11h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.codesignal.com

Major October 20, 2025

External outage

Detected by Pingoru
Oct 20, 2025, 02:10 PM UTC
Resolved
Oct 20, 2025, 10:46 PM UTC
Duration
8h 36m
Affected: CodeSignal LearnCode Execution
Timeline · 3 updates
  1. identified Oct 20, 2025, 02:10 PM UTC

    We are recovering from a major outage caused by issues with an external provider. We recommend not starting assessments or live interviews until the issue is fully resolved.

  2. monitoring Oct 20, 2025, 07:41 PM UTC

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

  3. resolved Oct 20, 2025, 10:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 4, 2025

High Error Rate for IDE

Detected by Pingoru
Aug 04, 2025, 11:58 PM UTC
Resolved
Aug 05, 2025, 12:18 AM UTC
Duration
19m
Affected: Main App
Timeline · 2 updates
  1. investigating Aug 04, 2025, 11:58 PM UTC

    We are currently investigating this issue.

  2. resolved Aug 05, 2025, 12:18 AM UTC

    The error rate is resolved.

Read the full incident report →

Minor July 7, 2025

Learn and Interview Issues

Detected by Pingoru
Jul 07, 2025, 02:50 PM UTC
Resolved
Jul 07, 2025, 05:10 PM UTC
Duration
2h 19m
Affected: Main AppCodeSignal Learn
Timeline · 4 updates
  1. investigating Jul 07, 2025, 02:50 PM UTC

    We're experiencing issues that are impacting Learn practice and Interview sessions. We are currently investigating the issues.

  2. identified Jul 07, 2025, 03:09 PM UTC

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

  3. monitoring Jul 07, 2025, 04:05 PM UTC

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

  4. resolved Jul 07, 2025, 05:10 PM UTC

    This incident has been resolved.

Read the full incident report →