Xplenty SSH Tunnel Status

Find the latest information on your SSH tunnel availability below.


Status Refreshed February 17, 2026 at 02:36am 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"
2026/02/16 02:34:28 autossh[24]: port set to 0, monitoring disabled
2026/02/16 02:34:28 autossh[25]: starting ssh (count 1)
2026/02/16 02:34:28 autossh[25]: ssh child pid is 27
2026/02/16 02:34:30 autossh[33]: port set to 0, monitoring disabled
2026/02/16 02:34:30 autossh[34]: starting ssh (count 1)
2026/02/16 02:34:30 autossh[34]: ssh child pid is 35
2026/02/16 02:34:32 autossh[34]: ssh exited with error status 255; restarting ssh
2026/02/16 02:34:32 autossh[34]: starting ssh (count 2)
2026/02/16 02:34:32 autossh[34]: ssh child pid is 43
2026/02/16 02:34:33 autossh[34]: ssh exited with error status 255; restarting ssh
2026/02/16 02:34:33 autossh[34]: starting ssh (count 3)
2026/02/16 02:34:33 autossh[34]: ssh child pid is 44
2026/02/16 02:34:35 autossh[34]: ssh exited with error status 255; restarting ssh
2026/02/16 02:34:35 autossh[34]: starting ssh (count 4)
2026/02/16 02:34:35 autossh[34]: ssh child pid is 45
2026/02/16 02:34:37 autossh[34]: ssh exited with error status 255; restarting ssh
2026/02/16 02:34:37 autossh[34]: starting ssh (count 5)
2026/02/16 02:34:37 autossh[34]: ssh child pid is 46
2026/02/16 02:34:39 autossh[34]: ssh exited with error status 255; restarting ssh
2026/02/16 02:34:39 autossh[34]: starting ssh (count 6)
2026/02/16 02:34:39 autossh[34]: ssh child pid is 47
2026/02/16 02:34:40 autossh[34]: ssh exited with error status 255; restarting ssh
2026/02/16 02:34:42 autossh[34]: starting ssh (count 7)
2026/02/16 02:34:42 autossh[34]: ssh child pid is 48
2026/02/16 02:34:44 autossh[34]: ssh exited with error status 255; restarting ssh
2026/02/16 02:34:52 autossh[34]: starting ssh (count 8)
2026/02/16 02:34:52 autossh[34]: ssh child pid is 49
2026/02/16 02:34:54 autossh[34]: ssh exited with error status 255; restarting ssh
2026/02/16 02:35:12 autossh[34]: starting ssh (count 9)
2026/02/16 02:35:12 autossh[34]: ssh child pid is 50
2026/02/16 02:35:13 autossh[34]: ssh exited with error status 255; restarting ssh
2026/02/16 02:35:45 autossh[34]: starting ssh (count 10)
2026/02/16 02:35:45 autossh[34]: ssh child pid is 51
2026/02/16 02:35:47 autossh[34]: ssh exited with error status 255; restarting ssh
2026/02/16 02:36:37 autossh[34]: starting ssh (count 11)
2026/02/16 02:36:37 autossh[34]: ssh child pid is 52
2026/02/16 02:36:39 autossh[34]: ssh exited with error status 255; restarting ssh
2026/02/16 02:37:51 autossh[34]: starting ssh (count 12)
2026/02/16 02:37:51 autossh[34]: ssh child pid is 53
2026/02/16 02:37:53 autossh[34]: ssh exited with error status 255; restarting ssh
2026/02/16 02:39:31 autossh[34]: starting ssh (count 13)
2026/02/16 02:39:31 autossh[34]: ssh child pid is 54
2026/02/16 02:39:32 autossh[34]: ssh exited with error status 255; restarting ssh
2026/02/16 02:41:40 autossh[34]: starting ssh (count 14)
2026/02/16 02:41:40 autossh[34]: ssh child pid is 55
2026/02/16 02:41:42 autossh[34]: ssh exited with error status 255; restarting ssh
2026/02/16 02:44:24 autossh[34]: starting ssh (count 15)
2026/02/16 02:44:24 autossh[34]: ssh child pid is 56
2026/02/16 02:44:26 autossh[34]: ssh exited with error status 255; restarting ssh