Xplenty SSH Tunnel Status

Find the latest information on your SSH tunnel availability below.


Status Refreshed April 19, 2026 at 03:13am 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/04/18 20:04:43 autossh[23]: port set to 0, monitoring disabled
2026/04/18 20:04:43 autossh[24]: starting ssh (count 1)
2026/04/18 20:04:43 autossh[24]: ssh child pid is 27
2026/04/18 20:04:44 autossh[32]: port set to 0, monitoring disabled
2026/04/18 20:04:44 autossh[33]: starting ssh (count 1)
2026/04/18 20:04:44 autossh[33]: ssh child pid is 34
2026/04/18 20:04:46 autossh[33]: ssh exited with error status 255; restarting ssh
2026/04/18 20:04:46 autossh[33]: starting ssh (count 2)
2026/04/18 20:04:46 autossh[33]: ssh child pid is 42
2026/04/18 20:04:48 autossh[33]: ssh exited with error status 255; restarting ssh
2026/04/18 20:04:48 autossh[33]: starting ssh (count 3)
2026/04/18 20:04:48 autossh[33]: ssh child pid is 43
2026/04/18 20:04:50 autossh[33]: ssh exited with error status 255; restarting ssh
2026/04/18 20:04:50 autossh[33]: starting ssh (count 4)
2026/04/18 20:04:50 autossh[33]: ssh child pid is 44
2026/04/18 20:04:51 autossh[33]: ssh exited with error status 255; restarting ssh
2026/04/18 20:04:51 autossh[33]: starting ssh (count 5)
2026/04/18 20:04:51 autossh[33]: ssh child pid is 45
2026/04/18 20:04:53 autossh[33]: ssh exited with error status 255; restarting ssh
2026/04/18 20:04:53 autossh[33]: starting ssh (count 6)
2026/04/18 20:04:53 autossh[33]: ssh child pid is 46
2026/04/18 20:04:55 autossh[33]: ssh exited with error status 255; restarting ssh
2026/04/18 20:04:57 autossh[33]: starting ssh (count 7)
2026/04/18 20:04:57 autossh[33]: ssh child pid is 47
2026/04/18 20:04:59 autossh[33]: ssh exited with error status 255; restarting ssh
2026/04/18 20:05:07 autossh[33]: starting ssh (count 8)
2026/04/18 20:05:07 autossh[33]: ssh child pid is 48
2026/04/18 20:05:08 autossh[33]: ssh exited with error status 255; restarting ssh
2026/04/18 20:05:26 autossh[33]: starting ssh (count 9)
2026/04/18 20:05:26 autossh[33]: ssh child pid is 49
2026/04/18 20:05:28 autossh[33]: ssh exited with error status 255; restarting ssh
2026/04/18 20:06:00 autossh[33]: starting ssh (count 10)
2026/04/18 20:06:00 autossh[33]: ssh child pid is 50
2026/04/18 20:06:02 autossh[33]: ssh exited with error status 255; restarting ssh
2026/04/18 20:06:52 autossh[33]: starting ssh (count 11)
2026/04/18 20:06:52 autossh[33]: ssh child pid is 51
2026/04/18 20:06:53 autossh[33]: ssh exited with error status 255; restarting ssh
2026/04/18 20:08:05 autossh[33]: starting ssh (count 12)
2026/04/18 20:08:05 autossh[33]: ssh child pid is 52
2026/04/18 20:08:07 autossh[33]: ssh exited with error status 255; restarting ssh
2026/04/18 20:09:45 autossh[33]: starting ssh (count 13)
2026/04/18 20:09:45 autossh[33]: ssh child pid is 53
2026/04/18 20:09:47 autossh[33]: ssh exited with error status 255; restarting ssh
2026/04/18 20:11:55 autossh[33]: starting ssh (count 14)
2026/04/18 20:11:55 autossh[33]: ssh child pid is 54
2026/04/18 20:11:57 autossh[33]: ssh exited with error status 255; restarting ssh
2026/04/18 20:14:39 autossh[33]: starting ssh (count 15)
2026/04/18 20:14:39 autossh[33]: ssh child pid is 55
2026/04/18 20:14:41 autossh[33]: ssh exited with error status 255; restarting ssh