Syncthing community relay pool
- Free allowance
- No quota at all — relay operators cap themselves with -global-rate (commonly ~20 Mbps in and out).
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- anonymousno card, no phone
- Binding limit
- per-ip-shaping20 Mbps
- Evidence
- reported4 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | No quota at all — relay operators cap themselves with -global-rate (commonly ~20 Mbps in and out). The pool is anonymous and unvetted. unit unlimited; metered on unstated |
|---|---|
| Price | none stated |
| Limits |
Per-relay bandwidth set by the operator; sessions per client and per relay are limited. Relays can vanish without notice. |
| Identity | anonymous anonymous |
| Egress | Free. Paid for by whoever runs each relay, not by a company with a budget. |
| Per-object cap | not stated |
| Retention | not stated |
| Interface | unknown relay:// protocol on 22067; the pool is a JSON endpoint. |
| Tooling | strelaysrv; Syncthing's own relay selection. |
| Composes with | Relay is only used until a direct connection is established; Syncthing then switches to direct and the relay carries nothing. |
| Reliability | The pool endpoint returns dozens of relay://IP:22067 entries with self-signed device IDs. No accounting means no sustainability, but also no gate. |
| Parsed numbers |
|
Evidence 4
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | relays.syncthing.net/endpoint | literal JSON list of relay:// URLs with IDs |
| 2026-10-21 | docs.syncthing.net/users/strelaysrv | 'Anyone can run a relay server, and it will automatically join the relay pool' |
| 2026-10-21 | docs.syncthing.net/users/relaying.html | traffic is bounced via a relay only when a direct connection is impossible |
| 2026-10-21 | relays.syncthing.net/ | 'The relays listed on this page are not managed or vetted by the Syncthing project' |
Unknown values 5
- interface: the access interface was not established
- per object cap notes: the field may be stated in a source that was not read
- per object cap stated: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read
- retention stated: the field may be stated in a source that was not read