Random TCP handshake problems / HTTP 522

Hi, Since Friday we're experiencing random 522 at customers' pages. I've found that some CF servers doesn't want to talk with us when they get SYN-ACK send from synproxy, it seems like the SYN-ACK is rejected somewhere. I see that in DCs located in Warsaw and Frankfurt. When I pass traffic form CF beyond the synproxy everything is ok. It's not a subject of specific prefix or address. One address generally works, but once upon a time it doesn't establish TCP session for a few minutes. MTRs doesn't show any packet loss. tcpdump and traceroute outputs attached.
1 Reply
Denisov
Denisov6mo ago
Hi, I too see this problem. It big problem 50% traffic loses because this. Error on page Paris, Warsaw and Frankfurt.... But I see this on traceroute. Yesterday big loss, at this night problem was solved, but in the morning there are big losses again and problem still persist traceroute 172.68.138.122 -n traceroute to 172.68.138.122 (172.68.138.122), 30 hops max, 60 byte packets 1 45.135.92.1 0.489 ms 0.476 ms 0.450 ms 2 93.189.144.136 0.242 ms 0.256 ms 0.248 ms 3 80.64.102.112 0.460 ms 0.455 ms 0.433 ms 4 80.64.97.71 1.446 ms 1.174 ms 1.441 ms 5 80.64.97.70 1.008 ms 1.039 ms 1.023 ms 6 * 172.68.138.122 28.493 ms * traceroute 162.158.102.12 -n traceroute to 162.158.102.12 (162.158.102.12), 30 hops max, 60 byte packets 1 45.135.92.1 1.512 ms 1.704 ms 1.683 ms 2 93.189.144.136 0.407 ms 0.432 ms 0.423 ms 3 80.64.102.112 0.413 ms 0.402 ms 0.380 ms 4 80.64.97.71 0.995 ms 1.226 ms 1.226 ms 5 80.64.97.70 1.186 ms 0.707 ms 0.729 ms 6 * * * 7 162.158.102.12 28.667 ms 28.437 ms 28.458 ms