Softwareheritage Outage History
3 incidents recorded over the last 365 days, 2 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 Softwareheritage Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 12, 2026 | Incident on our object storageWe have identified connection issues with our object storage Services, especially those reading from the archive, are much slower than usual. No data is lost, we are working on a fix. We are sorry for the… | 17h 16m | Resolved |
| Oct 8, 2026 | Authentication Stack UpgradeScheduled Maintenance | 2h 0m | Scheduled |
| Sep 8, 2026 | Hosted site www.softwareheritage.org is downThe site hosted by by our host provider are not responding [1] Currently investigating the issue. [1] https://www.softwareheritage.org [2] http://www.sourcecode-exhibition.softwareheritage.org/ | 25h 48m | 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 Softwareheritage 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 Softwareheritage 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 Softwareheritage 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 Softwareheritage outage in this window ran 1d 1h, against a mean recovery of 15h 1m. If you depend on Softwareheritage 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.