UpGuard CyberRisk Outage History
6 incidents recorded over the last 365 days, 5 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 UpGuard CyberRisk Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 23, 2026 | A database outage is causing the platform to be unavailableThis incident is now resolved. The database ran out of connections due to a lock being held as part of the fortnightly release. Changes to the release process are being implemented to remove the risk of this happening… | 46 min | Resolved |
| Aug 10, 2026 | An Issue has been identified regarding a disruption to login services.This incident has now been resolved | 0 min | Resolved |
| Aug 10, 2026 | An Issue has been identified regarding a disruption to login services.The incident is now resolved. Login services have been restored. | 11 min | Resolved |
| Jul 8, 2026 | Disruption to notification emailsThe incident is now resolved. All delayed notifications have now been sent. | 7h 18m | Resolved |
| May 9, 2026 | Database maintenanceThe scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Mar 6, 2026 | We are experiencing an issue where the platform will be offline for a period of time.Our engineers have identified the issue, and it's been fully resolved. The platform is fully functional. | 22 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 UpGuard CyberRisk 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 UpGuard CyberRisk 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 UpGuard CyberRisk 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 UpGuard CyberRisk outage in this window ran 7h 18m, against a mean recovery of 2h 6m. If you depend on UpGuard CyberRisk 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.