At around 09:50pm CET the upstream VPN provider had issues:

Mar 20 20:53:52 flood mullvad-daemon[633]: [talpidcore::tunnelstatemachine::connectingstate][DEBUG] WireGuard tunnel timed out Mar 20 20:53:52 flood mullvad-daemon[633]: [talpidcore::tunnelstatemachine::connectingstate][DEBUG] Tunnel monitor exited with block reason: None Mar 20 20:53:52 flood mullvad-daemon[633]: [mullvadrelayselector][INFO] Selected relay fr-par-wg-004 at 193.32.126.69 Mar 20 20:53:52 flood mullvad-daemon[633]: [mullvadrelayselector][DEBUG] Relay matched on highest preference for retry attempt 0 Mar 20 20:53:52 flood mullvad-daemon[633]: [mullvad_daemon::tunnel][DEBUG] Same IP is NOT being used

Unfortunately the automatic recovery did not work as expected, instead looping with:

Mar 20 20:54:04 flood mullvad-daemon[633]: [talpidcore::tunnelstatemachine::connectingstate][DEBUG] WireGuard tunnel timed out Mar 20 20:54:04 flood mullvad-daemon[633]: [talpidcore::tunnelstatemachine::connectingstate][DEBUG] The tunnel disconnected unexpectedly Mar 20 20:54:04 flood mullvad-daemon[633]: [talpidcore::tunnelstatemachine::connectingstate][DEBUG] Tunnel monitor exited with block reason: None

The machine was rebooted and service restored. There will be followup work to make this more resilient, and to alert via OpsGenie for quicker response through work in the Sentinel.

Only downloading was affected.