Tresorit status history
Current state: operational — “All Systems Operational” per https://status.tresorit.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Tresorit incidents last?
From 4 incidents with a vendor-posted start and resolve time. Longest on record: eSign issues — 13.1 h (2026-04-01 22:00 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 (4)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-04-01 22:00 UTC | eSign issues | resolved | minor | 13 h 03 min |
| 2025-12-17 19:45 UTC | tresorit.com website is down | resolved | critical | 1 h 14 min |
| 2025-10-29 16:00 UTC | Website connectivity issues | resolved | critical | 3 h 20 min |
| 2025-10-09 11:34 UTC | Partial outage affecting the web interface and the signups | resolved | minor | 4 h 40 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 Tresorit with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"tresorit"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
