Code Storage Outage History

Code Storage is up right now

Pingoru has recorded 9 incidents for Code Storage: 9 in the last 12 months and 4 in the last 90 days.

Source: status.code.storage

9incidents recorded
9last 12 months
4last 90 days
47 minutestypical duration
Incidents per month
024AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Code Storage in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202623 of 720 (0%)
May 202621 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202632 of 744 (0%)
September 202600 of 720 (0%)
October 202611 of 744 (0%)
November 202600 of 6 (0%)

Incidents, newest first

Minor October 7, 2026 Elevated errors in GCP Europe West 4 1h 19m AWS US West 2 (API), AWS US West 2 (Git HTTP), AWS US East 2 (API), AWS US East 2 (Git HTTP) and 6 more

Started Oct 07, 2026, 02:30 PM UTC· resolved Oct 07, 2026, 03:49 PM UTC

  1. monitoring Oct 07, 2026, 02:30 PM UTC

    We have identified the cause of the elevated error rates. Since 13:40 UTC, some repository creation requests in GCP Europe West 4 have failed with 503 errors or taken up to two minutes to fail. The cause was a capacity limit in the storage layer for this region. We have moved storage to larger machines. While the move was in progress, between 15:18 and 15:25 UTC, some file reads and Git fetches also returned 503 errors. Error rates have returned to normal since 15:25 UTC. The final part of the move is still in progress, and we are watching error rates until it completes.

  2. resolved Oct 07, 2026, 03:49 PM UTC

    The capacity upgrade in GCP Europe West 4 is complete, and error rates have stayed at normal levels. Between 13:40 and 15:25 UTC, some repository creation requests failed with 503 errors. Between 15:18 and 15:25 UTC, some file reads and Git fetches also failed. Requests that failed during these windows can be retried. We are adding capacity monitoring so we can act before load reaches this limit again.

  3. resolved Oct 07, 2026, 03:49 PM UTC

    The capacity upgrade in GCP Europe West 4 is complete, and error rates have stayed at normal levels. Between 13:40 and 15:25 UTC, some repository creation requests failed with 503 errors. Between 15:18 and 15:25 UTC, some file reads and Git fetches also failed. Requests that failed during these windows can be retried. We are adding capacity monitoring so we can act before load reaches this limit again.

Read the full incident report →

Minor August 21, 2026 Occasional 503 error bursts – GCP US Central 1 (Git HTTP), GCP Europe West 4 (API)

Started Aug 21, 2026, 09:02 PM UTC· resolved Aug 21, 2026, 09:02 PM UTC

  1. monitoring Aug 21, 2026, 08:32 PM UTC

    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

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

    We believe the issue is resolved and are monitoring closely.

Read the full incident report →

Minor August 21, 2026 Disrupted service 30m AWS US West 2 (API), AWS US West 2 (Git HTTP), AWS US East 2 (API), AWS US East 2 (Git HTTP) and 6 more

Started Aug 21, 2026, 08:32 PM UTC· resolved Aug 21, 2026, 09:02 PM UTC

  1. monitoring Aug 21, 2026, 08:32 PM UTC

    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.

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

    The issue was resolved after the mitigation was applied.

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

    The issue was resolved after the mitigation was applied.

Read the full incident report →

Minor August 19, 2026 Git push degraded in GCP EU West 4 1h 9m AWS US West 2 (Git HTTP), AWS US East 2 (Git HTTP), AWS EU Central 1 (Git HTTP), GCP US Central 1 (Git HTTP) and 1 more

Started Aug 19, 2026, 11:46 PM UTC· resolved Aug 20, 2026, 12:55 AM UTC

  1. investigating Aug 19, 2026, 11:46 PM UTC

    Git push operations to GCP EU West 4 are failing intermittently.

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

    We are investigating a degraded NATS cluster in the effected cluster.

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

    We are increasing storage capacity of the effected NATS cluster.

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

    All NATS nodes have fully recovered and we continue to monitor the deployment.

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

    Deployment has remained healthy.

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

    Deployment has remained healthy.

Read the full incident report →

Minor May 19, 2026 Partial degradation of service impacting us-east-2 45m Platform

Started May 19, 2026, 06:45 PM UTC· resolved May 19, 2026, 07:30 PM UTC

  1. investigating May 19, 2026, 06:45 PM UTC

    CreateCommit endpoint regression deployed to us-east-2

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

    We identified a regression to our createCommitPack endpint

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

    Service restored to us-east-2

Read the full incident report →

Minor May 7, 2026 Elevated 503s in us-east-2 4m Platform

Started May 07, 2026, 08:49 PM UTC· resolved May 07, 2026, 08:53 PM UTC

  1. investigating May 07, 2026, 08:49 PM UTC

    The us-east-2 cluster is experiencing elevated rates of 503s affecting both reads and writes. Our team is investigating.

  2. monitoring May 07, 2026, 08:51 PM UTC

    Our team has taken remedial action and is observing recovery, we will continue to monitor.

  3. resolved May 07, 2026, 08:52 PM UTC

    We've observed a complete recovery of traffic.

Read the full incident report →

Minor April 20, 2026 Increased read latency in AWS eu-central-1 1h 59m Platform

Started Apr 20, 2026, 03:09 PM UTC· resolved Apr 20, 2026, 05:08 PM UTC

  1. investigating Apr 20, 2026, 03:09 PM UTC

    Increased latency in p95 read for AWS eu-central-1

  2. resolved Apr 20, 2026, 05:08 PM UTC

    Resolved latency spike around p95 read operations.

Read the full incident report →

Minor April 13, 2026 Increased push latency in AWS eu-central-1 1h 17m Platform

Started Apr 13, 2026, 07:28 PM UTC· resolved Apr 13, 2026, 08:45 PM UTC

  1. identified Apr 13, 2026, 07:28 PM UTC

    Increased push latency affecting customers in AWS eu-central-1.

  2. resolved Apr 13, 2026, 08:45 PM UTC

    Latency impact to us-central-1 has been mitigated.

Read the full incident report →

Critical December 31, 2025 Outage in aws eu-central-1 –

Started Dec 31, 2025, 08:16 PM UTC· resolved Dec 31, 2025, 08:16 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →