Jottacloud Public Outage History
2 incidents recorded over the last 365 days, 1 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 Jottacloud Public Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 13, 2026 | Service disruption – some users unable to reach JottacloudThis incident has been resolved. Heightened monitoring following DDoS attack. | 46h 18m | Resolved |
| May 27, 2026 | Storage maintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
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 Jottacloud Public 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 Jottacloud Public 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 Jottacloud Public 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 Jottacloud Public outage in this window ran 1d 22h, against a mean recovery of 1d. If you depend on Jottacloud Public 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.