Is Code Storage down?

Last checked 1m ago
Current status
Code Storage is up

No incidents right now.

Code Storage is operational right now. Last checked 1m ago; the most recent incident resolved 24d ago.

Real-time Code Storage status, recent outages, and incident history: pulled directly from Code Storage's official status page at status.code.storage every 5 minutes. Pingoru tracks 11 Code Storage services and has captured 4 incidents in the last 90 days (96.97% uptime). Get email, Slack, Discord, or webhook alerts the moment Code Storage reports a new incident, free for 3 monitors, no credit card.

Users who monitor Code Storage also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 8,000+ providers
Code Storage uptime 96.97% uptime · past 90 days
Mon Wed Fri
AugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1h 19m
    Started Oct 07, 2026, 02:30 PM UTC · Resolved Oct 07, 2026, 03:49 PM UTC
    APIGit HTTPAPIGit HTTPAPIGit HTTPAPIGit HTTPAPIGit HTTP
    Timeline · 2 updates
    • monitoring · Oct 07, 2026, 02:30 PM UTC

      Status: Monitoring 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. Affected components API (Degraded performance) Git HTTP (Degraded performance)

    • resolved · Oct 07, 2026, 03:49 PM UTC

      Status: Resolved 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. Affected components API (Operational) Git HTTP (Operational)

    Latest: Status: Resolved 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…

  2. Resolved –
    Started Aug 21, 2026, 09:02 PM UTC · Resolved Aug 21, 2026, 09:02 PM UTC
    Git HTTPAPI
    Timeline · 2 updates
    • 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)

    • 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)

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

  3. Resolved 30m
    Started Aug 21, 2026, 08:32 PM UTC · Resolved Aug 21, 2026, 09:02 PM UTC
    APIGit HTTPAPIGit HTTPAPIGit HTTPAPIGit HTTPAPIGit HTTP
    Timeline · 2 updates
    • 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)

    • 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)

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

  4. Resolved 1h 9m
    Started Aug 19, 2026, 11:46 PM UTC · Resolved Aug 20, 2026, 12:55 AM UTC
    Git HTTPGit HTTPGit HTTPGit HTTPGit HTTP
    Timeline · 5 updates
    • 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)

    • 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)

    • 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)

    • 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)

    • resolved · Aug 20, 2026, 12:55 AM UTC

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

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

Incident record

Since April 2026 · incident.io · 11 components checked every 5 minutes
12incidents recorded
12last 12 months
4last 90 days
35 minutestypical duration, 12 months

The longest incident in the last year, Increased read latency in AWS eu-central-1 on April 20, 2026, ran for 118 minutes.

Most affected components, last 12 months

  • Git HTTP4
  • Platform4
  • API3
  • Git HTTP3
  • Git HTTP3

Latest incidents

  • Elevated errors in GCP Europe West 4 October 7, 2026 · 79 minutes · degraded service

    Status: Monitoring We have identified the cause of the elevated error rates. Since 13:40 UTC, some repository creation requests in GCP Europe West 4 have…

  • Occasional 503 error bursts August 21, 2026 · under a minute · degraded service

    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…

  • Disrupted service August 21, 2026 · 30 minutes · degraded service

    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…

Outage history

Past 90 days · 4 incidents View full outage history →