Vendor Status Watch

← all vendors

Storj status history

Current state: operational — “All Systems Operational” per https://status.storj.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days
2incidents, last 90 days
14incidents on record
Incidents per week, last 12 weeks:

How long do Storj incidents last?

67 minmedian incident duration14 measured
2.8 h90th percentile1 in 10 ran longer
68 minmedian, major/critical only7 incidents

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)

StartedIncidentStatusImpactDuration
2026-07-04 16:39 UTCElevated error rates for US1resolvedminor1 h 31 min
2026-07-02 20:00 UTCSatellite - Investigating - Elevated Error Ratesresolvedcritical4 min
2026-06-03 19:21 UTCElevated Error Ratesresolvedmajor31 min
2026-03-18 19:44 UTCElevated Error Ratesresolvedmajor2 h 50 min
2026-03-06 10:10 UTCElevated error rates for US1 Selectresolvednone2 h 20 min
2026-02-24 18:26 UTCIncreased error rates on US1 servicesresolvedminor1 h 06 min
2025-12-15 12:31 UTCIssue with elevated error rates for uploadsresolvednone0 min
2025-12-10 23:25 UTCIssue with elevated error rates for uploadsresolvedcritical26 min
2025-09-18 18:41 UTCwww.storj.io returning 500 errorsresolvednone52 min
2025-09-16 16:09 UTCElevated Error Ratesresolvedminor42 min
2025-09-13 05:52 UTCEU1 access keys becoming non-functionalpostmortemmajor2 h 30 min
2025-09-03 19:44 UTCElevated error rates during uploads for US1 selectresolvedminor2 h 04 min
2025-08-27 21:25 UTCEmail sending issue on AP1postmortemmajor21 h 11 min
2025-08-26 05:32 UTCElevated Error Rateresolvedmajor1 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
}