Resolved after 2 hours 5 minutes, affecting Admin UI and API, on December 4, 2024.
On December 3rd, SDM released a server build that added a new index to the table tracking latency between nodes. While the build succeeded on the EU and UK Control Planes, it failed on the US Control Plane. Retrying the build on the US Control Plane left the index in an invalid state, which went undetected by our migration tools. The following day, December 4th, SDM released a server build that relied on the new index. Without the index, node-to-node latency was no longer stored, and approximately three minutes later, the routing system stopped attempting multi-hop routes. This issue was limited to the US Control Plane, as the index was successfully created in the EU and UK Control Planes. StrongDM has already taken steps with internal processes to ensure that this kind of issue does not repeat in the future. Thank you for your patience and understanding.
Affected components
Update timeline
- identified Dec 04, 2024, 01:03 PM UTC
The cause of the outage is due to a change in our production db. Engineering has identified the cause and is working to remediate the issue. Updates to follow.
- monitoring Dec 04, 2024, 01:49 PM UTC
A fix has been implemented and we are monitoring the results. This should be resolved. If you are still seeing issues please reach out to support: https://help.strongdm.com/hc/en-us/requests/new
- monitoring Dec 04, 2024, 01:56 PM UTC
This issue does not appear to have impacted customers using our EU and UK Control Planes. This outage impacted the US Control Plane only.
- resolved Dec 04, 2024, 03:08 PM UTC
This incident was resolved at 13:49 UTC. An RCA will be posted here within a week.
- postmortem Dec 20, 2024, 05:20 PM UTC
On December 3rd, SDM released a server build that added a new index to the table tracking latency between nodes. While the build succeeded on the EU and UK Control Planes, it failed on the US Control Plane. Retrying the build on the US Control Plane left the index in an invalid state, which went undetected by our migration tools. The following day, December 4th, SDM released a server build that relied on the new index. Without the index, node-to-node latency was no longer stored, and approximately three minutes later, the routing system stopped attempting multi-hop routes. This issue was limited to the US Control Plane, as the index was successfully created in the EU and UK Control Planes. StrongDM has already taken steps with internal processes to ensure that this kind of issue does not repeat in the future. Thank you for your patience and understanding.
Your product runs on more than StrongDM
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services