Storj status history
Current state: operational — “All Systems Operational” per https://status.storj.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Storj incidents last?
From 14 incidents with a vendor-posted start and resolve time. Longest on record: Email sending issue on AP1 — 21.2 h (2025-08-27 21:25 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (14)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-07-04 16:39 UTC | Elevated error rates for US1 | resolved | minor | 1 h 31 min |
| 2026-07-02 20:00 UTC | Satellite - Investigating - Elevated Error Rates | resolved | critical | 4 min |
| 2026-06-03 19:21 UTC | Elevated Error Rates | resolved | major | 31 min |
| 2026-03-18 19:44 UTC | Elevated Error Rates | resolved | major | 2 h 50 min |
| 2026-03-06 10:10 UTC | Elevated error rates for US1 Select | resolved | none | 2 h 20 min |
| 2026-02-24 18:26 UTC | Increased error rates on US1 services | resolved | minor | 1 h 06 min |
| 2025-12-15 12:31 UTC | Issue with elevated error rates for uploads | resolved | none | 0 min |
| 2025-12-10 23:25 UTC | Issue with elevated error rates for uploads | resolved | critical | 26 min |
| 2025-09-18 18:41 UTC | www.storj.io returning 500 errors | resolved | none | 52 min |
| 2025-09-16 16:09 UTC | Elevated Error Rates | resolved | minor | 42 min |
| 2025-09-13 05:52 UTC | EU1 access keys becoming non-functional | postmortem | major | 2 h 30 min |
| 2025-09-03 19:44 UTC | Elevated error rates during uploads for US1 select | resolved | minor | 2 h 04 min |
| 2025-08-27 21:25 UTC | Email sending issue on AP1 | postmortem | major | 21 h 11 min |
| 2025-08-26 05:32 UTC | Elevated Error Rate | resolved | major | 1 h 08 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Storj with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"storj"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}