Storj had 10 outages in the last 2 years totaling 33h 26m of downtime — averaging 0.4 incidents per month.
There were 10 Storj outages since July 8, 2025 totaling 33h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are investigating reports of elevated error rates from our API services.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We have applied a fix for the previously mentioned performance impact and are continuing to monitor the system.
The previously identified issue affecting performance has been resolved.
We are investigating the issue
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
This incident has been resolved.
We have been alerted to an issue causing access keys in the EU1 region to stop working.
We are continuing to investigate this issue.
This incident has been resolved.
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.
We are investigating reports of elevated error rates during uploads
The issue has been identified and a fix is being applied
A fix has been implemented and we are monitoring the results.
This incident has been resolved
We have identified the cause of the elevated API error rate and will be applying a fix shortly.
A fix has been applied and we will continue to monitor the system.
The previously identified issue has been resolved.