Safe Software Outage History
2 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 Safe Software Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | FME Community file uploads disabledAll remaining functionality has been restored to the FME Community. Please reach out to the Support Team if you continue to experience any challenges in the FME Community. | 124h 14m | Resolved |
| Apr 27, 2026 | AI responses not availableThis incident is resolved, but we continue to monitor the status of our AI vendor. | 26h 0m | 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 Safe Software 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 Safe Software 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 Safe Software 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 Safe Software outage in this window ran 5d 4h, against a mean recovery of 3d 3h. If you depend on Safe Software 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.