Test Results

Every WireGuard case we ran on 8 November 2026, with its result on an iPhone and on an Android phone: 40 of 40 cases passed on the iPhone and 35 of 35 on Android.

How these tests ran

The phones were an iPhone 12 with iOS 27.2 and a Samsung Galaxy A55 with Android 17, with the code of commit 3731b356 on the iPhone, as a Debug build, and of c1410582, which follows it, on Android, as a debug APK; the iPhone's rows of the wg-release-… cases come from a Release build of 3731b356's code, the kind TestFlight ships. The server was WireGuard in the Linux kernel 6.8 on Ubuntu 24.04, with wireguard-tools 1.0.20210914: a wg0 like the one WireGuard server sets up, on port 51821, with a peer of its own for each phone and for the files without a preshared key and with the wrong one.

How to read the results

LabelMeaning
VERIFIED — TESTED SUCCESSFULLYThe case did what its row expects: it connected and moved its traffic through the tunnel, or it was refused with the message shown.
TESTED — FAILEDThe case did not do what its row expects; the row says what happened.
NOT VERIFIEDThe case did not run on that phone.

Speeds are averages over the whole transfer on our office line. They show that traffic moved, and are not a benchmark. When both directions ran at once on the iPhone, the downloads took most of the line.

Not tested in this round

Transfers and UDP

CaseSettingsTrafficExpectediPhoneAndroid
wg-downloadthe phone's file: all IPv4 traffic, preshared key, keepalive 25 sdownload, 60 sconnectVERIFIED — TESTED SUCCESSFULLY
194.17 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 3.7 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer android1 13 s before it was asked
wg-uploadthe phone's file: all IPv4 traffic, preshared key, keepalive 25 supload, 45 sconnectVERIFIED — TESTED SUCCESSFULLY
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
up 77.92 Mbit/s
the server had a handshake with the peer ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 14.0 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer android1 13 s before it was asked
wg-full-duplexthe phone's file: all IPv4 traffic, preshared key, keepalive 25 sdownload and upload at once, 60 sconnectVERIFIED — TESTED SUCCESSFULLY
down 158.8 / up 39.18 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 10.5 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer android1 13 s before it was asked
wg-many-connectionsthe phone's file: all IPv4 traffic, preshared key, keepalive 25 s16 downloads at once, 45 sconnectVERIFIED — TESTED SUCCESSFULLY
205.46 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 26.1 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer android1 13 s before it was asked
wg-udp-probethe phone's file: all IPv4 traffic, preshared key, keepalive 25 sdownload, 15 s, and a DNS query over UDPconnectVERIFIED — TESTED SUCCESSFULLY
184.19 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer ios1 7 s before it was asked
the UDP DNS query was answered, and saw the server's address
VERIFIED — TESTED SUCCESSFULLY
transfer 3.9 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer android1 16 s before it was asked
the UDP DNS query was answered, and saw the server's address

The configuration

CaseSettingsTrafficExpectediPhoneAndroid
wg-no-pska file and peer without a preshared keydownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
190.74 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer nopsk 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 4.9 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer nopsk 13 s before it was asked
wg-no-keepalivethe phone's file without PersistentKeepalivedownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
194.52 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 3.8 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer android1 12 s before it was asked
wg-mtu-1280the phone's file with MTU = 1280download, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
183.44 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 3.8 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer android1 13 s before it was asked
wg-endpoint-ipthe phone's file with the server's address as Endpointconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer ios1 1 s before it was asked
held for 6 s
VERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer android1 4 s before it was asked
held for 6 s
wg-split-tunnelthe phone's file with AllowedIPs = 10.66.66.0/24download, 15 s, and a DNS query over UDPconnectVERIFIED — TESTED SUCCESSFULLY
194.05 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer ios1 8 s before it was asked
the UDP DNS query was answered, and saw the phone's own network
VERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer android1 18 s before it was asked
the UDP DNS query was answered, and saw the phone's own network
the server's tunnel address answered a ping: 3 packets transmitted, 3 received, 0% packet loss, time 2005ms
wg-manual-configurationthe phone's file: all IPv4 traffic, preshared key, keepalive 25 s; the same values entered under Manual Configuration instead of a fileconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer ios1 1 s before it was asked
held for 6 s
VERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer android1 4 s before it was asked
held for 6 s

Server and Port

CaseSettingsTrafficExpectediPhoneAndroid
wg-port-field-overrides-profilethe phone's file with Endpoint port 51829 (nothing listens); Port 51821connect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer ios1 1 s before it was asked
held for 6 s
VERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer android1 3 s before it was asked
held for 6 s
wg-server-field-overrides-profilethe phone's file with an Endpoint name that does not exist; Server: the server's nameconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer ios1 1 s before it was asked
held for 6 s
VERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer android1 2 s before it was asked
held for 6 s

Refusals and damaged files

CaseSettingsTrafficExpectediPhoneAndroid
wg-wrong-server-keythe phone's file with a server public key of nobodyconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 11.1 s
The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51821 may be closed.
VERIFIED — TESTED SUCCESSFULLY
The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51821 may be closed.
wg-unknown-client-keythe phone's file with a private key the server does not haveconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 11.1 s
The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51821 may be closed.
VERIFIED — TESTED SUCCESSFULLY
The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51821 may be closed.
wg-wrong-pska file whose preshared key is not the server's for its peerconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 11.1 s
The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51821 may be closed.
VERIFIED — TESTED SUCCESSFULLY
The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51821 may be closed.
wg-closed-portthe phone's file with Endpoint port 51829 (nothing listens)connect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 11.2 s
The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51829 may be closed.
VERIFIED — TESTED SUCCESSFULLY
The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51829 may be closed.
wg-unknown-hostthe phone's file with an Endpoint name that does not existconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.4 s
The WireGuard endpoint no-such-host.srp.invalid could not be resolved.
VERIFIED — TESTED SUCCESSFULLY
The WireGuard endpoint no-such-host.srp.invalid could not be resolved.
wg-bad-keythe phone's file with a damaged private keyconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.6 s
Invalid WireGuard config: a key is not valid base64 (32 bytes).
VERIFIED — TESTED SUCCESSFULLY
Invalid WireGuard config: a key is not valid base64 (32 bytes).
wg-bad-preshared-keythe phone's file with a damaged preshared keyconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.4 s
Invalid WireGuard config: the PresharedKey is not valid base64 (32 bytes).
VERIFIED — TESTED SUCCESSFULLY
Invalid WireGuard config: the PresharedKey is not valid base64 (32 bytes).
wg-retry-before-connectthe phone's file with Endpoint port 51829 (nothing listens); Port 51829; Retry Times 2connect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 31.3 s
Could not connect after 3 attempts. (The server did not answer the WireGuard handshake.)
VERIFIED — TESTED SUCCESSFULLY
Could not connect after 3 attempts. (The server did not answer the WireGuard handshake.)
wg-no-addressthe phone's file without Addressconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.4 s
Invalid WireGuard config: The config has no [Interface] Address.
VERIFIED — TESTED SUCCESSFULLY
Invalid WireGuard config: The config has no [Interface] Address.
wg-garbage-configa file with [Interface] and [Peer] but no valuesconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.5 s
Invalid WireGuard config: The config has no [Interface] PrivateKey.
VERIFIED — TESTED SUCCESSFULLY
Invalid WireGuard config: The config has no [Interface] PrivateKey.

Log levels

CaseSettingsTrafficExpectediPhoneAndroid
wg-log-normalthe phone's file: all IPv4 traffic, preshared key, keepalive 25 s; Log Level Normaldownload, 40 sconnectVERIFIED — TESTED SUCCESSFULLY
198.72 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
in the log: the session line
not in the log: a private key line, a preshared key line, the engine's private key, the engine's preshared key, the 30-second handshake and byte line
VERIFIED — TESTED SUCCESSFULLY
transfer 3.8 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
held for 40 s
in the log: the session line
not in the log: a private key line, a preshared key line, the engine's private key, the engine's preshared key, the 30-second handshake and byte line
wg-log-expertthe phone's file: all IPv4 traffic, preshared key, keepalive 25 s; Log Level Expertdownload, 40 sconnectVERIFIED — TESTED SUCCESSFULLY
208.41 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
in the log: the session line, the 30-second handshake and byte line
not in the log: a private key line, a preshared key line, the engine's private key, the engine's preshared key
VERIFIED — TESTED SUCCESSFULLY
transfer 3.7 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
held for 40 s
in the log: the session line, the 30-second handshake and byte line
not in the log: a private key line, a preshared key line, the engine's private key, the engine's preshared key
wg-log-debugthe phone's file: all IPv4 traffic, preshared key, keepalive 25 s; Log Level Debugdownload, 4 sconnectVERIFIED — TESTED SUCCESSFULLY
148.42 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
in the log: the session line, WireGuard's own lines
not in the log: a private key line, a preshared key line, the engine's private key, the engine's preshared key
VERIFIED — TESTED SUCCESSFULLY
transfer 3.9 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
in the log: the session line, WireGuard's own lines
not in the log: a private key line, a preshared key line, the engine's private key, the engine's preshared key
wg-release-log-normala file of the server; Log Level Normaldownload, 40 sconnectVERIFIED — TESTED SUCCESSFULLY
207.37 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
Release build
in the log: the session line
not in the log: a private key line, a preshared key line, the engine's private key, the engine's preshared key, the 30-second handshake and byte line
NOT VERIFIED
wg-release-log-experta file of the server; Log Level Expertdownload, 40 sconnectVERIFIED — TESTED SUCCESSFULLY
199.84 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
Release build
in the log: the session line, the 30-second handshake and byte line
not in the log: a private key line, a preshared key line, the engine's private key, the engine's preshared key
NOT VERIFIED
wg-release-log-debuga file of the server; Log Level Debugdownload, 4 sconnectVERIFIED — TESTED SUCCESSFULLY
143.04 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
Release build
in the log: the session line, WireGuard's own lines
not in the log: a private key line, a preshared key line, the engine's private key, the engine's preshared key
NOT VERIFIED
wg-release-downloada file of the serverdownload, 60 sconnectVERIFIED — TESTED SUCCESSFULLY
198.21 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
Release build
the server had a handshake with the peer iosrel 6 s before it was asked
NOT VERIFIED
wg-release-wrong-server-keya file of the server; Log Level Expertconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
Release build
ended after 11.1 s
The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51821 may be closed.
NOT VERIFIED

Sleep, a server that goes away, network changes and Retry Times

CaseSettingsTrafficExpectediPhoneAndroid
wg-life-sleep-modesthe phone's file: all IPv4 traffic, preshared key, keepalive 25 s; On Sleep Stay, Pause and Off, and Off with Auto Reconnect offconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
On Sleep Stay, Auto Reconnect on: connected again after 3.4 s
On Sleep Pause, Auto Reconnect off: connected again after 3.2 s
On Sleep Off, Auto Reconnect on: connected again after 3.3 s
On Sleep Off, Auto Reconnect off: ended after 3.4 s with: The connection was closed while the device slept.
VERIFIED — TESTED SUCCESSFULLY
stayed connected through 10 s of sleep; transfer after wake passed
paused at sleep, connected again at wake; transfer passed
closed at sleep, connected again at wake; transfer passed
ended at wake: The connection was closed while the device slept.
wg-life-server-restartthe phone's file: all IPv4 traffic, preshared key, keepalive 25 s; the server's WireGuard restarts (wg-quick); Auto Reconnect onconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
connected again after 17.0 s
VERIFIED — TESTED SUCCESSFULLY
traffic passed again 17.3 s after the restart; transfer passed
wg-life-outage-reconnectthe phone's file: all IPv4 traffic, preshared key, keepalive 25 s; the server's WireGuard stops for 8 s; Auto Reconnect onconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
connected again after 16.2 s
VERIFIED — TESTED SUCCESSFULLY
traffic passed again 25.4 s after the server stopped; transfer passed
wg-life-dead-path-reconnectsthe phone's file: all IPv4 traffic, preshared key, keepalive 25 s; every packet of the session dropped for 45 s; Auto Reconnect onconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
connected again after 48.1 s
VERIFIED — TESTED SUCCESSFULLY
noticed the dead path after 33.0 s, connected again 46.6 s after the drop began; transfer passed
wg-life-server-down-no-reconnectthe phone's file: all IPv4 traffic, preshared key, keepalive 25 s; the server's WireGuard stops for 150 s; Auto Reconnect offconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
ended after 35.1 s with: The server stopped answering: nothing came back for 30 seconds (auto reconnect is off).
VERIFIED — TESTED SUCCESSFULLY
ended 37.7 s after the server stopped with: The server stopped answering: nothing came back for 30 seconds (auto reconnect is off).
wg-life-retry-exhaustedthe phone's file: all IPv4 traffic, preshared key, keepalive 25 s; the server's WireGuard stops for 120 s; Auto Reconnect on; Retry Times 2connect onlyconnectVERIFIED — TESTED SUCCESSFULLY
ended after 55.3 s with: Could not reconnect after 2 attempts. (The server did not answer the WireGuard handshake.)
VERIFIED — TESTED SUCCESSFULLY
ended 58.2 s after the server stopped with: Could not reconnect after 2 attempts. (The server did not answer the WireGuard handshake.)
wg-life-path-switchthe phone's file: all IPv4 traffic, preshared key, keepalive 25 s; the connection moved to the current networkconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
connected again after 0.3 s
VERIFIED — TESTED SUCCESSFULLY
followed the network to mobile data and back to Wi-Fi (2 changes); on mobile data 5 of 5 pings to the server's tunnel address were answered; transfer passed

The server as the guide sets it up

CaseSettingsTrafficExpectediPhoneAndroid
wg-guide-udpthe guide's phone1.confdownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
197.29 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer phone1 26 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 3.9 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer phone1 20 s before it was asked
wg-guide-removedthe guide's phone2.conf, phone2 removed as part 5 saysconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 11.1 s
The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51821 may be closed.
VERIFIED — TESTED SUCCESSFULLY
The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51821 may be closed.