// troubleshooting guide · tailscale

Tailscale Slow? Connection Relayed via DERP

Status
Workaround available
platforms:
Windows, macOS, Linux, iOS, Android
updated:
November 16, 2026
reports:
5
Method
how we research
Share

RUNBOOK · tailscale/slow5 FIXES

// quick answer

Tailscale is slow mostly when a connection goes through a DERP relay instead of directly between devices. Confirm with 'tailscale status' or 'tailscale ping', then allow UDP 41641, enable UPnP/NAT-PMP on your router, or run a peer relay.

Most likely fix: Check whether the connection is direct

How to fix it

// try these in order, the most common fix is first

  1. FIX 1Check whether the connection is direct

    1. 01Run 'tailscale status' and look at the peer's line for 'direct', 'relay' or 'peer-relay'
    2. 02Run 'tailscale ping <device>' and ignore the first replies; later replies should say 'via <IP>:<port>' for a direct path
    3. 03Run 'tailscale netcheck' on both devices to see UDP support, port mapping and nearest DERP latency
    Did this fix it?
  2. FIX 2Allow UDP 41641

    1. 01Allow inbound and return UDP on port 41641 in the device firewall and any cloud security group
    2. 02If you need another port, start tailscaled with --port=<number> (on Linux set it in /etc/default/tailscaled)
    3. 03Re-run 'tailscale ping' to see if it switches to direct
    Did this fix it?
  3. FIX 3Enable UPnP or NAT-PMP on your router

    1. 01Open your router's admin page
    2. 02Turn on UPnP or NAT-PMP so Tailscale gets predictable, reachable ports
    3. 03Reconnect Tailscale and check 'tailscale status' again
    Did this fix it?
  4. FIX 4Give cloud machines a public IP

    1. 01Attach a public (static or dynamic) IP to the cloud instance running Tailscale instead of routing it through a NAT gateway
    Did this fix it?
  5. FIX 5Run a peer relay

    1. 01If you can't change the network, deploy a Tailscale peer relay inside your own infrastructure (both ends on a recent client)
    2. 02Peer relays are generally faster than DERP and avoid cloud gateway egress
    Did this fix it?

SANDBOX · tailscale RUNS IN YOUR BROWSER

Try it: connect to a server and see what websites see

A hands-on Tailscale-style sandbox, including the spots where users get stuck. See where problems like this one start. 1-2 minutes, nothing is saved.

Symptoms

High latency and low throughput between two tailnet devices; 'tailscale status' shows 'relay' instead of 'direct'; 'tailscale ping' replies 'via DERP(...)'.

Why it happens

  • C-01Outbound or return UDP blocked by a firewall or ISP
  • C-02Both devices behind hard NAT or CGNAT
  • C-03Cloud NAT gateways (for example on AWS) that behave like hard NAT
  • C-04Network conditions changed and a direct path fell back to a relay
  • C-05DERP servers cap throughput for fairness

// this guide also covers

  • why is tailscale so slow
  • tailscale slow speed
  • tailscale relay instead of direct
  • tailscale derp slow
  • tailscale direct connection not established

Still not working?

If Tailscale keeps failing, you're not alone. See every Tailscale problem users report or the alternatives people switch to.

Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.

Talk to us

Watch Tailscale Get an email when its price changes, it has an outage, or we publish a new fix. No spam.

Fixed it? Share this guide

The same problem in other apps

All not loading, error messages & connection guides →

Other Tailscale errors

All 13 Tailscale errors and fixes →