FTP not work, IP not have response.
I tested ping with online website and no have any response, total lost, 100% of packets sent has been lost
FTP IP: ftp.epizy.com
The DDoS Attack continue?
Ping to most servers is blocked now as part of the measures to stop the DDoS attack. It will however not affect your ability to use FTP itself.
What do you mean by “FTP not work, IP not have a response”? Can you try to login with FileZilla and paste the errors from the FTP server here?
Let’s continue my answers here. (It’s the same issue)
I checked the traffic through a VPN and this seems to connect. I tried to contact my ISP but they did not seem to have enough technical information. Anyway, there seems to be a routing problem between the FTP server and my ISP.
It’s a trace without VPN:
C:\\Users\\Lara>tracert 185.27.134.11 Rastreando a rota para 1113427185.ifastnet.org [185.27.134.11] com no mximo 30 saltos: 1 1 ms 1 ms 1 ms AcidHub [192.168.200.1]
2 11 ms 12 ms 13 ms 10.11.0.1
3 13 ms 11 ms 12 ms bd075050.virtua.com.br [189.7.80.80]
4 * * * Esgotado o tempo limite do pedido.
5 * * * Esgotado o tempo limite do pedido.
6 * * * Esgotado o tempo limite do pedido.
7 * * * Esgotado o tempo limite do pedido.
and with VPN:
C:\\Users\\Lara>tracert 185.27.134.11 Rastreando a rota para 1113427185.ifastnet.org [185.27.134.11] com no mximo 30 saltos: 1 187 ms 189 ms 189 ms 10.8.0.1
2 191 ms 188 ms 201 ms 23.107.60.73
3 201 ms 190 ms 189 ms te0-10-0-32.ccr41.lax04.atlas.cogentco.com [38.104.82.21]
4 188 ms 384 ms 189 ms be3271.ccr41.lax01.atlas.cogentco.com [154.54.42.101]
5 214 ms 204 ms 200 ms be2931.ccr21.phx02.atlas.cogentco.com [154.54.44.85]
6 207 ms 209 ms 210 ms be2929.ccr21.elp01.atlas.cogentco.com [154.54.42.66]
7 221 ms 223 ms 222 ms be3047.ccr22.den01.atlas.cogentco.com [154.54.1.126]
8 234 ms 233 ms 233 ms be3036.ccr22.mci01.atlas.cogentco.com [154.54.31.90]
9 245 ms 246 ms 245 ms be2832.ccr42.ord01.atlas.cogentco.com [154.54.44.170]
10 256 ms 253 ms 253 ms be2718.ccr22.cle04.atlas.cogentco.com [154.54.7.130]
11 260 ms 258 ms 269 ms be2994.ccr22.yyz02.atlas.cogentco.com [154.54.31.234]
12 268 ms 266 ms 268 ms be3260.ccr22.ymq01.atlas.cogentco.com [154.54.42.90]
13 336 ms 486 ms 417 ms be3043.ccr22.lpl01.atlas.cogentco.com [154.54.44.165]
14 482 ms 436 ms 425 ms be2191.ccr21.man01.atlas.cogentco.com [130.117.49.50]
15 457 ms 337 ms 337 ms be2826.rcr21.man02.atlas.cogentco.com [154.54.59.10]
16 336 ms 339 ms 347 ms 149.6.11.22
17 341 ms 341 ms 343 ms v504.cr-4.rel.ncl.wildcard.net.uk [31.22.6.25]
18 341 ms 349 ms 339 ms cust.te3-1.cr-4.rel.ncl.wildcard.net.uk [31.22.6.126] 19 * * * Esgotado o tempo limite do pedido.
20 * * * Esgotado o tempo limite do pedido.
21 * * * Esgotado o tempo limite do pedido.
22 * * * Esgotado o tempo limite do pedido.
Thank you @ShyPixie for including the traceroute, it tells a lot about the issue (I did take the liberty to format the message though, the line endings were missing from the pasted text it seems).
The traceroute with the VPN is what the traceroute should look like: a few steps inside the network of the internet provider, then a number of hops through an intermediate network (cogentco.com in this case) after which it ends up at the network of Wildcard, who own the datacenter where we host your websites. It fails after that because we block further traceroutes within our network, but these results show that you can reach our network.
The traceroute without the VPN shows that the connection hits your internet provider, but is completely blocked afterwards. That’s very clear proof that your internet provider is blocking the connection. Whether that’s a technical error or on purpose I can’t tell from here.
I would highly recommend to send these traceroutes to your internet provider as well, because it clearly tells them what’s going on and that it’s something they should fix.