[Twingate Client] Resources Stop Responding While the Client Shows Connected

Applicable to

Twingate Component: Client, with Connector version 1.93.0 or later

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.

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

For administrators: affected users connect through Connectors running version 1.93.0 or later.

Cause

When a device briefly loses network connectivity, for example during sleep or when switching Wi-Fi networks, the connection between the Client and the Connector can resume in a state where traffic is no longer delivered reliably. This affects only connections that pass through a Twingate Relay. Peer-to-peer connections are not affected.

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 after a later network interruption. If it occurs frequently or affects many users, contact Twingate Support and include a Client log upload and the approximate time the issue started.