Code Storage Outage History

Code Storage is up right now

Code Storage had 8 outages in the last 2 years — averaging 0.3 incidents per month.

There were 8 Code Storage outages since December 31, 2025. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.code.storage

Minor August 21, 2026

Disrupted service

Detected by Pingoru
Aug 21, 2026, 09:02 PM UTC
Resolved
Aug 21, 2026, 09:02 PM UTC
Duration
Affected: Git HTTPAPI
Timeline · 2 updates
  1. monitoring Aug 21, 2026, 08:32 PM UTC

    Status: Monitoring A few users saw bursts of 503 errors on Git operations due to a rollout on code.storage. A short-term fix was implemented, and a longer-term fix will roll out shortly. We did not expect more errors and monitored the situation closely. Affected components API (Partial outage) Git HTTP (Partial outage)

  2. resolved Aug 21, 2026, 09:02 PM UTC

    Status: Resolved The issue was resolved after the mitigation was applied. Affected components API (Operational) Git HTTP (Operational)

Read the full incident report →

Minor August 21, 2026

Occasional 503 error bursts

Detected by Pingoru
Aug 21, 2026, 09:02 PM UTC
Resolved
Aug 21, 2026, 09:02 PM UTC
Duration
Affected: Git HTTPAPI
Timeline · 2 updates
  1. monitoring Aug 21, 2026, 08:32 PM UTC

    Status: Monitoring A few users saw bursts of 503 errors on git operations due to a rollout on code.storage. A short term fix has been implemented, and a longer term fix will roll out shortly. We don't expect any more errors, but are monitoring the situation closely Affected components API (Partial outage) Git HTTP (Partial outage)

  2. resolved Aug 21, 2026, 09:02 PM UTC

    Status: Resolved We believe the issue is resolved and are monitoring closely. Affected components API (Operational) Git HTTP (Operational)

Read the full incident report →

Minor August 20, 2026

Git push degraded in GCP EU West 4

Detected by Pingoru
Aug 20, 2026, 12:55 AM UTC
Resolved
Aug 20, 2026, 12:55 AM UTC
Duration
Affected: Git HTTP
Timeline · 5 updates
  1. investigating Aug 19, 2026, 11:46 PM UTC

    Status: Investigating Git push operations to GCP EU West 4 are failing intermittently. Affected components Git HTTP (Partial outage)

  2. investigating Aug 20, 2026, 12:10 AM UTC

    Status: Investigating We are investigating a degraded NATS cluster in the effected cluster. Affected components Git HTTP (Partial outage)

  3. identified Aug 20, 2026, 12:15 AM UTC

    Status: Identified We are increasing storage capacity of the effected NATS cluster. Affected components Git HTTP (Operational)

  4. monitoring Aug 20, 2026, 12:48 AM UTC

    Status: Monitoring All NATS nodes have fully recovered and we continue to monitor the deployment. Affected components Git HTTP (Operational)

  5. resolved Aug 20, 2026, 12:55 AM UTC

    Status: Resolved Deployment has remained healthy. Affected components Git HTTP (Operational)

Read the full incident report →

Minor May 19, 2026

Partial degradation of service impacting us-east-2

Detected by Pingoru
May 19, 2026, 07:30 PM UTC
Resolved
May 19, 2026, 07:30 PM UTC
Duration
Affected: Platform
Timeline · 3 updates
  1. investigating May 19, 2026, 06:45 PM UTC

    Status: Investigating CreateCommit endpoint regression deployed to us-east-2 Affected components Platform (Partial outage)

  2. identified May 19, 2026, 06:45 PM UTC

    Status: Identified We identified a regression to our createCommitPack endpint Affected components Platform (Operational)

  3. resolved May 19, 2026, 07:30 PM UTC

    Status: Resolved Service restored to us-east-2 Affected components Platform (Operational)

Read the full incident report →

Minor May 7, 2026

Elevated 503s in us-east-2

Detected by Pingoru
May 07, 2026, 08:53 PM UTC
Resolved
May 07, 2026, 08:53 PM UTC
Duration
Timeline · 1 update
  1. resolved May 07, 2026, 08:53 PM UTC

    Status: Resolved We've observed a complete recovery of traffic.

Read the full incident report →