Xplenty SSH Tunnel Status

Find the latest information on your SSH tunnel availability below.


Status Refreshed December 19, 2025 at 02:18am UTC

Your tunnel is healthy

Logs

autossh -M 0 -f -N -R 49422:ec2-52-192-145-188.ap-northeast-1.compute.amazonaws.com:5432 sshtunnel@virginia-tunnel.xplenty.com -g -i /app/.ssh/id_rsa -p 50683 -o "ExitOnForwardFailure yes" -o "ServerAliveInterval 10" -o "ServerAliveCountMax 1" -o "UserKnownHostsFile /app/.ssh/known_hosts"
2025/12/18 06:10:07 autossh[21]: port set to 0, monitoring disabled
2025/12/18 06:10:07 autossh[22]: starting ssh (count 1)
2025/12/18 06:10:07 autossh[22]: ssh child pid is 25
2025/12/18 06:10:09 autossh[30]: port set to 0, monitoring disabled
2025/12/18 06:10:09 autossh[31]: starting ssh (count 1)
2025/12/18 06:10:09 autossh[31]: ssh child pid is 32
2025/12/18 06:10:10 autossh[31]: ssh exited with error status 255; restarting ssh
2025/12/18 06:10:10 autossh[31]: starting ssh (count 2)
2025/12/18 06:10:10 autossh[31]: ssh child pid is 40
2025/12/18 06:10:12 autossh[31]: ssh exited with error status 255; restarting ssh
2025/12/18 06:10:12 autossh[31]: starting ssh (count 3)
2025/12/18 06:10:12 autossh[31]: ssh child pid is 41
2025/12/18 06:10:14 autossh[31]: ssh exited with error status 255; restarting ssh
2025/12/18 06:10:14 autossh[31]: starting ssh (count 4)
2025/12/18 06:10:14 autossh[31]: ssh child pid is 42
2025/12/18 06:10:16 autossh[31]: ssh exited with error status 255; restarting ssh
2025/12/18 06:10:16 autossh[31]: starting ssh (count 5)
2025/12/18 06:10:16 autossh[31]: ssh child pid is 43
2025/12/18 06:10:17 autossh[31]: ssh exited with error status 255; restarting ssh
2025/12/18 06:10:17 autossh[31]: starting ssh (count 6)
2025/12/18 06:10:17 autossh[31]: ssh child pid is 44
2025/12/18 06:10:19 autossh[31]: ssh exited with error status 255; restarting ssh
2025/12/18 06:10:21 autossh[31]: starting ssh (count 7)
2025/12/18 06:10:21 autossh[31]: ssh child pid is 45
2025/12/18 06:10:23 autossh[31]: ssh exited with error status 255; restarting ssh
2025/12/18 06:10:31 autossh[31]: starting ssh (count 8)
2025/12/18 06:10:31 autossh[31]: ssh child pid is 46
2025/12/18 06:10:33 autossh[31]: ssh exited with error status 255; restarting ssh
2025/12/18 06:10:51 autossh[31]: starting ssh (count 9)
2025/12/18 06:10:51 autossh[31]: ssh child pid is 47
2025/12/18 06:10:52 autossh[31]: ssh exited with error status 255; restarting ssh
2025/12/18 06:11:24 autossh[31]: starting ssh (count 10)
2025/12/18 06:11:24 autossh[31]: ssh child pid is 48
2025/12/18 06:11:26 autossh[31]: ssh exited with error status 255; restarting ssh
2025/12/18 06:12:16 autossh[31]: starting ssh (count 11)
2025/12/18 06:12:16 autossh[31]: ssh child pid is 49
2025/12/18 06:12:18 autossh[31]: ssh exited with error status 255; restarting ssh
2025/12/18 06:13:30 autossh[31]: starting ssh (count 12)
2025/12/18 06:13:30 autossh[31]: ssh child pid is 50
2025/12/18 06:13:32 autossh[31]: ssh exited with error status 255; restarting ssh
2025/12/18 06:15:10 autossh[31]: starting ssh (count 13)
2025/12/18 06:15:10 autossh[31]: ssh child pid is 51
2025/12/18 06:15:12 autossh[31]: ssh exited with error status 255; restarting ssh
2025/12/18 06:17:20 autossh[31]: starting ssh (count 14)
2025/12/18 06:17:20 autossh[31]: ssh child pid is 54
2025/12/18 06:17:21 autossh[31]: ssh exited with error status 255; restarting ssh
2025/12/18 06:20:03 autossh[31]: starting ssh (count 15)
2025/12/18 06:20:03 autossh[31]: ssh child pid is 55
2025/12/18 06:20:05 autossh[31]: ssh exited with error status 255; restarting ssh