522 errors - ukraine hosting provider AS200000

Hi,
We also have these same issues in The Netherlands, from the Hamburg datacenter

@recandnot @kapeliukh.aleksandr @dmp7781 @bogdans @walukmichal @jolie1 @and.shemchuk could you get a traceroute from your servers back to us while the issue is happening? Run each of these from your server’s commandline and paste the results here:

traceroute 172.68.238.143
mtr -urwc 30 172.68.238.143
mtr -rwc 30 172.68.238.143

1 to 5: our intern network and external IP, that i don’t want to show at the community)

6 te0-3-1-4.rcr21.b015960-1.ams03.atlas.cogentco .com (149.6.128.21) 1.572 ms 1.823 ms 1.788 ms
7 be2456.ccr42.ams03.atlas.cogentco .com (130.117.49.145) 1.765 ms 2.743 ms 2.734 ms
8 be2814.ccr42.fra03.atlas.cogentco .com (130.117.0.142) 8.705 ms 8.678 ms 8.673 ms
9 be2960.ccr22.muc03.atlas.cogentco .com (154.54.36.254) 14.612 ms 13.634 ms 14.584 ms
10 be3462.ccr52.vie01.atlas.cogentco .com (154.54.59.181) 20.588 ms 20.564 ms 20.906 ms
11 be3463.ccr22.bts01.atlas.cogentco .com (154.54.59.186) 21.903 ms 21.890 ms 22.007 ms
12 be2047.ccr22.kbp01.atlas.cogentco .com (154.54.60.206) 38.926 ms 37.882 ms 37.872 ms
13 149.6.191.138 (149.6.191.138) 37.856 ms 37.434 ms 37.575 ms
14 172.68.238.143 (172.68.238.143) 36.860 ms 37.827 ms 37.809 ms

1-5 our intern network and external IP, that i don’t want to show at the community
6.|-- te0-3-1-4.rcr21.b015960-1.ams03.atlas.cogentco .com 0.0% 30 2.6 1.7 1.2 2.6 0.4
7.|-- be2456.ccr42.ams03.atlas.cogentco .com 0.0% 30 2.2 4.0 1.7 54.9 9.6
8.|-- be2814.ccr42.fra03.atlas.cogentco .com 0.0% 30 12.6 10.3 8.4 41.8 6.1
9.|-- be2960.ccr22.muc03.atlas.cogentco .com 0.0% 30 15.1 14.1 13.6 15.6 0.5
10.|-- be3462.ccr52.vie01.atlas.cogentco .com 0.0% 30 20.5 20.7 19.9 29.7 1.7
11.|-- be3463.ccr22.bts01.atlas.cogentco .com 0.0% 30 22.1 23.1 21.2 62.7 7.5
12.|-- be2047.ccr22.kbp01.atlas.cogentco .com 0.0% 30 37.5 37.8 37.0 44.3 1.3
13.|-- 149.6.191.138 0.0% 30 38.2 40.7 37.2 73.9 7.9
14.|-- 172.68.238.143 76.7% 30 37.7 37.5 36.8 38.8 0.8


6.|-- te0-3-1-4.rcr21.b015960-1.ams03.atlas.cogentco .com 0.0% 30 1.3 1.7 1.2 4.3 0.7
7.|-- be2456.ccr42.ams03.atlas.cogentco .com 0.0% 30 1.7 2.8 1.7 10.7 2.0
8.|-- be2814.ccr42.fra03.atlas.cogentco .com 0.0% 30 8.6 10.1 8.4 26.8 3.8
9.|-- be2960.ccr22.muc03.atlas.cogentco .com 0.0% 30 14.2 15.5 13.4 37.6 5.1
10.|-- be3462.ccr52.vie01.atlas.cogentco .com 0.0% 30 19.9 21.1 19.9 34.7 2.7
11.|-- be3463.ccr22.bts01.atlas.cogentco .com 0.0% 30 22.4 22.0 21.1 24.3 1.0
12.|-- be2047.ccr22.kbp01.atlas.cogentco .com 0.0% 30 37.4 38.3 36.9 55.2 3.3
13.|-- 149.6.191.138 0.0% 30 38.4 39.8 37.4 58.0 4.4
14.|-- 172.68.238.143 0.0% 30 38.5 37.5 36.7 40.7 1.1

I think we missed the window of failure just and as of ~10:56 UTC things are working again. As soon as you see a 522, please run the following on your origin server:

traceroute 172.68.238.143
mtr -urwc 30 172.68.238.143
mtr -rwc 30 172.68.238.143

We still have the same issue, it is not resolved for us at all.

Here is a new trace etc.:
mtr -rwc 30 172.68.238.143
Start: 2021-08-23T13:02:21+0200
HOST: *** Loss% Snt Last Avg Best Wrst StDev
6.|-- te0-3-1-4.rcr21.b015960-1.ams03.atlas.cogentco .com 0.0% 30 1.3 1.7 1.2 4.3 0.7
7.|-- be2456.ccr42.ams03.atlas.cogentco .com 0.0% 30 1.7 2.8 1.7 10.7 2.0
8.|-- be2814.ccr42.fra03.atlas.cogentco .com 0.0% 30 8.6 10.1 8.4 26.8 3.8
9.|-- be2960.ccr22.muc03.atlas.cogentco .com 0.0% 30 14.2 15.5 13.4 37.6 5.1
10.|-- be3462.ccr52.vie01.atlas.cogentco .com 0.0% 30 19.9 21.1 19.9 34.7 2.7
11.|-- be3463.ccr22.bts01.atlas.cogentco .com 0.0% 30 22.4 22.0 21.1 24.3 1.0
12.|-- be2047.ccr22.kbp01.atlas.cogentco .com 0.0% 30 37.4 38.3 36.9 55.2 3.3
13.|-- 149.6.191.138 0.0% 30 38.4 39.8 37.4 58.0 4.4
14.|-- 172.68.238.143 0.0% 30 38.5 37.5 36.7 40.7 1.1

traceroute 172.68.238.143
traceroute to 172.68.238.143 (172.68.238.143), 30 hops max, 60 byte packets
6 te0-3-1-4.rcr21.b015960-1.ams03.atlas.cogentco .com (149.6.128.21) 5.307 ms 1.407 ms 1.864 ms
7 be2456.ccr42.ams03.atlas.cogentco .com (130.117.49.145) 2.243 ms 2.122 ms 2.113 ms
8 be2814.ccr42.fra03.atlas.cogentco .com (130.117.0.142) 11.787 ms 11.763 ms 11.389 ms
9 be2960.ccr22.muc03.atlas.cogentco .com (154.54.36.254) 15.288 ms 15.266 ms 14.372 ms
10 be3462.ccr52.vie01.atlas.cogentco .com (154.54.59.181) 20.420 ms 20.551 ms 20.663 ms
11 be3463.ccr22.bts01.atlas.cogentco .com (154.54.59.186) 22.362 ms 22.439 ms 25.350 ms
12 be2047.ccr22.kbp01.atlas.cogentco .com (154.54.60.206) 41.341 ms 41.317 ms 39.798 ms
13 149.6.191.138 (149.6.191.138) 40.926 ms 37.942 ms 38.353 ms
14 172.68.238.143 (172.68.238.143) 37.588 ms 36.995 ms 38.432 ms

mtr -urwc 30 172.68.238.143
Start: 2021-08-23T13:10:01+0200
HOST: *** Loss% Snt Last Avg Best Wrst StDev
6.|-- te0-3-1-4.rcr21.b015960-1.ams03.atlas.cogentco .com 0.0% 30 1.6 1.6 1.1 3.3 0.5
7.|-- be2456.ccr42.ams03.atlas.cogentco .com 0.0% 30 1.9 2.2 1.7 5.6 0.7
8.|-- be2814.ccr42.fra03.atlas.cogentco .com 0.0% 30 8.7 20.5 8.4 136.3 35.0
9.|-- be2960.ccr22.muc03.atlas.cogentco .com 0.0% 30 14.2 14.1 13.5 14.9 0.3
10.|-- be3462.ccr52.vie01.atlas.cogentco .com 0.0% 30 20.5 20.5 19.8 25.4 1.1
11.|-- be3463.ccr22.bts01.atlas.cogentco .com 0.0% 30 22.0 22.8 21.1 51.6 5.5
12.|-- be2047.ccr22.kbp01.atlas.cogentco .com 0.0% 30 36.8 37.9 36.8 43.1 1.3
13.|-- 149.6.191.138 0.0% 30 38.0 40.6 37.2 64.1 5.8
14.|-- 172.68.238.143 76.7% 30 36.7 37.0 36.7 37.4 0.2

@jolie1 is your hosting provider based in the Ukraine? Can you DM me your origin IP address?

Unfortunately, this problem has affected all our customers in the Bulgarian network
All sites that use the Bulgarian servers are down

This has been resolved 1 hour ago but the problem come back
Please understand the situation and resolve the issue with high prior
This has affect lot of people in Europe

1 Like

I have DM’ed you. We are located in The Netherlands

Thanks - to confirm your issue is unrelated to this one - I will check with you directly.

@ServiceProviderNT what is your hosting provider? Is it AS200000 - if it is not, then this is a separate issue. Make sure you check the community advice for 522s here: Community Tip - Fixing Error 522: Connection timed out

Thanks for your update
AS201133
So whats problem ?

@ServiceProviderNT please follow the advice on Community Tip - Fixing Error 522: Connection timed out to check your issue - this thread is specifically for AS200000 which I don’t believe is impacting you because that is not your provider.

We have got the same problems: AS 39566 in Poland.
Today some customers sites proxied by CF hav got 522 errors. Than it worked. And now they still have 522 errors.


Same, maybe traffic is being blocked or something?

All of my sites hosted in Ukraine doesn’t work - we still getting 522 error. Does anyone have the same problem?

I ask my hosting provider - thay doesn’t block CloudFlare IPs.

We host our site on ukraine.com.ua and have the same error:

The hosting company made an annoncment about CloudFlare 522 error: they are not to blame and ask to transfer domains directly to their hosting.

When I press “Pause Cloudflare on Site” at Advanced Actions my site is working good.

This issue is still not solved! I submitted a ticket, but I don’t have any pro or enterprise account or whatever (which is stupid) so I have to send this here, here’s what I wrote:

I’ll start off by saying that I don’t have access to the account that has the domain Gaming-Hub.eu set-up.

Hello, for the past 2 days from 7:00 UTC+2 to maybe 11:00 I’ve been getting 522 status and today it’s almost the whole day, it’s only on 1 webserver though (217.11.249.85 Czech Republic, https://gaming-hub.eu/), websites hosted on my VPS (82.208.17.136 Czech Republic) are running fine (eg. https://demos.gaming-hub.eu/), I posted a ticket to the host and they told me they don’t see any problem on their side and told me to send you this:

Times are in UTC+2
09:30:49.044838 IP 141.101.96.16.42578 > 217.11.249.85.80: Flags [S], seq 3950906380, win 65535, options [mss 1460,nop,nop,sackOK,nop,wscale 10], length 0
09:30:49.044851 IP 217.11.249.85.80 > 141.101.96.16.42578: Flags [S.], seq 2975647109, ack 3950906381, win 0, options [mss 1460], length 0
09:30:49.594316 IP 141.101.96.128.35138 > 217.11.249.85.80: Flags [S], seq 3736377527, win 65535, options [mss 1460,nop,nop,sackOK,nop,wscale 10], length 0
09:30:49.594332 IP 217.11.249.85.80 > 141.101.96.128.35138: Flags [S.], seq 1154830161, ack 3736377528, win 0, options [mss 1460], length 0
09:30:50.095250 IP 141.101.96.16.42578 > 217.11.249.85.80: Flags [S], seq 3950906380, win 65535, options [mss 1460,nop,nop,sackOK,nop,wscale 10], length 0
09:30:50.095265 IP 217.11.249.85.80 > 141.101.96.16.42578: Flags [S.], seq 2975647109, ack 3950906381, win 0, options [mss 1460], length 0
09:30:51.242117 IP 172.70.34.193.11474 > 217.11.249.85.80: Flags [S], seq 1779952009, win 65535, options [mss 1460,nop,nop,sackOK,nop,wscale 10], length 0
09:30:51.242159 IP 217.11.249.85.80 > 172.70.34.193.11474: Flags [S.], seq 2002756828, ack 1779952010, win 0, options [mss 1460], length 0
09:30:52.143220 IP 141.101.96.16.42578 > 217.11.249.85.80: Flags [S], seq 3950906380, win 65535, options [mss 1460,nop,nop,sackOK,nop,wscale 10], length 0
09:30:52.143234 IP 217.11.249.85.80 > 141.101.96.16.42578: Flags [S.], seq 3001257472, ack 3950906381, win 0, options [mss 1460], length 0
09:30:53.626324 IP 141.101.96.128.35138 > 217.11.249.85.80: Flags [S], seq 3736377527, win 65535, options [mss 1460,nop,nop,sackOK,nop,wscale 10], length 0
09:30:53.626339 IP 217.11.249.85.80 > 141.101.96.128.35138: Flags [S.], seq 1166644269, ack 3736377528, win 0, options [mss 1460], length 0

so basically the SYN packet from CloudFlare is going through, then the SYN / ACK goes fine from the host to CloudFlare but then the ACK packet doesn’t come from CloudFlare.

I’ve been watching the CloudFlare Community and people were having the same issue
(522 errors - ukraine hosting provider AS200000)

Sites hosted on Ukrainian IPs is now working good.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.