Storj Outage History

Storj is up right now

Storj had 38 outages in the last 2 years totaling 62h 3m of downtime — averaging 1.6 incidents per month.

There were 38 Storj outages since June 11, 2024 totaling 62h 3m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.storj.io

Major March 18, 2026

Elevated Error Rates

Detected by Pingoru
Mar 18, 2026, 07:44 PM UTC
Resolved
Mar 18, 2026, 10:35 PM UTC
Duration
2h 50m
Affected: US1 - GatewayUS1 - Select
Timeline · 5 updates
  1. investigating Mar 18, 2026, 07:44 PM UTC

    We are investigating reports of elevated error rates from our API services.

  2. identified Mar 18, 2026, 08:12 PM UTC

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

  3. identified Mar 18, 2026, 08:59 PM UTC

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

  4. monitoring Mar 18, 2026, 09:25 PM UTC

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

  5. resolved Mar 18, 2026, 10:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 6, 2026

Elevated error rates for US1 Select

Detected by Pingoru
Mar 06, 2026, 10:10 AM UTC
Resolved
Mar 06, 2026, 12:31 PM UTC
Duration
2h 20m
Affected: US1 - Select
Timeline · 3 updates
  1. investigating Mar 06, 2026, 10:10 AM UTC

    We are currently investigating this issue.

  2. monitoring Mar 06, 2026, 10:48 AM UTC

    We have applied a fix for the previously mentioned performance impact and are continuing to monitor the system.

  3. resolved Mar 06, 2026, 12:31 PM UTC

    The previously identified issue affecting performance has been resolved.

Read the full incident report →

Minor February 24, 2026

Increased error rates on US1 services

Detected by Pingoru
Feb 24, 2026, 06:26 PM UTC
Resolved
Feb 24, 2026, 07:32 PM UTC
Duration
1h 6m
Affected: US1 - APIUS1 - LinksharingUS1 - GatewayUS1 - Select
Timeline · 5 updates
  1. investigating Feb 24, 2026, 06:26 PM UTC

    We are investigating the issue

  2. investigating Feb 24, 2026, 06:27 PM UTC

    We are continuing to investigate this issue.

  3. identified Feb 24, 2026, 06:58 PM UTC

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

  4. monitoring Feb 24, 2026, 06:58 PM UTC

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

  5. resolved Feb 24, 2026, 07:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 15, 2025

Issue with elevated error rates for uploads

Detected by Pingoru
Dec 15, 2025, 12:31 PM UTC
Resolved
Dec 15, 2025, 12:31 PM UTC
Duration
—
Affected: US1 - Select
Timeline · 1 update
  1. resolved Dec 15, 2025, 12:31 PM UTC

    The issue with elevated error rates for uploads has been resolved for all affected users. The incident was limited to a region-specific storage tier in the United States.

Read the full incident report →

Notice September 18, 2025

www.storj.io returning 500 errors

Detected by Pingoru
Sep 18, 2025, 06:41 PM UTC
Resolved
Sep 18, 2025, 07:34 PM UTC
Duration
52m
Timeline · 2 updates
  1. investigating Sep 18, 2025, 06:41 PM UTC

    The main storj landing page is returning 500 errors. All Storj services remain unaffected. Use https://www.storj.io/login to login to the web console and use your accounts until this is resolved.

  2. resolved Sep 18, 2025, 07:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 13, 2025

EU1 access keys becoming non-functional

Detected by Pingoru
Sep 13, 2025, 05:52 AM UTC
Resolved
Sep 13, 2025, 08:22 AM UTC
Duration
2h 30m
Affected: EU1 - LinksharingEU1 - Gateway
Timeline · 4 updates
  1. investigating Sep 13, 2025, 07:42 AM UTC

    We have been alerted to an issue causing access keys in the EU1 region to stop working.

  2. investigating Sep 13, 2025, 08:14 AM UTC

    We are continuing to investigate this issue.

  3. resolved Sep 13, 2025, 08:22 AM UTC

    This incident has been resolved.

  4. postmortem Sep 19, 2025, 03:30 PM UTC

    On September 13th, 2025, we experienced an issue that caused access keys to stop working for some customers in the EU1 region. This problem was isolated to a small subset of our infrastructure. We identified the root cause as a database configuration mismatch that occurred during a software update performed the previous day at approximately 21:12 UTC. Our team quickly redirected traffic away from the affected server to minimize service interruption. After implementing the necessary configuration changes, we were able to restore full functionality. The service has fully recovered, and we're taking steps to prevent similar issues in the future. We apologize for any inconvenience this may have caused.

Read the full incident report →

Minor September 3, 2025

Elevated error rates during uploads for US1 select

Detected by Pingoru
Sep 03, 2025, 07:44 PM UTC
Resolved
Sep 03, 2025, 09:49 PM UTC
Duration
2h 4m
Affected: US1 - Select
Timeline · 4 updates
  1. investigating Sep 03, 2025, 08:13 PM UTC

    We are investigating reports of elevated error rates during uploads

  2. identified Sep 03, 2025, 08:14 PM UTC

    The issue has been identified and a fix is being applied

  3. monitoring Sep 03, 2025, 09:09 PM UTC

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

  4. resolved Sep 03, 2025, 09:49 PM UTC

    This incident has been resolved

Read the full incident report →

Major August 26, 2025

Elevated Error Rate

Detected by Pingoru
Aug 26, 2025, 05:32 AM UTC
Resolved
Aug 26, 2025, 06:41 AM UTC
Duration
1h 8m
Affected: US1 - APIUS1 - GatewayUS1 - Select
Timeline · 3 updates
  1. identified Aug 26, 2025, 05:32 AM UTC

    We have identified the cause of the elevated API error rate and will be applying a fix shortly.

  2. monitoring Aug 26, 2025, 06:19 AM UTC

    A fix has been applied and we will continue to monitor the system.

  3. resolved Aug 26, 2025, 06:41 AM UTC

    The previously identified issue has been resolved.

Read the full incident report →

Major June 18, 2025

Elevated error levels on Storj US1

Detected by Pingoru
Jun 18, 2025, 07:59 AM UTC
Resolved
Jun 18, 2025, 02:27 PM UTC
Duration
6h 27m
Affected: US1 - APIUS1 - LinksharingUS1 - GatewayUS1 - Select
Timeline · 4 updates
  1. investigating Jun 18, 2025, 07:59 AM UTC

    Some requests to Storj US1 are failing with error 500. We are investigating the issue.

  2. monitoring Jun 18, 2025, 09:55 AM UTC

    We identified high lock time in the database and we scaled it up. We are already seeing reduced error levels as we continue to monitor.

  3. monitoring Jun 18, 2025, 01:58 PM UTC

    Our additional analysis spotted a problem with the Redis cache. We restarted Redis and saw the remaining errors clearing.

  4. resolved Jun 18, 2025, 02:27 PM UTC

    No more errors have been observed since the last intervention.

Read the full incident report →

Major May 22, 2025

Performance Impact

Detected by Pingoru
May 22, 2025, 01:53 AM UTC
Resolved
May 22, 2025, 05:13 AM UTC
Duration
3h 20m
Affected: AP1 - APIEU1 - APIUS1 - APIAP1 - GatewayEU1 - GatewayUS1 - GatewayUS1 - Select
Timeline · 5 updates
  1. investigating May 22, 2025, 02:09 AM UTC

    We are investigating reports of performance impacts to one or more components of our system.

  2. investigating May 22, 2025, 02:09 AM UTC

    We are continuing to investigate this issue.

  3. monitoring May 22, 2025, 02:47 AM UTC

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

  4. resolved May 22, 2025, 05:13 AM UTC

    This incident has been resolved.

  5. postmortem May 23, 2025, 05:20 PM UTC

    On May 22, 2025 from 00:12 to 02:54 UTC Storj experienced a service disruption causing elevated error rates and increased request latency that affected the US1 API, Gateway, Linksharing, and US1 - Select services. We discovered lock contention triggered by high-load delete operations. In the short term, we are artificially slowing down some of these intensive requests to leave needed headroom. We will eliminate the lock contention going forward.

Read the full incident report →

Minor May 6, 2025

US1 Elevated Error Rates

Detected by Pingoru
May 06, 2025, 05:22 PM UTC
Resolved
May 06, 2025, 05:22 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 06, 2025, 05:51 PM UTC

    We are investigating reports of elevated error rates from our US1 services.

Read the full incident report →

Minor May 6, 2025

AP1 Linksharing Intermittent Connectivity Issues

Detected by Pingoru
May 06, 2025, 04:10 PM UTC
Resolved
May 07, 2025, 12:25 AM UTC
Duration
8h 15m
Affected: AP1 - Linksharing
Timeline · 4 updates
  1. investigating May 06, 2025, 07:59 PM UTC

    We are investigating intermittent connectivity issues affecting the Linksharing service in the AP1 region.

  2. identified May 06, 2025, 08:02 PM UTC

    We have identified the issue and are implementing a fix.

  3. monitoring May 06, 2025, 08:12 PM UTC

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

  4. resolved May 07, 2025, 12:25 AM UTC

    The incident has been resolved.

Read the full incident report →

Notice April 25, 2025

Brief period of US Select Uploads interruption

Detected by Pingoru
Apr 25, 2025, 07:55 PM UTC
Resolved
Apr 25, 2025, 08:06 PM UTC
Duration
11m
Affected: US1 - Select
Timeline · 3 updates
  1. investigating Apr 25, 2025, 07:55 PM UTC

    Our monitoring detected a brief period of uploads failing for our US Select service only. Our engineering team is actively investigating.

  2. identified Apr 25, 2025, 07:59 PM UTC

    The issue has been identified and automated fail over kept the disruption minimal.

  3. resolved Apr 25, 2025, 08:06 PM UTC

    This incident has been resolved. The short-lived disruption in uploads was due to an entire zone losing connectivity for a brief period of time. US Select is designed with three zone redundancy and the service automatically excluded the affected zone. The brief upload failures were during the period during cutover. Reads were never impacted. We apologize to all who might have been affected by the disruption.

Read the full incident report →

Critical April 14, 2025

Issue with the US metadata region

Detected by Pingoru
Apr 14, 2025, 03:33 PM UTC
Resolved
Apr 14, 2025, 04:07 PM UTC
Duration
33m
Affected: US1 - APIUS1 - BillingUS1 - Web ConsoleUS1 - LinksharingUS1 - GatewayUS1 - Select
Timeline · 3 updates
  1. investigating Apr 14, 2025, 03:33 PM UTC

    We are experiencing an issue with the US1 satellite (metadata region), which is intermittently inaccessible. Our engineering team is actively investigating. We apologize to all who are affected by the disruption.

  2. monitoring Apr 14, 2025, 03:54 PM UTC

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

  3. resolved Apr 14, 2025, 04:07 PM UTC

    The issue with the US metadata region has been resolved for all affected users. We thank you for your patience while we worked on resolving the issue.

Read the full incident report →

Minor April 4, 2025

EU1: Link Sharing service degraded performance

Detected by Pingoru
Apr 04, 2025, 01:46 AM UTC
Resolved
Apr 04, 2025, 02:51 AM UTC
Duration
1h 5m
Affected: EU1 - Linksharing
Timeline · 3 updates
  1. investigating Apr 04, 2025, 01:46 AM UTC

    We are currently experiencing issues with the Link Sharing service in the Europe region. Customers may notice increased request times and error rates. Our engineering team is actively investigating. We apologize to all who are affected by the disruption.

  2. monitoring Apr 04, 2025, 02:31 AM UTC

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

  3. resolved Apr 04, 2025, 02:51 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 12, 2025

High load causing application instability

Detected by Pingoru
Mar 12, 2025, 09:10 PM UTC
Resolved
Mar 13, 2025, 12:18 AM UTC
Duration
3h 7m
Affected: US1 - APIUS1 - BillingUS1 - Web ConsoleUS1 - LinksharingUS1 - GatewayUS1 - Select
Timeline · 3 updates
  1. monitoring Mar 12, 2025, 09:10 PM UTC

    We have scaled up to meet the load and are monitoring behavior.

  2. monitoring Mar 12, 2025, 09:28 PM UTC

    We are continuing to monitor for any further issues.

  3. resolved Mar 13, 2025, 12:18 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 6, 2025

AP1: Elevated errors and degraded performance

Detected by Pingoru
Mar 06, 2025, 10:08 PM UTC
Resolved
Mar 06, 2025, 10:49 PM UTC
Duration
40m
Affected: AP1 - APIAP1 - LinksharingAP1 - Gateway
Timeline · 4 updates
  1. investigating Mar 06, 2025, 10:08 PM UTC

    We are currently investigating this issue.

  2. identified Mar 06, 2025, 10:31 PM UTC

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

  3. monitoring Mar 06, 2025, 10:48 PM UTC

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

  4. resolved Mar 06, 2025, 10:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 18, 2025

Issue with edge services connectivity affecting customers in Asia-Pacific

Detected by Pingoru
Feb 18, 2025, 03:57 PM UTC
Resolved
Feb 18, 2025, 04:17 PM UTC
Duration
20m
Affected: AP1 - LinksharingAP1 - Gateway
Timeline · 2 updates
  1. investigating Feb 18, 2025, 03:57 PM UTC

    We are experiencing an issue with edge services connectivity affecting customers in Asia-Pacific. Our engineering team is actively investigating. We apologize to all who are affected by the disruption.

  2. resolved Feb 18, 2025, 04:17 PM UTC

    This issue has been resolved for all affected users. We thank you for your patience while we worked on resolving the issue.

Read the full incident report →

Minor February 12, 2025

US1: Elevated Errors and Degraded Performance

Detected by Pingoru
Feb 12, 2025, 11:09 AM UTC
Resolved
Feb 12, 2025, 11:54 AM UTC
Duration
44m
Affected: US1 - APIUS1 - BillingUS1 - Web ConsoleUS1 - LinksharingUS1 - GatewayUS1 - Select
Timeline · 2 updates
  1. monitoring Feb 12, 2025, 11:49 AM UTC

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

  2. resolved Feb 12, 2025, 11:54 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 1, 2025

EU1: Elevated Errors and Degraded Performance

Detected by Pingoru
Feb 01, 2025, 11:23 PM UTC
Resolved
Feb 02, 2025, 12:54 AM UTC
Duration
1h 31m
Affected: EU1 - APIEU1 - BillingEU1 - Web ConsoleEU1 - LinksharingEU1 - Gateway
Timeline · 3 updates
  1. investigating Feb 01, 2025, 11:23 PM UTC

    We are investigating reports of performance impacts to one or more components of our system in the EU1 metadata region.

  2. monitoring Feb 01, 2025, 11:58 PM UTC

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

  3. resolved Feb 02, 2025, 12:54 AM UTC

    The previously identified issue has been resolved.

Read the full incident report →

Minor January 7, 2025

Intermittent listing failures

Detected by Pingoru
Jan 07, 2025, 04:13 PM UTC
Resolved
Jan 07, 2025, 04:13 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jan 07, 2025, 04:13 PM UTC

    Duration: December 19, 2024 - January 7, 2025 Customers experienced intermittent failures when attempting to list objects in storage buckets. Affected users received incomplete bucket listings, with some objects not appearing in their directory listings. This issue did not affect object storage or retrieval operations. As of January 7, 2025, full object listing functionality has been restored and validated across all regions. For customers who experienced this issue: We recommend performing a fresh listing of your buckets to confirm all objects are now visible. If you continue to observe any inconsistencies, please contact our support team. We apologize for any disruption this may have caused to your operations. We are implementing additional monitoring and failsafes to prevent similar incidents in the future.

Read the full incident report →