StrongDM Outage History
6 incidents recorded over the last 365 days, 6 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 StrongDM Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Feb 18, 2026 | Slack Integration Token Mass Revocation IncidentWe’ve identified that yesterday’s incident also impacted Slack Integrations. Specifically, token refresh requests were timing out, which caused some Slack connections to disconnect. Latency has improved following the… | 0 min | Resolved |
| Feb 17, 2026 | Increased Latency and Intermittent Timeouts in US Control Plane (Admin UI & API)On February 17, 2026, some customers experienced elevated latency in the US Control Plane due to a relatively small number of specific query log requests. These specific requests were searching for a very small subset… | 7h 45m | Resolved |
| Jan 28, 2026 | Investigating – AWS Connection Issues with AWS Secret StoresTIMELINE * On January 14, 2026 at 4:59pm PDT, a pull request was merged which changed the way the relays obtain credentials from AWS. We migrated to Go AWS SDK v2 and our migration was missing container credential… | 24h 49m | Resolved |
| Jan 15, 2026 | StrongDM Slack Integration is experiencing issues currently.This issue has been resolved. The cause: The SKU of certain customers was miscalculated by the Slack integration, resulting in affected customers losing functionality. A code change will be pushed out to make fix this… | 35 min | Resolved |
| Dec 12, 2025 | Service Degradation on US Control Plane.**Summary** On December 11th 2025, StrongDM experienced a service degradation affecting the US Control Plane. The issue was caused by resource exhaustion from an internal monitoring component and lasted approximately… | 1h 22m | Resolved |
| Nov 24, 2025 | Reporting Refresh delay in Admin UI.Our orchestration platform has been experiencing intermittent errors and we are actively working to fix the issues as quickly as possible. At this time the issue has been resolved and reporting is working correctly. | 0 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 StrongDM 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 StrongDM 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 StrongDM 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 StrongDM outage in this window ran 1d, against a mean recovery of 5h 45m. If you depend on StrongDM 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.