Syncthing Relay

Public relay to help file synchronization between Syncthing devices when direct peer-to-peer connection is not possible.

Syncthing Relay acts as a relay point for Syncthing devices that cannot always reach each other directly, for example because of NAT, firewalls or restrictive networks. It then allows synchronization traffic to pass through a public relay.

It does not replace Syncthing itself: it complements peer-to-peer synchronization when a direct connection is unavailable.

• Help devices synchronize when direct connection fails.
• Keep using decentralized synchronization in restrictive networks.
• Avoid hosting a relay yourself for occasional needs.
• Improve connectivity between devices behind NAT or firewalls.

• Syncthing first tries to connect devices directly.
• If direct connection is not possible, a relay can transport encrypted synchronization traffic.
• The relay helps connectivity but does not manage your files or devices.
• Your Syncthing configuration remains on your own devices.

• Data exchanged through the relay stays end-to-end encrypted between Syncthing devices.
• The relay cannot inspect the content of files passed through it.
• However, a relay does see some metadata required to operate, in particular device IDs and IP addresses used for the connection.
• The relay operator can also see the volume of traffic going through the service.
• A public relay improves connectivity but does not replace good network configuration or a direct connection when one is available.

• Synchronize devices behind restrictive NAT.
• Keep a file sync setup working while traveling.
• Improve connectivity between remote devices.
• Use a public relay without operating one yourself.

Service: syncthing.hostux.net