Digistore24 Outage History
6 incidents recorded over the last 365 days, 4 of them resolved, 1 still open. 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 Digistore24 Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 17, 2026 | Digistore24: Scheduled MaintenanceWe will be undergoing scheduled maintenance during this time. We are going to update core elements of our infrastructure to ensure and improve stability and uptime of all our applications. We do expect a downtime of… | 1h 0m | Scheduled |
| Oct 23, 2026 | Digibiz24 has been discontinuedAs announced earlier, Digibiz24 was officially sunset on on 30.06.2026 and is now permanently shut down and no longer available starting 23.10.2026. What this means: * You can no longer log in to the editor, the course… | — | Investigating |
| Aug 28, 2026 | Service disruption - Processing purchases and transactionsA database issue caused errors when processing purchases and transactions from 08/28/2026 09:00 am until 10:30 a.m. The issue is solved, processing purchases and transactions is back to normal. | -135 min | Resolved |
| Aug 13, 2026 | Service disruption — blank pages and 503 errorsOn Sunday, August 9 between 02:15–03:45 CEST, parts of the Digistore24 platform were unavailable. Affected users saw blank pages or HTTP 503 errors. The incident was triggered by a defect in an internal refresh… | -6062 min | Resolved |
| May 18, 2026 | Digistore24 Currently UnavailableThe service is fully functional and back to operation | 10 min | Resolved |
| Feb 13, 2026 | Digistore currently unavailableThe issue has been resolved. | 1h 28m | 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 Digistore24 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 Digistore24 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 Digistore24 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 Digistore24 outage in this window ran 1h 28m, against a mean recovery of 53 min. If you depend on Digistore24 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.