Twingate experienced a major incident on April 30, 2024 affecting Authentication - Enterprise, lasting 35m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 30, 2024, 06:03 PM UTC
We are currently investigating this issue.
- investigating Apr 30, 2024, 06:03 PM UTC
We are continuing to investigate this issue.
- investigating Apr 30, 2024, 06:05 PM UTC
A software rollout has broken the logins with Github. We are working on rolling out a hotfix.
- resolved Apr 30, 2024, 06:38 PM UTC
We have successfully rollout the HotFix for the issue with Github logins.
- postmortem May 03, 2024, 07:00 PM UTC
**Components impacted** Control Plane: Authentication **Summary** On April 30, 2024, between 15:44 and 18:38 UTC, users were unable to login to Twingate through GitHub. The Twingate Engineering team investigated the issue upon receiving support communications and found that logins with other identity providers were functioning normally, but GitHub logins were not working as expected. The problem was traced back to a software rollout that had inadvertently impacted GitHub logins. Engineering was able to create a fix and roll it out at 18:38 UTC, which restored the GitHub logins to its normal functionality. The team is investigating better ways to identify and prevent these types of issues from reaching production and address them as quickly as possible if they ever arise again. **Root cause** A recent package upgrade introduced a bug that impacted Twingate logins via GitHub. **Corrective actions** Short-term: * Increase our testing coverage to allow early detection of login issues for all supported identity providers in all environments. This will aid in early detection when software is deployed to lower, non-production environments. * Improve alerting for login issues.