SafeDep Cloud Outage History
3 incidents recorded over the last 365 days, 3 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 SafeDep Cloud Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 21, 2026 | Endpoints List API TimeoutNo list API timeout observed during the monitoring period. | 1h 1m | Resolved |
| Jun 4, 2026 | AWS RDS Internal Service OutageFully restored RDS and MemoryDB post outage. | 4h 36m | Resolved |
| Mar 17, 2026 | SafeDep App Authentication FailureResolved by restoring API Gateway version. | 14 min | 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 SafeDep Cloud 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 SafeDep Cloud 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 SafeDep Cloud 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 SafeDep Cloud outage in this window ran 4h 36m, against a mean recovery of 1h 57m. If you depend on SafeDep Cloud 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.