Storj DCS Outage History
13 incidents recorded over the last 365 days, 9 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Storj DCS Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 20, 2026 | Intermittent errors on US select networkThis incident has been resolved. | 2h 34m | Resolved |
| Sep 24, 2026 | Network maintenance on SelectUpstream provider maintenance is done. | 96h 0m | Scheduled |
| Jul 8, 2026 | Planned maintenance of US1 satelliteThe scheduled maintenance has been completed. | 45 min | Scheduled |
| Jul 4, 2026 | Elevated error rates for US1The previously identified issue affecting performance has been resolved. | 1h 31m | Resolved |
| Jul 2, 2026 | Satellite - Investigating - Elevated Error RatesThis incident has been resolved. | 4 min | Resolved |
| Jul 2, 2026 | Planned maintenance of EU1 satelliteThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jun 29, 2026 | Planned maintenance of AP1 satelliteThe previously identified issue affecting performance has been resolved. | 1h 0m | Scheduled |
| Jun 3, 2026 | Elevated Error RatesThis incident has been resolved. | 31 min | Resolved |
| Mar 18, 2026 | Elevated Error RatesThis incident has been resolved. | 2h 50m | Resolved |
| Mar 6, 2026 | Elevated error rates for US1 SelectThe previously identified issue affecting performance has been resolved. | 2h 20m | Resolved |
| Feb 24, 2026 | Increased error rates on US1 servicesThis incident has been resolved. | 1h 6m | Resolved |
| Dec 15, 2025 | Issue with elevated error rates for uploadsThe 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. | 0 min | Resolved |
| Dec 10, 2025 | Issue with elevated error rates for uploadsThe 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. We thank you for your patience while we worked… | 26 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Storj DCS incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Storj DCS Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Storj DCS acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Storj DCS outage in this window ran 4d, against a mean recovery of 8h 28m. If you depend on Storj DCS in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.