Major incident
Guardsquare: Detection reasons on threat type page showing incorrect data
Jul 27, 2026, 07:58 UTC
started
09:24 UTC
resolved July 29, 2026
2 days 1 h
duration
Current status of Guardsquare: Operational — live Guardsquare status
Timeline
- Jul 27, 2026, 07:58 UTCinvestigatingThe aggregated detection reasons breakdown on threat type page is showing incorrect data. The correct detection reason for individual detections is available on the threat details and device pages.
- Jul 27, 2026, 09:00 UTCidentifiedWe've identified the issue and are working a solution. No data was lost during this incident.
- Jul 29, 2026, 09:24 UTCresolvedThe 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.
Updates as published by Guardsquare.
Other services with incidents at the same time
- Gong 08:46 UTC · Gong Application Sign-in Issues
- BrowserStack 08:02 UTC · Live is facing issues
More Guardsquare incidents
- October 21, 2026 Preventive measures against (CVE-2026-109618 & CVE-2026-109619)
- September 1, 2026 Monitoring api intermittently errors or times out
- August 20, 2026 Increased attestation token issuance error rate
- May 3, 2026 TLS certificate issues
- April 21, 2026 Guardsquare platform services were unavailable
- April 3, 2026 Increased webhook delivery failure rate