- Level
- confirmed
- Worst impact
- Degraded
- Components
- Authentication - Enterprise, Public API, Admin Console, Authorization, Connector Heartbeat
- Down Index
- 19of 100
What to do
Check whether you use Twingate Authentication - Enterprise, Public API, Admin Console, Authorization and 1 more. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 20m it lasted.
Anything that failed between 2023-08-19 08:01 UTC and 2023-08-19 08:21 UTC may need a replay.Subscribe to Twingate's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=twingate works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Twingate 4
- investigating
We are seeing issues with Twingate service and investigating.
provider
- investigating
We are continuing to investigate this issue.
provider
- resolved
This incident has been resolved. We'll publish RCA as soon as we can.
provider
- postmortem
**Summary** On August 19 at 7:51 AM UTC, Twingate received alerts of issues with the login services. Within a few minutes, the Twingate engineering team began investigating. The team quickly identified that our backend was seeing excessive timeouts from a 3rd-party API, preventing it from being able to process other requests such as authentication. After some initial fixes were unsuccessful, Twingate contacted the 3rd party and also disabled support for real-time updates that make use of these specific 3rd-party API calls. As a result, the issues started resolving at 8:10 AM UTC. Most of the services recovered quickly and full resolution occurred at 8:15 AM UTC. The vendor later confirmed and fixed the issue, and Twingate re-enabled the real-time update feature shortly after on the same day, August 19. **Root cause** The Twingate backend was exhausted due to timeouts from a 3rd-party API. **Post-incident Analysis** Twingate had already separated out most services to their own deployments, allowing those services to function throughout the incident. Therefore, only some users that needed to authenticate or re-authenticate were affected; any user that had authenticated prior to the incident was not impacted. Analysis of logs post-incident showed that the incident started at 7:49 AM UTC and fully recovered at 8:15 AM UTC. **Corrective actions** Short Term: * Separate Authentication and real-time services to their own deployments - COMPLETED Medium / Long Term: * Reevaluate and optimize timeout values for various backend and 3rd party services * Simplify the internal Twingate process for enabling and disabling features
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-a18f6c293f
Is Twingate still down?
No, this incident was resolved 2023-08-19 08:21 UTC. For Twingate's live state, see https://down.guide/twingate.
How long did it last?
20m, from 2023-08-19 08:01 UTC to 2023-08-19 08:21 UTC, by the times Twingate posted.
What was affected?
Twingate named Authentication - Enterprise, Public API, Admin Console, Authorization and 1 more.
What caused it?
Twingate hasn't published a root cause. If it does, it shows here.
Where does this come from?
Twingate's official status page, https://status.twingate.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.