World of Warcraft: ständige Lags und Disconnects bei super Ping

Question

Hey ich habe eigentlich eine top Verbindung und bei wow einen 14ms Ping. Trotzdem habe ich zu jeder Tageszeit ständig mal lags oder disconnects. Mein Discord funktioniert in der Zeit und auch der Browser lässt Seiten öffnen. Es ist einzig WoW. Ich kann dann auch sofort wieder neu einloggen:Ich habe VDSL 100 bei der Telekom.Hier meine Ergebnisse fürs Pathing usw von den Blizzard Tipps und Tools: Tracing der 3 Blizzard EU Ips:Routenverfolgung zu 185.60.112.157 &#129;ber maximal 30 Hops1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]2 6 ms 5 ms 4 ms p3e9bf306.dip0.t-ipconnect. de [62.155.243.6]3 11 ms 10 ms 10 ms 217.5.117.1334 11 ms 10 ms 10 ms 62.157.248.745 24 ms 17 ms 16 ms ae1-br01-eqfr5.as57976. net [137.221.80.33]6 * * * Zeit&#129;berschreitung der Anforderung.7 2152 ms 2338 ms 2460 ms 137.221.65.758 16 ms 14 ms 14 ms 137.221.78.479 15 ms 14 ms 14 ms 185.60.112.157Ablaufverfolgung beendet. Routenverfolgung zu 185.60.112.158 &#129;ber maximal 30 Hops1 <1 ms <1 ms 1 ms fritz.box [192.168.178.1]2 6 ms 4 ms 4 ms p3e9bf306.dip0.t-ipconnect. de [62.155.243.6]3 11 ms 11 ms 10 ms f-eh1-i.F.DE.NET. DTAG . DE [62.154.4.189]4 11 ms 9 ms 10 ms 62.157.248.745 18 ms 17 ms 17 ms ae1-br01-eqfr5.as57976. net [137.221.80.33]6 * * * Zeit&#129;berschreitung der Anforderung.7 * * * Zeit&#129;berschreitung der Anforderung.8 15 ms 13 ms 14 ms 137.221.78.479 16 ms 14 ms 14 ms 137.221.66.4110 16 ms 14 ms 14 ms 185.60.112.158Ablaufverfolgung beendet. Routenverfolgung zu 185.60.114.159 &#129;ber maximal 30 Hops1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]2 6 ms 4 ms 5 ms p3e9bf306.dip0.t-ipconnect. de [62.155.243.6]3 3253 ms 9 ms 10 ms 62.159.98.814 45 ms 77 ms 10 ms 62.157.248.745 21 ms 24 ms 21 ms 137.221.80.356 253 ms 141 ms 63 ms et-0-0-2-br01-eqpa4.as57976 .net [137.221.65.26]7 80 ms 19 ms 20 ms et-0-0-0-pe04-eqpa4.as57976. net [137.221.77.51]8 20 ms 20 ms 20 ms 137.221.66.399 22 ms 20 ms 20 ms 185.60.114.159Ablaufverfolgung beendet. Pathing der 3 Blizzard EU Ips: Routenverfolgung zu '185.60.112.157' &#129;ber maximal 30 Hops0 DESKTOP-1AVINC3.fritz.box [192.168.178.21]1 fritz.box [192.168.178.1]2 p3e9bf306.dip0.t-ipconnect. de [62.155.243.6]3 217.5.117.1334 62.157.248.745 ae1-br01-eqfr5.as57976. net [137.221.80.33]6 * * *Berechnung der Statistiken dauert ca. 125 Sekunden...Quelle zum Abs. Knoten/VerbindungAbs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse0 DESKTOP-1AVINC3.fritz.box [192.168.178.21]0/ 100 = 0% |1 0ms 0/ 100 = 0% 0/ 100 = 0% fritz.box [192.168.178.1]45/ 100 = 45% |2 --- 100/ 100 =100% 55/ 100 = 55% p3e9bf306.dip0.t-ipconnect. de [62.155.243.6]0/ 100 = 0% |3 --- 100/ 100 =100% 55/ 100 = 55% 217.5.117.1330/ 100 = 0% |4 --- 100/ 100 =100% 55/ 100 = 55% 62.157.248.740/ 100 = 0% |5 433ms 45/ 100 = 45% 0/ 100 = 0% ae1-br01-eqfr5.as57976. net [137.221.80.33]Ablaufverfolgung beendet. Routenverfolgung zu '185.60.112.158' &#129;ber maximal 30 Hops0 DESKTOP-1AVINC3.fritz.box [192.168.178.21]1 fritz.box [192.168.178.1]2 p3e9bf306.dip0.t-ipconnect. de [62.155.243.6]3 f-eh1-i.F.DE.NET. DTAG . DE [62.154.4.189]4 62.157.248.745 ae1-br01-eqfr5.as57976. net [137.221.80.33]6 * * *Berechnung der Statistiken dauert ca. 125 Sekunden...Quelle zum Abs. Knoten/VerbindungAbs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse0 DESKTOP-1AVINC3.fritz.box [192.168.178.21]0/ 100 = 0% |1 0ms 0/ 100 = 0% 0/ 100 = 0% fritz.box [192.168.178.1]43/ 100 = 43% |2 --- 100/ 100 =100% 57/ 100 = 57% p3e9bf306.dip0.t-ipconnect. de [62.155.243.6]0/ 100 = 0% |3 --- 100/ 100 =100% 57/ 100 = 57% f-eh1-i.F.DE.NET. DTAG . DE [62.154.4.189]0/ 100 = 0% |4 --- 100/ 100 =100% 57/ 100 = 57% 62.157.248.740/ 100 = 0% |5 370ms 43/ 100 = 43% 0/ 100 = 0% ae1-br01-eqfr5.as57976. net [137.221.80.33]Ablaufverfolgung beendet. Routenverfolgung zu '185.60.114.159' &#129;ber maximal 30 Hops0 DESKTOP-1AVINC3.fritz.box [192.168.178.21]1 fritz.box [192.168.178.1]2 p3e9bf306.dip0.t-ipconnect. de [62.155.243.6]3 62.159.98.814 62.157.248.745 137.221.80.356 et-0-0-2-br01-eqpa4.as57976. net [137.221.65.26]7 et-0-0-0-pe04-eqpa4.as57976 .net [137.221.77.51]8 137.221.66.399 185.60.114.159Berechnung der Statistiken dauert ca. 225 Sekunden...Quelle zum Abs. Knoten/VerbindungAbs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse0 DESKTOP-1AVINC3.fritz.box [192.168.178.21]0/ 100 = 0% |1 0ms 0/ 100 = 0% 0/ 100 = 0% fritz.box [192.168.178.1]0/ 100 = 0% |2 --- 100/ 100 =100% 100/ 100 =100% p3e9bf306.dip0.t-ipconnect. de [62.155.243.6]0/ 100 = 0% |3 --- 100/ 100 =100% 100/ 100 =100% 62.159.98.810/ 100 = 0% |4 --- 100/ 100 =100% 100/ 100 =100% 62.157.248.740/ 100 = 0% |5 20ms 0/ 100 = 0% 0/ 100 = 0% 137.221.80.350/ 100 = 0% |6 26ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-2-br01-eqpa4.as57976. net [137.221.65.26]0/ 100 = 0% |7 27ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-0-pe04-eqpa4.as57976. net [137.221.77.51]0/ 100 = 0% |8 --- 100/ 100 =100% 100/ 100 =100% 137.221.66.390/ 100 = 0% |9 20ms 0/ 100 = 0% 0/ 100 = 0% 185.60.114.159Ablaufverfolgung beendet. Looking Glass Analyse von BlizzardTRACEROUTE:traceroute to 217.89.0.132 (217.89.0.132), 15 hops max, 60 byte packets1 Blizzard Blizzard 3.503 ms 3.492 ms 3.490 ms2 37.244.24.131 (37.244.24.131) 4.933 ms 5.083 ms 5.282 ms3 Blizzard Blizzard 4.127 ms 4.126 ms 4.125 ms4 137.221.66.40 (137.221.66.40) 4.089 ms 4.100 ms 4.100 ms5 137.221.78.46 (137.221.78.46) 103.739 ms 103.756 ms 103.760 ms6 * * *7 137.221.78.32 (137.221.78.32) 1.214 ms 1.233 ms 1.233 ms8 80.156.162.85 (80.156.162.85) 266.382 ms 266.430 ms 266.582 ms9 p5b17d829.dip0.t-ipconnect. de (91.23.216.41) 12.049 ms 12.110 ms 12.122 ms10 pd9590084.dip0.t-ipconnect. de (217.89.0.132) 16.662 ms 16.670 ms 17.048 ms18/12/2020 11:01:28 UTC--------------------PING:PING 217.89.0.132 (217.89.0.132) 56(84) bytes of data.64 bytes from 217.89.0.132: icmp_seq=1 ttl=54 time=16.5 ms64 bytes from 217.89.0.132: icmp_seq=3 ttl=54 time=16.9 ms64 bytes from 217.89.0.132: icmp_seq=4 ttl=54 time=16.0 ms--- 217.89.0.132 ping statistics ---4 packets transmitted, 3 received, 25% packet loss, time 2999msrtt min/avg/max/mdev = 16.090/16.527/16.921/0.356 ms18/12/2020 11:01:28 UTC--------------------TRACEROUTE:traceroute to 217.89.0.132 (217.89.0.132), 15 hops max, 60 byte packets1 Blizzard Blizzard 0.330 ms 0.334 ms 0.336 ms2 37.244.24.131 (37.244.24.131) 0.899 ms 0.903 ms 1.015 ms3 Blizzard Blizzard 0.890 ms 0.896 ms 0.897 ms4 137.221.66.40 (137.221.66.40) 0.814 ms 0.831 ms 0.834 ms5 137.221.78.46 (137.221.78.46) 214.363 ms 214.410 ms 214.700 ms6 * * *7 137.221.78.32 (137.221.78.32) 1.099 ms 1.117 ms 1.118 ms8 80.156.162.85 (80.156.162.85) 160.819 ms 156.740 ms 156.827 ms9 p5b17d829.dip0.t-ipconnect. de (91.23.216.41) 12.186 ms 12.229 ms 12.258 ms10 * * *11 * * *12 * * *13 * * *14 * * *15 * * *18/12/2020 11:01:28 UTC--------------------PING:PING 217.89.0.132 (217.89.0.132) 56(84) bytes of data.--- 217.89.0.132 ping statistics ---4 packets transmitted, 0 received, 100% packet loss, time 3007ms 18/12/2020 11:01:28 UTC--------------------TRACEROUTE:traceroute to 217.89.0.132 (217.89.0.132), 15 hops max, 60 byte packets1 Blizzard Blizzard 0.307 ms 0.308 ms 0.311 ms2 37.244.24.131 (37.244.24.131) 0.932 ms 0.964 ms 1.003 ms3 Blizzard Blizzard 0.930 ms 0.934 ms 0.937 ms4 137.221.66.40 (137.221.66.40) 0.860 ms 0.878 ms 0.883 ms5 137.221.78.46 (137.221.78.46) 118.545 ms 118.549 ms 118.558 ms6 * * *7 137.221.78.32 (137.221.78.32) 1.206 ms 1.207 ms 1.207 ms8 80.156.162.85 (80.156.162.85) 1.162 ms 1.055 ms 1.045 ms9 p5b17d829.dip0.t-ipconnect. de (91.23.216.41) 12.253 ms 12.303 ms 12.333 ms10 pd9590084.dip0.t-ipconnect. de (217.89.0.132) 17.149 ms * *18/12/2020 11:01:32 UTC--------------------PING:PING 217.89.0.132 (217.89.0.132) 56(84) bytes of data.--- 217.89.0.132 ping statistics ---4 packets transmitted, 0 received, 100% packet loss, time 2999ms 18/12/2020 11:01:32 UTC--------------------TRACEROUTE:traceroute to 217.89.0.132 (217.89.0.132), 15 hops max, 60 byte packets1 Blizzard Blizzard 0.315 ms 0.301 ms 0.300 ms2 37.244.25.2 (37.244.25.2) 1.538 ms 1.712 ms 1.907 ms3 Blizzard Blizzard 1.086 ms * 1.082 ms4 137.221.66.34 (137.221.66.34) 1.052 ms 1.057 ms 1.058 ms5 137.221.77.82 (137.221.77.82) 1.022 ms 1.038 ms 1.036 ms6 137.221.77.34 (137.221.77.34) 1.034 ms 1.111 ms 1.059 ms7 80.157.202.37 (80.157.202.37) 1.020 ms 1.062 ms 1.155 ms8 p5b17d701.dip0.t-ipconnect. de (91.23.215.1) 15.761 ms 15.778 ms 15.775 ms9 * * *10 * * *11 * * *12 * * *13 * * *14 * * *15 * * *18/12/2020 11:01:34 UTC--------------------PING:PING 217.89.0.132 (217.89.0.132) 56(84) bytes of data.--- 217.89.0.132 ping statistics ---4 packets transmitted, 0 received, 100% packet loss, time 2998ms 18/12/2020 11:01:37 UTC--------------------MTR:Start: Fri Dec 18 11:01:28 2020 Blizzard 1.|-- Blizzard 0.0% 10 2.1 0.8 0.2 3.2 0.92.|-- 37.244.24.131 0.0% 10 0.6 1.4 0.5 5.5 1.53.|-- Blizzard 0.0% 10 0.7 0.8 0.7 1.2 0.04.|-- 137.221.66.40 0.0% 10 0.4 4.4 0.4 39.5 12.35.|-- 137.221.78.46 0.0% 10 28.6 198.5 16.5 577.8 180.96.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.07.|-- 137.221.78.32 0.0% 10 1.3 13.7 0.9 50.8 20.78.|-- 80.156.162.85 0.0% 10 1.2 34.4 0.9 208.0 72.79.|-- p5b17d829.dip0.t-ipconnect. de 0.0% 10 12.1 12.2 12.1 12.4 0.010.|-- pd9590084.dip0.t-ipconnect. de 90.0% 10 16.3 16.3 16.3 16.3 0.018/12/2020 11:01:28 UTC--------------------MTR:Start: Fri Dec 18 11:01:28 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.5 0.02.|-- 37.244.24.131 0.0% 10 0.7 0.7 0.6 0.9 0.03.|-- Blizzard 0.0% 10 0.7 0.8 0.7 0.9 0.04.|-- 137.221.66.40 0.0% 10 0.6 13.5 0.4 129.4 40.85.|-- 137.221.78.46 0.0% 10 128.9 118.7 37.8 219.7 54.26.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.07.|-- 137.221.78.32 0.0% 10 11.9 2.2 1.0 11.9 3.48.|-- 80.156.162.85 0.0% 10 15.6 43.6 1.0 329.9 103.89.|-- p5b17d829.dip0.t-ipconnect. de 0.0% 10 12.0 12.1 12.0 12.2 0.010.|-- pd9590084.dip0.t-ipconnect. de 90.0% 10 16.9 16.9 16.9 16.9 0.018/12/2020 11:01:28 UTC--------------------MTR:Start: Fri Dec 18 11:01:30 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.02.|-- 37.244.24.131 0.0% 10 0.9 0.8 0.6 1.3 0.03.|-- Blizzard 0.0% 10 0.7 0.8 0.7 1.0 0.04.|-- 137.221.66.40 0.0% 10 0.9 10.4 0.4 53.9 20.95.|-- 137.221.78.46 0.0% 10 9.8 180.1 9.8 537.6 170.76.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.07.|-- 137.221.78.32 0.0% 10 0.9 3.3 0.9 22.5 6.78.|-- 80.156.162.85 0.0% 10 1.1 1.1 1.0 1.3 0.09.|-- p5b17d829.dip0.t-ipconnect. de 0.0% 10 12.0 13.1 12.0 19.9 2.410.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.018/12/2020 11:01:30 UTC--------------------TRACEROUTE:traceroute to 217.89.0.132 (217.89.0.132), 15 hops max, 60 byte packets1 Blizzard Blizzard 0.354 ms 0.340 ms 0.340 ms2 37.244.25.130 (37.244.25.130) 1.348 ms 1.348 ms 1.347 ms3 Blizzard Blizzard 0.855 ms 0.927 ms 0.944 ms4 137.221.66.32 (137.221.66.32) 1.285 ms 1.305 ms 1.304 ms5 137.221.77.76 (137.221.77.76) 50.052 ms 50.076 ms 50.075 ms6 137.221.77.32 (137.221.77.32) 3.812 ms 0.976 ms 0.947 ms7 80.157.202.37 (80.157.202.37) 1.131 ms 1.232 ms 1.299 ms8 p5b17d829.dip0.t-ipconnect. de (91.23.216.41) 15.429 ms 15.447 ms 15.443 ms9 * * *10 * * *11 * * *12 * * *13 * * *14 * * *15 * * *18/12/2020 11:01:42 UTC--------------------PING:PING 217.89.0.132 (217.89.0.132) 56(84) bytes of data.64 bytes from 217.89.0.132: icmp_seq=2 ttl=55 time=19.9 ms--- 217.89.0.132 ping statistics ---4 packets transmitted, 1 received, 75% packet loss, time 2998msrtt min/avg/max/mdev = 19.981/19.981/19.981/0.000 ms18/12/2020 11:01:43 UTC--------------------MTR:Start: Fri Dec 18 11:01:33 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 0.5 0.02.|-- 37.244.25.2 0.0% 10 0.8 0.7 0.6 1.0 0.03.|-- Blizzard 0.0% 10 1.0 1.1 0.8 2.9 0.64.|-- 137.221.66.34 0.0% 10 0.4 3.1 0.4 26.1 8.15.|-- 137.221.77.82 0.0% 10 15.5 8.3 0.7 56.7 17.66.|-- 137.221.77.34 0.0% 10 1.0 4.4 0.9 27.1 8.37.|-- 80.157.202.37 0.0% 10 1.2 68.0 1.0 383.8 130.78.|-- p5b17d701.dip0.t-ipconnect. de 0.0% 10 15.6 15.6 15.4 16.2 0.09.|-- pd9590084.dip0.t-ipconnect. de 40.0% 10 20.1 20.0 19.5 20.3 0.018/12/2020 11:01:33 UTC--------------------TRACEROUTE:traceroute to 217.89.0.132 (217.89.0.132), 15 hops max, 60 byte packets1 Blizzard Blizzard 0.502 ms 0.506 ms 0.512 ms2 37.244.25.130 (37.244.25.130) 0.785 ms 0.882 ms 1.043 ms3 Blizzard Blizzard 1.714 ms 1.740 ms 1.734 ms4 137.221.66.32 (137.221.66.32) 0.600 ms 0.640 ms 0.646 ms5 137.221.77.76 (137.221.77.76) 1.719 ms 1.721 ms 1.722 ms6 137.221.77.32 (137.221.77.32) 0.960 ms 1.023 ms 1.553 ms7 80.157.202.37 (80.157.202.37) 1.146 ms 1.225 ms 1.276 ms8 p5b17d829.dip0.t-ipconnect. de (91.23.216.41) 15.347 ms 15.417 ms 15.402 ms9 * * *10 * * *11 * * *12 * * *13 * * *14 * * *15 * * *18/12/2020 11:01:46 UTC--------------------PING:PING 217.89.0.132 (217.89.0.132) 56(84) bytes of data.--- 217.89.0.132 ping statistics ---4 packets transmitted, 0 received, 100% packet loss, time 3000ms 18/12/2020 11:01:46 UTC--------------------MTR:Start: Fri Dec 18 11:01:38 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 1.5 0.3 11.5 3.52.|-- 37.244.25.130 0.0% 10 1.0 1.0 0.6 1.6 0.03.|-- Blizzard 0.0% 10 1.1 1.0 0.8 1.1 0.04.|-- 137.221.66.32 0.0% 10 0.8 1.1 0.5 5.1 1.45.|-- 137.221.77.76 0.0% 10 1.0 14.7 0.8 126.8 39.56.|-- 137.221.77.32 0.0% 10 1.2 5.6 0.9 46.6 14.47.|-- 80.157.202.37 0.0% 10 1.2 46.1 1.1 318.7 104.28.|-- p5b17d829.dip0.t-ipconnect. de 0.0% 10 15.5 15.8 15.4 18.2 0.89.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.010.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.011.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.012.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.013.|-- pd9590084.dip0.t-ipconnect. de 70.0% 10 20.3 20.1 19.9 20.3 0.018/12/2020 11:01:38 UTC--------------------MTR:Start: Fri Dec 18 11:01:43 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 0.5 0.02.|-- 37.244.25.130 0.0% 10 0.7 0.8 0.7 1.0 0.03.|-- Blizzard 0.0% 10 1.0 0.9 0.8 1.0 0.04.|-- 137.221.66.32 0.0% 10 0.8 2.9 0.4 12.6 4.75.|-- 137.221.77.76 0.0% 10 0.9 22.9 0.8 121.5 37.36.|-- 137.221.77.32 0.0% 10 1.0 1.9 0.9 8.9 2.47.|-- 80.157.202.37 0.0% 10 1.3 39.9 1.1 291.4 93.58.|-- p5b17d829.dip0.t-ipconnect. de 0.0% 10 15.5 16.7 15.4 24.9 2.99.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.010.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.011.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.012.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.013.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.014.|-- pd9590084.dip0.t-ipconnect .de 10.0% 10 20.2 20.1 19.8 20.6 0.018/12/2020 11:01:43 UTC--------------------

ex2j · Accepted Answer

Nach dem ich unter Netzwerkeinstellungen im Spiel IPv6 deaktiviert habe, traten keine Probleme mehr auf

Neuauftrag Telekom Disney+

Neuauftrag

Disney+ bei Telekom

Disney + als Kunde von Disney+ trotsdem noch Telekom Disney+ aktivieren?

Disney+ by Telekom trotz Kündigung

Telekom Disney+ Option

Das könnte Sie auch interessieren

Kaufberatung anfragen

Angebote anzeigen

Social Media