Guardsquare Outage History
12 incidents recorded over the last 365 days, 12 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 Guardsquare Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | Preventive measures against (CVE-2026-109618 & CVE-2026-109619)**Official Security Advisory** Upon learning of the vulnerabilities we immediately identified the external facing services within our infrastructure that were potentially vulnerable to CVE-2026-109618 &… | 3h 55m | Resolved |
| Sep 1, 2026 | Monitoring api intermittently errors or times outWe've gotten confirmation from our cloud vendor that this issue can only happen in the 17 hour period around the end of the month. In addition we will take measures to prevent this issue on our side as well. | 3h 2m | Resolved |
| Aug 20, 2026 | Increased attestation token issuance error rateThe issue is fully resolved. We will reach out to affected customers. | -649 min | Resolved |
| Jul 27, 2026 | Detection reasons on threat type page showing incorrect dataThe aggregated detection reasons breakdown on threat type page now shows the correct detections reasons again. This is true for both newly ingested events and events that were already ingested. | 49h 26m | Resolved |
| May 3, 2026 | TLS certificate issuesThe issue is fully resolved now. | 20h 47m | Resolved |
| Apr 21, 2026 | Guardsquare platform services were unavailableServices are operational again. | -105 min | Resolved |
| Apr 3, 2026 | Increased webhook delivery failure rateThe issue is fully resolved. Automatically deactivated webhooks have been re-enabled. | 1h 12m | Resolved |
| Mar 12, 2026 | Increased error rate in loading data on the dashboardIssue is fully resolved. | 20 min | Resolved |
| Jan 27, 2026 | Increased error rates when ingesting threat eventsThreat event ingestion is fully operational again. | -19 min | Resolved |
| Jan 21, 2026 | Issue with uploading of application scans via the browserUploads for application scans via the browser are working as expected again. | -1521 min | Resolved |
| Jan 13, 2026 | Platform dashboard briefly unavailablePlatform dashboard available again. | -346 min | Resolved |
| Dec 10, 2025 | Threat monitoring dashboard showing intermittend data loading errorsThe issue is fully resolved. | -35 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 Guardsquare 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 Guardsquare 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 Guardsquare 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 Guardsquare outage in this window ran 2d 1h, against a mean recovery of 13h 7m. If you depend on Guardsquare 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.