Issue #9394 resolved

bitbucket SSH down right now

Guzmán Brasó
created an issue

Good morning,

Below is tcpdump output from a server in a France DC which have no connectivity known issue right now.

Ip 131.103.20.167 ssh does not even reply SYN packets. Ip 131.103.20.168 is able to reply syn but not to establish the socket.

12:03:37.183772 IP 5.39.66.215.49858 > 131.103.20.168.22: Flags [S], seq 3211748865, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 9], length 0 12:03:38.182773 IP 5.39.66.215.49858 > 131.103.20.168.22: Flags [S], seq 3211748865, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 9], length 0 12:03:40.186759 IP 5.39.66.215.49858 > 131.103.20.168.22: Flags [S], seq 3211748865, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 9], length 0 12:03:44.194797 IP 5.39.66.215.61001 > 131.103.20.167.22: Flags [S], seq 1552130016, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 9], length 0 12:03:44.312674 IP 131.103.20.167.22 > 5.39.66.215.61001: Flags [S.], seq 2101408937, ack 1552130017, win 14600, options [mss 1460,nop,wscale 10], length 0 12:03:44.312700 IP 5.39.66.215.61001 > 131.103.20.167.22: Flags [.], ack 1, win 29, length 0 12:03:45.707123 IP 131.103.20.167.22 > 5.39.66.215.61001: Flags [S.], seq 2101408937, ack 1552130017, win 14600, options [mss 1460,nop,wscale 10], length 0 12:03:45.707176 IP 5.39.66.215.61001 > 131.103.20.167.22: Flags [.], ack 1, win 29, length 0 12:03:47.709096 IP 131.103.20.167.22 > 5.39.66.215.61001: Flags [S.], seq 2101408937, ack 1552130017, win 14600, options [mss 1460,nop,wscale 10], length 0 12:03:47.709180 IP 5.39.66.215.61001 > 131.103.20.167.22: Flags [.], ack 1, win 29, length 0 12:03:51.908032 IP 131.103.20.167.22 > 5.39.66.215.61001: Flags [S.], seq 2101408937, ack 1552130017, win 14600, options [mss 1460,nop,wscale 10], length 0 12:03:51.908101 IP 5.39.66.215.61001 > 131.103.20.167.22: Flags [.], ack 1, win 29, length 0

Comments (7)

  1. Guzmán Brasó reporter

    Now the 131.103.20.168 is not replying SYN packets either.

    12:09:07.074969 IP 5.39.66.215.64862 > 131.103.20.167.22: Flags [S], seq 3697053027, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 9], length 0 12:09:08.074818 IP 5.39.66.215.64862 > 131.103.20.167.22: Flags [S], seq 3697053027, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 9], length 0 12:09:10.078778 IP 5.39.66.215.64862 > 131.103.20.167.22: Flags [S], seq 3697053027, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 9], length 0 12:09:14.090826 IP 5.39.66.215.53856 > 131.103.20.168.22: Flags [S], seq 1165177710, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 9], length 0

    12:09:15.090808 IP 5.39.66.215.53856 > 131.103.20.168.22: Flags [S], seq 1165177710, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 9], length 0 12:09:17.094807 IP 5.39.66.215.53856 > 131.103.20.168.22: Flags [S], seq 1165177710, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 9], length 0

  2. Juan M. Caicedo

    I seem to be having a similar issue (I think).

    $ git fetch
    ssh: connect to host bitbucket.org port 22: Connection timed out
    fatal: The remote end hung up unexpectedly
    
  3. Log in to comment