Carbonautics Posted May 29, 2017 Posted May 29, 2017 (edited) straight to the point, I did a speedtest today at ookla speedtest site. I did the test on most of the servers near germany, and frankfurt. All these servers had 170-190 ping which is normal considering my distance. Then I tried ping to jay3 server, it had 280-300 ping. actually all the servers in that city have 280 ping. Does anyone know why is this happening? like most of Eu servers have 180 and just this city has 280 is a bit-odd kind of thing to come accross. I suspect its the packet loss based on the winmtr report which is here: |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 0 | 38 | 38 | 0 | 0 | 2 | 0 | | 117.200.104.1 - 3 | 34 | 33 | 0 | 6 | 14 | 6 | | 218.248.173.142 - 3 | 34 | 33 | 0 | 36 | 111 | 19 | | 218.248.235.198 - 17 | 24 | 20 | 18 | 21 | 49 | 18 | | 61.246.195.185 - 3 | 34 | 33 | 0 | 21 | 31 | 20 | | 182.79.245.161 - 0 | 38 | 38 | 256 | 261 | 282 | 260 | | decix-gw.hetzner.de - 0 | 38 | 38 | 263 | 266 | 283 | 263 | | core22.fsn1.hetzner.com - 0 | 38 | 38 | 267 | 275 | 296 | 270 | | ex9k2.rz12.hetzner.de - 0 | 38 | 38 | 265 | 268 | 287 | 266 | |static.170.72.63.178.clients.your-server.de - 0 | 38 | 38 | 266 | 270 | 286 | 270 | |________________________________________________|______|______|______|______|______|______| If anyone knows about the problem, i would like to learn about it and hopefully solve it too. One more thing can I somehow avoid routing through the servers that give packetloss? Here's another report: |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 0 | 34 | 34 | 0 | 0 | 1 | 0 | | 117.200.104.1 - 0 | 34 | 34 | 6 | 8 | 14 | 7 | | 218.248.173.142 - 0 | 34 | 34 | 16 | 98 | 334 | 89 | | 218.248.235.198 - 42 | 12 | 7 | 18 | 22 | 32 | 19 | | 61.246.195.185 - 0 | 34 | 34 | 27 | 31 | 39 | 27 | | 182.79.245.161 - 0 | 34 | 34 | 255 | 261 | 274 | 255 | | decix-gw.hetzner.de - 0 | 34 | 34 | 262 | 268 | 279 | 267 | | core22.fsn1.hetzner.com - 0 | 34 | 34 | 266 | 278 | 294 | 272 | | ex9k2.rz12.hetzner.de - 0 | 34 | 34 | 266 | 270 | 288 | 268 | |static.170.72.63.178.clients.your-server.de - 0 | 34 | 34 | 268 | 273 | 291 | 270 | |________________________________________________|______|______|______|______|______|______| Edited May 29, 2017 by Carbonautics 1 Quote
Ann!b@l Posted May 29, 2017 Posted May 29, 2017 |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 0 | 38 | 38 | 0 | 0 | 2 | 0 | | 117.200.104.1 - 3 | 34 | 33 | 0 | 6 | 14 | 6 | | 218.248.173.142 - 3 | 34 | 33 | 0 | 36 | 111 | 19 | | 218.248.235.198 - 17 | 24 | 20 | 18 | 21 | 49 | 18 | | 61.246.195.185 - 3 | 34 | 33 | 0 | 21 | 31 | 20 | | 182.79.245.161 - 0 | 38 | 38 | 256 | 261 | 282 | 260 | | decix-gw.hetzner.de - 0 | 38 | 38 | 263 | 266 | 283 | 263 | | core22.fsn1.hetzner.com - 0 | 38 | 38 | 267 | 275 | 296 | 270 | | ex9k2.rz12.hetzner.de - 0 | 38 | 38 | 265 | 268 | 287 | 266 | |static.170.72.63.178.clients.your-server.de - 0 | 38 | 38 | 266 | 270 | 286 | 270 | |________________________________________________|______|______|______|______|______|______| |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 0 | 34 | 34 | 0 | 0 | 1 | 0 | | 117.200.104.1 - 0 | 34 | 34 | 6 | 8 | 14 | 7 | | 218.248.173.142 - 0 | 34 | 34 | 16 | 98 | 334 | 89 | | 218.248.235.198 - 42 | 12 | 7 | 18 | 22 | 32 | 19 | | 61.246.195.185 - 0 | 34 | 34 | 27 | 31 | 39 | 27 | | 182.79.245.161 - 0 | 34 | 34 | 255 | 261 | 274 | 255 | | decix-gw.hetzner.de - 0 | 34 | 34 | 262 | 268 | 279 | 267 | | core22.fsn1.hetzner.com - 0 | 34 | 34 | 266 | 278 | 294 | 272 | | ex9k2.rz12.hetzner.de - 0 | 34 | 34 | 266 | 270 | 288 | 268 | |static.170.72.63.178.clients.your-server.de - 0 | 34 | 34 | 268 | 273 | 291 | 270 | |________________________________________________|______|______|______|______|______|______| seems to be an issue from your side\isp only. Have you tried to change and manually set different dns? https://www.tcpiputils.com/browse/ip-address/117.200.104.1 1 Quote
Carbonautics Posted May 30, 2017 Author Posted May 30, 2017 seems to be an issue from your side\isp only. Have you tried to change and manually set different dns? https://www.tcpiputils.com/browse/ip-address/117.200.104.1 yea, I had Google's DNS for a long time, then since the start of this month it started acting weird so I changed it to open DNS servers. Maybe it got reset again, will try changing it again. Sidenote: its always my isp problem, I only need to know the problem so that I can report it to them maybe even solve it 1 Quote
Carbonautics Posted May 30, 2017 Author Posted May 30, 2017 (edited) Changing DNS did not help the problem still persists, I had open DNS till now on both router and ethernet(pc) now changed it to google DNS servers, that didn't do anything, the ping is still same and the loss giving line isn't the dns server i used( or atleast thats not what i entered in those blank fields). Edited May 30, 2017 by Carbonautics 1 Quote
Ann!b@l Posted May 30, 2017 Posted May 30, 2017 Sidenote: its always my isp problem, I only need to know the problem so that I can report it to them maybe even solve it what I meant with my remark was that the hops causing you troubles should be fixed fixed by your isp itself. It's an issue with their servers. So I even doubt that you can fix it yourself aside maybe test some DYI with dns, dhcp, so on.. or either harass these lazy-ass\scammers through call phones. Changing DNS did not help the problem still persists, I had open DNS till now on both router and ethernet(pc) now changed it to google DNS servers, that didn't do anything, the ping is still same and the loss giving line isn't the dns server i used( or atleast thats not what i entered in those blank fields). yea I suggested this, but tbh there's really tiny chances to fix this issue this way. here a tool that will help you to choose the best dns: https://www.grc.com/dns/benchmark.htm Aside some rare cases or a privacy purpose, actually the dns of your own isp should be the best. Quote
Carbonautics Posted May 30, 2017 Author Posted May 30, 2017 what I meant with my remark was that the hops causing you troubles should be fixed fixed by your isp itself. It's an issue with their servers. So I even doubt that you can fix it yourself aside maybe test some DYI with dns, dhcp, so on.. or either harass these lazy-ass\scammers through call phones here a tool that will help you to choose the best dns: https://www.grc.com/dns/benchmark.htm Aside some rare cases or a privacy purpose, actually the dns of your own isp should be the best. Yea, i did the test it said google dns was best for me, the next was open dns, and so on..... But by changing my isp can the problem be solved? because i think its time i did that and stop complaining about it right? thanks for the help though. 1 Quote
Ann!b@l Posted May 30, 2017 Posted May 30, 2017 But by changing my isp can the problem be solved? because i think its time i did that and stop complaining about it right? Use it at least as a threat toward your current isp and get this abnormal situation fixed.. Or yes change straight for an other one if you get the opportunity to. Quote
Vanaraud Posted May 30, 2017 Posted May 30, 2017 Isn´t that sometimes the connections to outside of country get ovewhelmed? If it´s 1-2 weeks been so, then it might go away. I´ve also had my ping jumping 40-50ms as it´s going over the Atlantic also. Also some servers nowadays block against pinging, that packetloss might be some DDOS prevention? Bc even if I have clean lagometer(almost), I can get ~30% packetloss... My to 1.5 cents 1 Quote
Ann!b@l Posted May 30, 2017 Posted May 30, 2017 (edited) If it´s 1-2 weeks been so, then it might go away. That's the main problem in his case.. never been for a short period only.. And when this is a different kind of connection issue, it's most of the time again linked to his isp. Always knew Carbon with connection issues and rarely seen without so far. Pretty dramatic to see some companies still providing such bad services in 2017. Too bad, customers don't have a ban command over internet for such providers. Edited May 30, 2017 by Ann!b@l 1 Quote
Lenovo Posted June 1, 2017 Posted June 1, 2017 (edited) https://mega.nz/#!nYhHmYRA!lIF7_5i9NOWftO69ZjzBxbQcvlPN6B-x2GWgusvFLkU https://mega.nz/#!vYwWzD5I!EO6Tdy_iVqsfmNuVnW-lVUy0vPWPRu45yvODvYoAAIo this is my problem on jay3 ----------------------------------------------------------------------- cable test ------------------------------------------------------------------------ wi-fi 2.4ghz test 17.53 31 maggio 20017 ------------------------------------------------------------ C:\Windows\system32>ping www.google.it -n 30 Numero Ip : 216.58.207.35 Nazione : United States Citta : Mountain View Host Name : fra16s24-in-f3.1e100.net Esecuzione di Ping www.google.it [216.58.204.35] con 32 byte di dati: Risposta da 216.58.204.35: byte=32 durata=43ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=43ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=46ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=43ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=43ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=41ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=43ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Risposta da 216.58.204.35: byte=32 durata=42ms TTL=49 Statistiche Ping per 216.58.204.35: Pacchetti: Trasmessi = 30, Ricevuti = 30, Persi = 0 (0% persi), Tempo approssimativo percorsi andata/ritorno in millisecondi: Minimo = 41ms, Massimo = 46ms, Medio = 42ms ------------------------------------------------------------ C:\Windows\system32>ping www.google.com -n 30 Numero Ip : 172.217.22.4 Nazione : United States Citta : Mountain View Host Name : fra16s14-in-f4.1e100.net Esecuzione di Ping www.google.com [216.58.205.132] con 32 byte di dati: Risposta da 216.58.205.132: byte=32 durata=17ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=16ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=11ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=11ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=11ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=12ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=11ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=12ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=12ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=10ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=10ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=10ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=11ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=12ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=11ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=10ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=10ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=10ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=10ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=10ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=11ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=12ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=12ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=12ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=13ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=15ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=10ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=14ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=11ms TTL=54 Risposta da 216.58.205.132: byte=32 durata=10ms TTL=54 Statistiche Ping per 216.58.205.132: Pacchetti: Trasmessi = 30, Ricevuti = 30, Persi = 0 (0% persi), Tempo approssimativo percorsi andata/ritorno in millisecondi: Minimo = 10ms, Massimo = 17ms, Medio = 11ms ------------------------------------------------------------ C:\Windows\system32>ping jay3.clan-fa.com -n 30 Numero Ip : 178.63.72.170 Nazione : Germany Host Name : static.170.72.63.178.clients.your-server.de Esecuzione di Ping jay3.clan-fa.com [178.63.72.170] con 32 byte di dati: Risposta da 178.63.72.170: byte=32 durata=39ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=37ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=37ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=37ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=56ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=37ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=39ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=37ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=37ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=37ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=37ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=46ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.170: byte=32 durata=37ms TTL=117 Statistiche Ping per 178.63.72.170: Pacchetti: Trasmessi = 30, Ricevuti = 30, Persi = 0 (0% persi), Tempo approssimativo percorsi andata/ritorno in millisecondi: Minimo = 37ms, Massimo = 56ms, Medio = 38ms ------------------------------------------------------------ C:\Windows\system32>ping 8.9.4.227 -n 30 Numero Ip : 8.9.4.227 Nazione : United States Citta : Sayreville Esecuzione di Ping 8.9.4.227 con 32 byte di dati: Risposta da 8.9.4.227: byte=32 durata=158ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=157ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=158ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=157ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=158ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=158ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=157ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=158ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=158ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=165ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=162ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=161ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=157ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=158ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=158ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=158ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=161ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=207ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=158ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=159ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=157ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=173ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=158ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=157ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=157ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=157ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=159ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=157ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=157ms TTL=50 Risposta da 8.9.4.227: byte=32 durata=158ms TTL=50 Statistiche Ping per 8.9.4.227: Pacchetti: Trasmessi = 30, Ricevuti = 30, Persi = 0 (0% persi), Tempo approssimativo percorsi andata/ritorno in millisecondi: Minimo = 157ms, Massimo = 207ms, Medio = 160ms -------------------------------------------------------------- C:\Windows\system32>ping 178.63.72.175 -n 30 Numero Ip : 178.63.72.175 Host Name : static.175.72.63.178.clients.your-server.de Esecuzione di Ping 178.63.72.175 con 32 byte di dati: Risposta da 178.63.72.175: byte=32 durata=39ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=37ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=39ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=37ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=37ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=37ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=37ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=37ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=39ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=39ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=37ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=37ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=37ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=39ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=39ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=38ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=37ms TTL=117 Richiesta scaduta. Risposta da 178.63.72.175: byte=32 durata=39ms TTL=117 Risposta da 178.63.72.175: byte=32 durata=38ms TTL=117 Richiesta scaduta. Richiesta scaduta. Risposta da 178.63.72.175: byte=32 durata=38ms TTL=117 Statistiche Ping per 178.63.72.175: Pacchetti: Trasmessi = 30, Ricevuti = 27, Persi = 3 (10% persi), Tempo approssimativo percorsi andata/ritorno in millisecondi: Minimo = 37ms, Massimo = 39ms, Medio = 37ms ----------------------------------------------------------- C:\Windows\system32>ping www.tim.it -n 30 Esecuzione di Ping tim.it [156.54.69.9] con 32 byte di dati: Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=22ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=22ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=24ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=22ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=24ms TTL=242 Statistiche Ping per 156.54.69.9: Pacchetti: Trasmessi = 30, Ricevuti = 30, Persi = 0 (0% persi), Tempo approssimativo percorsi andata/ritorno in millisecondi: Minimo = 20ms, Massimo = 24ms, Medio = 20ms ---------------------------------------------------------------------- C:\Windows\system32>ping www.tim.it -n 30 Numero Ip : 156.54.69.9 Nazione : Italy Citta : Host Name : 156.54.69.9 Esecuzione di Ping tim.it [156.54.69.9] con 32 byte di dati: Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=22ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=22ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=24ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=22ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=20ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=21ms TTL=242 Risposta da 156.54.69.9: byte=32 durata=24ms TTL=242 Statistiche Ping per 156.54.69.9: Pacchetti: Trasmessi = 30, Ricevuti = 30, Persi = 0 (0% persi), Tempo approssimativo percorsi andata/ritorno in millisecondi: Minimo = 20ms, Massimo = 24ms, Medio = 20ms ------------------------------------------------------------------------ C:\Windows\system32>ping maya.ngi.it -n 30 Numero Ip : 88.149.202.248 Nazione : Italy Host Name : 88-149-202-248.v4.ngi.it Esecuzione di Ping test.ngi.it [88.149.202.248] con 32 byte di dati: Risposta da 88.149.202.248: byte=32 durata=13ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=12ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=12ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=15ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=14ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=12ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=11ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=11ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=11ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=11ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=12ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=11ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=12ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=12ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=11ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=11ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=19ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=11ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=12ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=12ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=13ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=12ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=11ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=12ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=11ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=11ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=12ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=12ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=11ms TTL=55 Risposta da 88.149.202.248: byte=32 durata=12ms TTL=55 Statistiche Ping per 88.149.202.248: Pacchetti: Trasmessi = 30, Ricevuti = 30, Persi = 0 (0% persi), Tempo approssimativo percorsi andata/ritorno in millisecondi: Minimo = 11ms, Massimo = 19ms, Medio = 12ms ----------------------------------------------------------------- C:\Windows\system32>tracert jay3.clan-fa.com Traccia instradamento verso jay3.clan-fa.com [178.63.72.170] su un massimo di 30 punti di passaggio: 1 1 ms <1 ms 1 ms modemtim.homenet.telecomitalia.it [192.168.1.1] 2 * * * Richiesta scaduta. 3 7 ms 7 ms 7 ms 172.17.177.49 4 10 ms 7 ms 9 ms 172.17.176.57 5 13 ms 13 ms 14 ms 172.19.241.254 6 11 ms * * 93.186.128.233 7 22 ms 17 ms 23 ms ae20.milano51.mil.seabone.net [195.22.205.13] 8 13 ms 12 ms 11 ms 93.186.128.157 9 36 ms 36 ms 38 ms ae-11.r01.mlanit01.it.bb.gin.ntt.net [129.250.2.40] 10 49 ms 49 ms 48 ms ae-2.r24.frnkge08.de.bb.gin.ntt.net [129.250.3.183] 11 40 ms 34 ms 33 ms ae-13.r03.frnkge03.de.bb.gin.ntt.net [129.250.6.207] 12 34 ms 34 ms 33 ms 213.198.82.130 13 38 ms 37 ms 37 ms core22.fsn1.hetzner.com [213.239.245.178] 14 38 ms 37 ms 37 ms ex9k2.rz12.hetzner.de [213.239.229.246] 15 38 ms 37 ms 37 ms static.170.72.63.178.clients.your-server.de [178.63.72.170] --------------------------------------------------------------------------------- Edited June 1, 2017 by JirenTV Quote
Guest Posted June 6, 2018 Posted June 6, 2018 (edited) WinMTR of today just restarted the modem, 30 minutes ago Edited June 6, 2018 by Cquattro 1 Quote
DFighter Posted June 6, 2018 Posted June 6, 2018 the packet loss starts already at your side from your pc to router Quote
Guest Posted June 6, 2018 Posted June 6, 2018 (edited) si, ma solo oggi e ho appena riavviato, sia il computer che il router la linea fa schifo tutti i giorni dalle 17.00 in poi (ora italiana) ma speedtest non lo trova come sempre devo andare all'appartamento di sopra e resettare il router di fabbrica e funzionerà circa 24 ore I'm happy because I received the call from my ISP, confirmation has arrived that on Wednesday June 13th they put me in this apartment if there are no problems my line will be "200MB down" and "40MB up" and this time with ethernet cable, I am so disheartened, it is 1 year and a half that I play in WI-FI with all these problems. will I be able to break everyone's ass now? Edited June 6, 2018 by Cquattro Quote
Veraudinus* Posted June 11, 2018 Posted June 11, 2018 (edited) Hello, i have everytime lags is some chance to change it ? :/ |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 84.116.254.140 - 63 | 1799 | 682 | 6828 | 1613 | 11125 | 7531 | | pl-ktw01a-rc1-ae18-0.aorta.net - 0 | 1799 | 1799 | 15 | 33 | 78 | 31 | | pl-waw26b-rc1-ae40-0.aorta.net - 0 | 1799 | 1799 | 15 | 32 | 78 | 31 | | pl-waw02a-ri1-ae18-0.aorta.net - 0 | 1799 | 1799 | 15 | 30 | 63 | 16 | | 213.46.178.54 - 0 | 1799 | 1799 | 15 | 33 | 110 | 32 | | xe-5-0-1.cr0-nyc6.ip4.gtt.net - 1 | 1799 | 1798 | 140 | 146 | 250 | 140 | | as20473-gw.nyc60.ip4.gtt.net - 0 | 1799 | 1799 | 140 | 148 | 203 | 156 | | vl41-br1.pnj1.choopa.net - 1 | 1799 | 1786 | 140 | 152 | 266 | 157 | | vl55-c11-1-b2-1.pnj1.choopa.net - 0 | 1799 | 1799 | 140 | 149 | 375 | 156 | | No response from host - 100 | 1799 | 0 | 0 | 0 | 0 | 0 | | 8.9.4.227 - 1 | 1798 | 1793 | 140 | 146 | 172 | 141 | |________________________________________________|______|______|______|______|______|______| WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( stanimir@cr.nivis.com ) Edited June 11, 2018 by Veraudinus* Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.