[Twingate Client] Resources Stop Responding While the Client Shows Connected
Last updated: November 2, 2026
Applicable to
Twingate Component: Client and Connector
Platform: Reported on macOS
Overview
Twingate Resources may stop responding while the Twingate Client continues to show Connected. No error is displayed, and access is restored as soon as the Client is disconnected and reconnected.
Twingate is aware of this issue and is actively investigating. This article will be updated as more information becomes available.
Symptoms
Resources stop loading, hang, or time out, with no error from the Twingate Client. This can affect web applications, git operations, and internal services
The Client shows Connected throughout
Websites and applications that are not Twingate Resources continue to work normally
The issue does not clear on its own and persists until the Client is reconnected or the device is restarted
It occurs intermittently and typically affects individual users rather than all users at once
Disconnecting and reconnecting the Client restores access immediately. If this resolves the issue, it is the most likely cause
Cause
The cause is under investigation. In the cases reported so far, the affected connections pass through a Twingate Relay.
Workarounds and Recommendations
Disconnect the Twingate Client, then connect it again. A full quit of the application is not required. Access to Resources is restored once the Client reconnects.
The issue can recur. If it occurs frequently or affects many users, contact Twingate Support and include a Client log upload and the approximate time the issue started.