I have the same issue, but mine started today. I contacted my local ISP that provided to me info that everything was running fine, I checked the router, ports and etc.
This always happens after the DDoS attacks, something happens to this NTT route.
My Server is Behemoth

Tracing route to 204.2.229.102 over a maximum of 30 hops

1 2 ms 2 ms 1 ms 192.168.0.1
2 190 ms 198 ms 205 ms 10.38.64.1
3 234 ms 227 ms 240 ms c90648d1.virtua.com.br [201.6.72.209]
4 237 ms 231 ms 237 ms c90640ee.virtua.com.br [201.6.64.238]
5 191 ms 204 ms 205 ms c90640e4.virtua.com.br [201.6.64.228]
6 217 ms 215 ms 225 ms embratel-H0-7-0-0-agg02.spolp.embratel.net.br [189.52.153.1]
7 348 ms 351 ms 351 ms ebt-H1-14-0-1-tcore01.spolp.embratel.net.br [200.230.130.17]
8 345 ms 349 ms 351 ms ebt-B1153-intl03.mianap.embratel.net.br [200.230.220.142]
9 361 ms 353 ms 360 ms ix-et-9-1-2-0.tcore2.mln-miami.as6453.net [66.110.72.89]
10 362 ms 354 ms 360 ms if-ae-1-2.tcore1.mln-miami.as6453.net [63.243.152.61]
11 406 ms * 352 ms ae-6.a00.miamfl02.us.bb.gin.ntt.net [129.250.9.33]
12 422 ms 423 ms 424 ms ae-4.r05.miamfl02.us.bb.gin.ntt.net [129.250.3.40]
13 367 ms 386 ms 366 ms ae-1.r21.miamfl02.us.bb.gin.ntt.net [129.250.4.88]
14 * * * Request timed out.
15 346 ms 351 ms 357 ms ae-5.r22.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
16 348 ms 343 ms 351 ms ae-1.r23.lsanca07.us.bb.gin.ntt.net [129.250.2.207]
17 394 ms 410 ms 431 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
18 425 ms 390 ms 385 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
19 384 ms 386 ms 395 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
20 395 ms 392 ms 398 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
21 389 ms 401 ms 410 ms 204.2.229.234
22 396 ms 401 ms 401 ms 204.2.229.102

Trace complete.

Also let me know if I can provide any other information required.