All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Very big latency to DigitalOcean (amsterdam), from Ukraine (not from all), help me to fix it.
Okay, agian, first of all - sorry for my really bad english.
I have some VPS in digitalocean, (amsterdam), i wont to say my real IP address, but i will show my gateway, please ping it: 185.14.184.1
My problem is - very big latency, (packetloss (check traceroute)) from my country to Amsterdam.
Tracert from my PC to DigitalOcean (amsterdam) gateway (same ping to my VPS too);
$ traceroute 185.14.184.1
traceroute to 185.14.184.1 (185.14.184.1), 30 hops max, 60 byte packets
1 10.0.161.254 (10.0.161.254) 0.784 ms 0.737 ms 0.711 ms
2 h-176-108-0-193.ktv.net.ua (176.108.0.193) 0.692 ms 0.683 ms 0.665 ms
3 donetsk1-ge-0-0-0-172.ett.ua (80.93.126.233) 3.432 ms 3.389 ms 3.347 ms
4 EUROTRANSTE.edge3.Frankfurt1.Level3.net (62.67.38.78) 40.461 ms 38.406 ms 40.717 ms
5 ae57-1110.edge3.Frankfurt1.Level3.net (62.67.38.77) 39.794 ms 41.529 ms 40.848 ms
6 * * *
7 xe-4-3-2.fra44.ip4.tinet.net (77.67.95.13) 98.684 ms 100.726 ms IntelQ-Tinet (4.68.63.58) 97.557 ms
8 xe-0-0-0.ams12.ip4.tinet.net (89.149.186.234) 103.145 ms xe-1-1-0.ams12.ip4.tinet.net (89.149.185.93) 105.956 ms xe-2-0-0.ams12.ip4.tinet.net (89.149.186.246) 106.226 ms
9 serverstack-gw.ip4.tinet.net (141.136.96.18) 107.048 ms 104.866 ms 107.943 ms
10 185.14.184.1 (185.14.184.1) 105.800 ms 107.126 ms 104.948 ms
I was think, it's my own problem, but is not. Here is traceroute to another amsterdam located servers:
for example: 80.82.70.133
traceroute 80.82.70.133
traceroute to 80.82.70.133 (80.82.70.133), 30 hops max, 60 byte packets
1 10.0.161.254 (10.0.161.254) 0.639 ms 0.602 ms 0.575 ms
2 h-176-108-0-193.ktv.net.ua (176.108.0.193) 0.556 ms 0.537 ms 0.650 ms
3 donetsk1-ge-0-0-0-172.ett.ua (80.93.126.233) 4.379 ms 30.813 ms 30.807 ms
4 213.242.109.34 (213.242.109.34) 9.308 ms 9.500 ms 9.419 ms
5 213.242.109.33 (213.242.109.33) 23.450 ms 23.453 ms 23.436 ms
6 * * *
7 4.69.200.173 (4.69.200.173) 42.728 ms 4.69.200.169 (4.69.200.169) 43.613 ms 49.598 ms
8 ae-23-23.ebr1.Dusseldorf1.Level3.net (4.69.143.189) 41.279 ms ae-22-22.ebr1.Dusseldorf1.Level3.net (4.69.143.185) 49.256 ms 43.764 ms
9 ae-47-47.ebr3.Frankfurt1.Level3.net (4.69.143.174) 45.027 ms ae-46-46.ebr3.Frankfurt1.Level3.net (4.69.143.170) 42.790 ms ae-47-47.ebr3.Frankfurt1.Level3.net (4.69.143.174) 43.396 ms
10 ae-93-93.csw4.Frankfurt1.Level3.net (4.69.163.14) 43.387 ms ae-83-83.csw3.Frankfurt1.Level3.net (4.69.163.10) 41.346 ms 41.339 ms
11 ae-4-90.edge4.Frankfurt1.Level3.net (4.69.154.200) 41.331 ms 41.316 ms ae-3-80.edge4.Frankfurt1.Level3.net (4.69.154.136) 43.518 ms
12 glbx-level3-10G.Frankfurt1.Level3.net (4.68.63.242) 41.500 ms 41.497 ms 47.641 ms
13 ae8.scr4.FRA4.gblx.net (67.16.145.241) 75.857 ms ae8.scr3.FRA4.gblx.net (67.16.145.237) 43.522 ms 43.667 ms
14 po2.ar7.AMS2.gblx.net (67.16.137.242) 49.673 ms po1.ar7.AMS2.gblx.net (67.16.137.238) 50.042 ms po2.ar7.AMS2.gblx.net (67.16.137.242) 49.644 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Or another amsterdam located server:
traceroute 195.5.121.10
traceroute to 195.5.121.10 (195.5.121.10), 30 hops max, 60 byte packets
1 10.0.161.254 (10.0.161.254) 0.374 ms 0.343 ms 0.495 ms
2 h-176-108-0-193.ktv.net.ua (176.108.0.193) 0.655 ms 0.637 ms 0.622 ms
3 donetsk1-ge-0-0-0-172.ett.ua (80.93.126.233) 3.318 ms 3.285 ms 3.277 ms
4 EUROTRANSTE.edge3.Frankfurt1.Level3.net (62.67.38.78) 38.346 ms 40.384 ms 39.854 ms
5 ae57-1110.edge3.Frankfurt1.Level3.net (62.67.38.77) 38.308 ms 40.473 ms 40.584 ms
6 * ae-3-80.edge5.Frankfurt1.Level3.net (4.69.154.137) 40.580 ms ae-1-60.edge5.Frankfurt1.Level3.net (4.69.154.9) 36.089 ms
7 Cogent-level3-1x10G.Frankfurt.Level3.net (4.68.70.118) 40.136 ms te0-0-0-3.ccr21.fra06.atlas.cogentco.com (130.117.15.129) 38.793 ms Cogent-level3-1x10G.Frankfurt.Level3.net (4.68.70.118) 40.091 ms
8 te0-4-0-5.ccr22.fra03.atlas.cogentco.com (154.54.61.165) 38.377 ms te0-6-0-5.ccr22.fra03.atlas.cogentco.com (154.54.76.57) 39.248 ms te0-2-0-5.ccr22.fra03.atlas.cogentco.com (154.54.36.62) 41.389 ms
9 te0-4-0-2.ccr22.ams03.atlas.cogentco.com (154.54.39.197) 45.887 ms te0-2-0-2.ccr22.ams03.atlas.cogentco.com (130.117.1.65) 47.925 ms te0-1-0-2.ccr22.ams03.atlas.cogentco.com (130.117.2.230) 45.874 ms
10 149.11.64.14 (149.11.64.14) 46.312 ms 46.277 ms 46.085 ms
11 195.5.121.10.static.alvotech.net (195.5.121.10) 52.562 ms 51.875 ms 51.226 ms
As you see, no problems with my internet provider, and pings to amsterdam is good (for me good is minimum 40, maximum 60ms);
So, go again look to digitalocean:
$ traceroute 185.14.184.1
traceroute to 185.14.184.1 (185.14.184.1), 30 hops max, 60 byte packets
1 10.0.161.254 (10.0.161.254) 0.784 ms 0.737 ms 0.711 ms
2 h-176-108-0-193.ktv.net.ua (176.108.0.193) 0.692 ms 0.683 ms 0.665 ms
3 donetsk1-ge-0-0-0-172.ett.ua (80.93.126.233) 3.432 ms 3.389 ms 3.347 ms
4 EUROTRANSTE.edge3.Frankfurt1.Level3.net (62.67.38.78) 40.461 ms 38.406 ms 40.717 ms
5 ae57-1110.edge3.Frankfurt1.Level3.net (62.67.38.77) 39.794 ms 41.529 ms 40.848 ms
6 * * *
7 xe-4-3-2.fra44.ip4.tinet.net (77.67.95.13) 98.684 ms 100.726 ms IntelQ-Tinet (4.68.63.58) 97.557 ms
8 xe-0-0-0.ams12.ip4.tinet.net (89.149.186.234) 103.145 ms xe-1-1-0.ams12.ip4.tinet.net (89.149.185.93) 105.956 ms xe-2-0-0.ams12.ip4.tinet.net (89.149.186.246) 106.226 ms
9 serverstack-gw.ip4.tinet.net (141.136.96.18) 107.048 ms 104.866 ms 107.943 ms
10 185.14.184.1 (185.14.184.1) 105.800 ms 107.126 ms 104.948 ms
do oyu see 6 step? it's ***, i was use in windows winmtr, and pinglatency for check it, and it's have packetloss ~ 50%, after this step ping go high. It's ubnormal for me, and i hate this situation, because ping for me is main.
At night, pings (latency) to digitalocean go to be OK, it's show me ~ 44ms, but this happened only at day....
So, guys, help me please, how to "report" about this problem to Tier1 Operator? Or what i must to do? I was send report to digitalocean support, and they say "it's brandwish "jumps"", and nothing more. Yes, i understand it already. When all europe people go download at day - big channel loading, BUT WHY SO BIG PING? Why anybody do not fix this problem?
P.S. Try to understand please, this problem caused not to all amsterdam users, or ISP providers, it's caused only for Eurotranstelecom users, + few russian operators, who use cogent, or rent tier1.... So guys, tell me truth, where i am miss, what i must to do, because i wont to megre my little project from so cheap hosting....
About DigitalOcean NY location - it's have great ping, it's never go change, it's always stable, and always show me ~ 118-120ms from ukraine.
Only problems with Amsterdam....
P.P.S. here is just-ping.com result:
http://just-ping.com/index.php?vh=185.14.184.1&c=&s=ping!
as you see, ping good for most users, (check ukraine, 40+ms); but not for my and few other ISP at day time...
Help me!)
Comments
I see 49ms to the Ukraine, however ping and traceroute from my location in the UK is good an stable using 185.14.184.1
Try to contact your ISP, maybe they can fix the problem. I do not see any problems with Cogent from Ukraine.
Попробуйте обратиться к вашему провайдеру, возможно, они могут решить эту проблему.
Я не вижу никаких проблем с Cogent из Украины.
` 2 190 ms 3 ms 199 ms XXXXX.ccr01.kbp01.atlas.cogentco.com [149.6.XX.XXX]
3 19 ms 19 ms 19 ms te0-1-0-1.ccr21.bts01.atlas.cogentco.com [130.11
7.49.41]
4 26 ms 26 ms 26 ms te0-3-0-5.ccr21.muc01.atlas.cogentco.com [154.54
.38.249]
5 32 ms 32 ms 32 ms te0-5-0-4.mpd21.fra03.atlas.cogentco.com [154.54
.74.210]
6 38 ms 38 ms 38 ms te0-2-0-2.mpd21.ams03.atlas.cogentco.com [130.11
7.2.202]
7 182 ms 199 ms 207 ms te2-1.mag01.ams03.atlas.cogentco.com [130.117.48
.62]
8 38 ms 48 ms 38 ms 185.14.184.1
Trace complete.`
English: That's the point, that always some problems, not clear where. Provider - a small, buy traffic from evrotranstelekoma. Now ping - all okay, no losses.
Start with 7utra and 23:00 ping jumps to 100-150-200ms. Other operators - all okay, in a minority of Russian \ Ukrainian - the same problem as me.
Russian:
Вот в этом и дело, что постоянно какие-то проблемы, не понятные причем. Провайдер - мелкий, покупает трафик у евротранстелекома. Сейчас пингую - все окей, потерь нет.
Начинаю с 7утра, и до 23:00 пинг подскакивает до 100-150-200мс. У других операторов - все окей, у меньшинства русских\украинских - такая же проблема как и у меня.
Проблема только когда подключение идет через Tinet?
да, только когда через Tinet.
Я могу только предположить вам обратиться к Tinet и вашему провайдеру.
My guess is that your ISP has overloaded links to some upstreams/peerings, as you note this only manifests itself in the evening, aka peak hours. Here's how it can look like, from monitoring of one of my VPSes: http://ompldr.org/vaG82NA/2013-03-05T224750Z-sp.png
When a link has not enough capacity, routers start to buffer packets before sending further, but then even this buffer is overflown, and they start just dropping them (you can see that peaks are also colored blue, i.e. some loss). Smokeping is a great tool btw, to monitor for these kinds of issues.
What do you expect anyone to suggest? Other than "complain to your ISP, if that doesn't help, change ISPs".
Tinet or whoever, they won't talk to you, you are not their customer. The only choice you have is to pester your immediate ISP, and get them to forward the issue to upstream / or change upstreams / or upgrade their pipe.