es lagt nun auch extrem in den Vision und M+ …nicht wie sonst immer in Boralus ,Pandaria,Uldum etc
gerade m+ gemacht ^^ war schon lustig .
gibts da irgendwie was von seiten blizzard?
es lagt nun auch extrem in den Vision und M+ …nicht wie sonst immer in Boralus ,Pandaria,Uldum etc
gerade m+ gemacht ^^ war schon lustig .
gibts da irgendwie was von seiten blizzard?
Das kann ich bestätigen.
High Ping und auffallende lags in Dungeons.
lg
Hab das selbe Problem T_T .
Bei mir lagt es auch, Latenz steigt immer wieder über 100
Seit heute morgen ist die Weltlatenz deutlicher höher wie sonst.
Entweder ist also auf dem Weg zu den Blizzard Servern was nicht in Ordnung oder bei Blizzard selbst.
Auf Twitter scheint Blizzard davon aber auch noch nichts mitbekommen zu haben.
Blizzard bekommt das nie mit, weil nach deren Ansicht immer alle anderen Schuld sind, und niemals sie selbst…
ach und weils sowieso nach gefragt wird…
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 100 | 100 | 0 | 0 | 3 | 0 |
| 100.68.128.1 - 0 | 100 | 100 | 1 | 1 | 7 | 1 |
| 100.127.1.13 - 0 | 100 | 100 | 5 | 5 | 13 | 5 |
| 185.22.46.72 - 0 | 100 | 100 | 6 | 6 | 13 | 6 |
| ae100.edge5.Dusseldorf1.Level3.net - 0 | 100 | 100 | 5 | 7 | 26 | 6 |
| ae-1-3104.edge7.Amsterdam1.Level3.net - 3 | 92 | 90 | 9 | 13 | 33 | 13 |
| BLIZZARD-EN.edge7.Amsterdam1.Level3.net - 0 | 100 | 100 | 11 | 14 | 63 | 12 |
| ae1-br02-eqam1.as57976.net - 5 | 82 | 78 | 78 | 772 | 1274 | 701 |
| 137.221.78.85 - 5 | 84 | 80 | 9 | 27 | 74 | 74 |
| 137.221.66.43 - 5 | 84 | 80 | 0 | 28 | 42 | 40 |
| 185.60.112.157 - 10 | 74 | 67 | 0 | 26 | 44 | 15 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)
Kann es bestätigen lagt auch in der Arena Bgs etc jenseits der 100 knapp 200 world
Ebenso bei mir. Ganzen Mittag schon Weltlatenz über 100 bis zu 2000
Äußerung ohne WinMTR ( was in der regel der fall ist… leider ) bringen halt keine Daten und es ist kostensparender, wenn erstmal der Kunde seine Probleme ausschließt.
Aber dein WinMTR ist eindeutig und bei mir schaut das ähnlich aus.
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 0 | 10 | 10 | 0 | 0 | 0 | 0 | | 100.68.128.1 - 0 | 10 | 10 | 1 | 1 | 2 | 1 | | 100.127.1.13 - 0 | 10 | 10 | 5 | 5 | 6 | 5 | | 185.22.46.72 - 17 | 6 | 5 | 6 | 6 | 6 | 6 | | ae100.edge5.Dusseldorf1.Level3.net - 0 | 10 | 10 | 6 | 6 | 10 | 6 | | ae-1-3104.edge7.Amsterdam1.Level3.net - 0 | 10 | 10 | 9 | 13 | 29 | 29 | | BLIZZARD-EN.edge7.Amsterdam1.Level3.net - 0 | 10 | 10 | 11 | 13 | 31 | 11 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | et-0-0-35-pe02-eqam1.as57976.net - 0 | 10 | 10 | 9 | 25 | 53 | 9 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | |________________________________________________|______|______|______|______|______|______| WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)
Tjo, wenn es so einfach wäre hier die WinMTR zu posten aber angeblich stören da irgendwelche Links immer wieder mal…
WinMTR Statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
192.168.1.1 | 0 | 15 | 15 | 0 | 0 | 0 | 0 |
100.68.128.1 | 0 | 15 | 15 | 1 | 1 | 2 | 1 |
100.127.1.13 | 0 | 15 | 15 | 5 | 5 | 6 | 5 |
185.22.46.72 | 0 | 15 | 15 | 6 | 6 | 7 | 6 |
ae100.edge5.Dusseldorf1.Level3.net | 0 | 15 | 15 | 6 | 8 | 35 | 6 |
ae-1-3104.edge7.Amsterdam1.Level3.net | 0 | 15 | 15 | 9 | 10 | 23 | 9 |
BLIZZARD-EN.edge7.Amsterdam1.Level3.net | 0 | 15 | 15 | 11 | 13 | 38 | 11 |
ae1-br02-eqam1.as57976.net | 10 | 11 | 10 | 816 | 1014 | 1100 | 1100 |
137.221.78.85 | 0 | 15 | 15 | 9 | 29 | 87 | 9 |
185.60.112.158 | 0 | 15 | 15 | 11 | 25 | 43 | 11 |
Ach ich hab da nochmal eine Erinnerung… ist nicht der erste MTR den ich poste wo genau der Punkt nach dem ersten Blizzard ärger macht… mal zur Erinnerung
Das mit Pandaria/Boralus musste sich Blizzard sowieso schon eingestehen aber scheint nicht so einfach gefixt zu werden, wenn das überhaupt noch vor SL passiert.
Du kannst mit dem </> gut dinge einfügen ohne dass wegen links gemeckert wird.
Kann die lags nur bestätigen.
Falls es was hilft, WinMTR für für 185.60.112.158:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| fritz.box - 0 | 169 | 169 | 0 | 0 | 7 | 0 |
| ber1005dihr001.versatel.de - 0 | 169 | 169 | 5 | 6 | 23 | 5 |
| 62.214.37.245 - 0 | 169 | 169 | 4 | 4 | 22 | 4 |
| 62.214.37.134 - 0 | 169 | 169 | 24 | 25 | 63 | 37 |
| pr01.eqfr5.blizzardonline.net - 0 | 169 | 169 | 19 | 23 | 95 | 20 |
| ae1-br01-eqfr5.as57976.net - 7 | 133 | 124 | 24 | 42 | 92 | 55 |
| et-0-0-2-br01-eqam1.as57976.net - 12 | 114 | 101 | 0 | 103 | 4793 | 101 |
| 137.221.78.79 - 6 | 137 | 129 | 23 | 41 | 95 | 54 |
| 137.221.66.45 - 5 | 142 | 135 | 26 | 43 | 63 | 58 |
| 185.60.112.158 - 7 | 135 | 126 | 26 | 42 | 59 | 57 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Mittwochs ist Lagday. Man sagt zwar mal sollte den nicht skippen, aber ich skippe den mittlerweile und mache die wichtigen Sachen Freitags
Microsoft Windows [Version 10.0.18363.815]
(c) 2019 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Windows\system32>pathping 185.60.114.159
Routenverfolgung zu "185.60.114.159" über maximal 30 Hops
0 DESKTOP-7TLN1UL.fritz.box [192.168.178.25]
1 fritz.box [192.168.178.1]
2 85.16.121.172
3 85.16.250.243
4 85.16.249.119
5 bbrt.ol-0-1-xe-3-2-0.ewe-ip-backbone.de [212.6.114.249]
6 bbrt.ffm-0-ae11.ewe-ip-backbone.de [212.6.114.38]
7 pr01.eqfr5.blizzardonline.net [80.81.195.26]
8 * 137.221.80.35
9 et-0-0-2-br01-eqpa4.as57976.net [137.221.65.26]
10 be1-pe1-eqpa4.as57976.net [137.221.77.67]
11 * * *
Berechnung der Statistiken dauert ca. 250 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 DESKTOP-7TLN1UL.fritz.box [192.168.178.25]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% fritz.box [192.168.178.1]
0/ 100 = 0% |
2 5ms 0/ 100 = 0% 0/ 100 = 0% 85.16.121.172
0/ 100 = 0% |
3 5ms 0/ 100 = 0% 0/ 100 = 0% 85.16.250.243
0/ 100 = 0% |
4 6ms 0/ 100 = 0% 0/ 100 = 0% 85.16.249.119
0/ 100 = 0% |
5 5ms 0/ 100 = 0% 0/ 100 = 0% bbrt.ol-0-1-xe-3-2-0.ewe-ip-backbone.de [212.6.114.249]
0/ 100 = 0% |
6 14ms 0/ 100 = 0% 0/ 100 = 0% bbrt.ffm-0-ae11.ewe-ip-backbone.de [212.6.114.38]
0/ 100 = 0% |
7 18ms 0/ 100 = 0% 0/ 100 = 0% pr01.eqfr5.blizzardonline.net [80.81.195.26]
0/ 100 = 0% |
8 38ms 7/ 100 = 7% 7/ 100 = 7% 137.221.80.35
0/ 100 = 0% |
9 31ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-2-br01-eqpa4.as57976.net [137.221.65.26]
100/ 100 =100% |
10 --- 100/ 100 =100% 0/ 100 = 0% be1-pe1-eqpa4.as57976.net [137.221.77.67]
Ablaufverfolgung beendet.
C:\Windows\system32>pathping 185.60.114.159
Routenverfolgung zu "185.60.114.159" über maximal 30 Hops
0 DESKTOP-7TLN1UL.fritz.box [192.168.178.25]
1 fritz.box [192.168.178.1]
2 85.16.121.172
3 85.16.250.243
4 85.16.249.119
5 bbrt.ol-0-1-xe-3-2-0.ewe-ip-backbone.de [212.6.114.249]
6 bbrt.ffm-0-ae11.ewe-ip-backbone.de [212.6.114.38]
7 pr01.eqfr5.blizzardonline.net [80.81.195.26]
8 137.221.80.35
9 et-0-0-2-br01-eqpa4.as57976.net [137.221.65.26]
10 be1-pe1-eqpa4.as57976.net [137.221.77.67]
11 * * *
Berechnung der Statistiken dauert ca. 250 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 DESKTOP-7TLN1UL.fritz.box [192.168.178.25]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% fritz.box [192.168.178.1]
0/ 100 = 0% |
2 4ms 0/ 100 = 0% 0/ 100 = 0% 85.16.121.172
0/ 100 = 0% |
3 4ms 0/ 100 = 0% 0/ 100 = 0% 85.16.250.243
0/ 100 = 0% |
4 5ms 0/ 100 = 0% 0/ 100 = 0% 85.16.249.119
0/ 100 = 0% |
5 5ms 0/ 100 = 0% 0/ 100 = 0% bbrt.ol-0-1-xe-3-2-0.ewe-ip-backbone.de [212.6.114.249]
0/ 100 = 0% |
6 14ms 0/ 100 = 0% 0/ 100 = 0% bbrt.ffm-0-ae11.ewe-ip-backbone.de [212.6.114.38]
0/ 100 = 0% |
7 18ms 0/ 100 = 0% 0/ 100 = 0% pr01.eqfr5.blizzardonline.net [80.81.195.26]
0/ 100 = 0% |
8 37ms 8/ 100 = 8% 8/ 100 = 8% 137.221.80.35
0/ 100 = 0% |
9 31ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-2-br01-eqpa4.as57976.net [137.221.65.26]
100/ 100 =100% |
10 --- 100/ 100 =100% 0/ 100 = 0% be1-pe1-eqpa4.as57976.net [137.221.77.67]
Ablaufverfolgung beendet.
C:\Windows\system32>pathping 185.60.114.159
Routenverfolgung zu "185.60.114.159" über maximal 30 Hops
0 DESKTOP-7TLN1UL.fritz.box [192.168.178.25]
1 fritz.box [192.168.178.1]
2 85.16.121.172
3 85.16.250.243
4 85.16.249.119
5 bbrt.ol-0-1-xe-3-2-0.ewe-ip-backbone.de [212.6.114.249]
6 bbrt.ffm-0-ae11.ewe-ip-backbone.de [212.6.114.38]
7 pr01.eqfr5.blizzardonline.net [80.81.195.26]
8 137.221.80.35
9 et-0-0-2-br01-eqpa4.as57976.net [137.221.65.26]
10 be1-pe1-eqpa4.as57976.net [137.221.77.67]
11 * * *
Berechnung der Statistiken dauert ca. 250 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 DESKTOP-7TLN1UL.fritz.box [192.168.178.25]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% fritz.box [192.168.178.1]
0/ 100 = 0% |
2 4ms 0/ 100 = 0% 0/ 100 = 0% 85.16.121.172
0/ 100 = 0% |
3 4ms 0/ 100 = 0% 0/ 100 = 0% 85.16.250.243
0/ 100 = 0% |
4 6ms 0/ 100 = 0% 0/ 100 = 0% 85.16.249.119
0/ 100 = 0% |
5 5ms 0/ 100 = 0% 0/ 100 = 0% bbrt.ol-0-1-xe-3-2-0.ewe-ip-backbone.de [212.6.114.249]
0/ 100 = 0% |
6 14ms 0/ 100 = 0% 0/ 100 = 0% bbrt.ffm-0-ae11.ewe-ip-backbone.de [212.6.114.38]
0/ 100 = 0% |
7 17ms 0/ 100 = 0% 0/ 100 = 0% pr01.eqfr5.blizzardonline.net [80.81.195.26]
0/ 100 = 0% |
8 35ms 3/ 100 = 3% 3/ 100 = 3% 137.221.80.35
0/ 100 = 0% |
9 32ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-2-br01-eqpa4.as57976.net [137.221.65.26]
100/ 100 =100% |
10 --- 100/ 100 =100% 0/ 100 = 0% be1-pe1-eqpa4.as57976.net [137.221.77.67]
Ablaufverfolgung beendet.
C:\Windows\system32>
Microsoft Windows [Version 10.0.18363.815]
(c) 2019 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Windows\system32>pathping 185.60.112.157
Routenverfolgung zu "185.60.112.157" über maximal 30 Hops
0 DESKTOP-7TLN1UL.fritz.box [192.168.178.25]
1 fritz.box [192.168.178.1]
2 85.16.121.172
3 85.16.250.240
4 85.16.249.117
5 bbrt.ol-1-1-xe-3-2-0.ewe-ip-backbone.de [80.228.90.86]
6 212.6.115.118
7 pr01.eqfr5.blizzardonline.net [80.81.195.26]
8 ae1-br01-eqfr5.as57976.net [137.221.80.33]
9 et-0-0-2-br01-eqam1.as57976.net [137.221.65.29]
10 137.221.78.79
11 185.60.112.157
Berechnung der Statistiken dauert ca. 275 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 DESKTOP-7TLN1UL.fritz.box [192.168.178.25]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% fritz.box [192.168.178.1]
0/ 100 = 0% |
2 5ms 0/ 100 = 0% 0/ 100 = 0% 85.16.121.172
0/ 100 = 0% |
3 5ms 0/ 100 = 0% 0/ 100 = 0% 85.16.250.240
0/ 100 = 0% |
4 6ms 0/ 100 = 0% 0/ 100 = 0% 85.16.249.117
0/ 100 = 0% |
5 6ms 0/ 100 = 0% 0/ 100 = 0% bbrt.ol-1-1-xe-3-2-0.ewe-ip-backbone.de [80.228.90.86]
0/ 100 = 0% |
6 9ms 0/ 100 = 0% 0/ 100 = 0% 212.6.115.118
0/ 100 = 0% |
7 16ms 0/ 100 = 0% 0/ 100 = 0% pr01.eqfr5.blizzardonline.net [80.81.195.26]
4/ 100 = 4% |
8 40ms 4/ 100 = 4% 0/ 100 = 0% ae1-br01-eqfr5.as57976.net [137.221.80.33]
4/ 100 = 4% |
9 40ms 9/ 100 = 9% 1/ 100 = 1% et-0-0-2-br01-eqam1.as57976.net [137.221.65.29]
0/ 100 = 0% |
10 39ms 8/ 100 = 8% 0/ 100 = 0% 137.221.78.79
1/ 100 = 1% |
11 37ms 9/ 100 = 9% 0/ 100 = 0% 185.60.112.157
Ablaufverfolgung beendet.
C:\Windows\system32>pathping 185.60.112.157
Routenverfolgung zu "185.60.112.157" über maximal 30 Hops
0 DESKTOP-7TLN1UL.fritz.box [192.168.178.25]
1 fritz.box [192.168.178.1]
2 85.16.121.172
3 85.16.250.240
4 85.16.249.117
5 bbrt.ol-1-1-xe-3-2-0.ewe-ip-backbone.de [80.228.90.86]
6 212.6.115.118
7 pr01.eqfr5.blizzardonline.net [80.81.195.26]
8 ae1-br01-eqfr5.as57976.net [137.221.80.33]
9 et-0-0-2-br01-eqam1.as57976.net [137.221.65.29]
10 137.221.78.79
11 185.60.112.157
Berechnung der Statistiken dauert ca. 275 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 DESKTOP-7TLN1UL.fritz.box [192.168.178.25]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% fritz.box [192.168.178.1]
0/ 100 = 0% |
2 4ms 0/ 100 = 0% 0/ 100 = 0% 85.16.121.172
0/ 100 = 0% |
3 5ms 0/ 100 = 0% 0/ 100 = 0% 85.16.250.240
0/ 100 = 0% |
4 6ms 0/ 100 = 0% 0/ 100 = 0% 85.16.249.117
0/ 100 = 0% |
5 6ms 0/ 100 = 0% 0/ 100 = 0% bbrt.ol-1-1-xe-3-2-0.ewe-ip-backbone.de [80.228.90.86]
0/ 100 = 0% |
6 9ms 0/ 100 = 0% 0/ 100 = 0% 212.6.115.118
0/ 100 = 0% |
7 15ms 0/ 100 = 0% 0/ 100 = 0% pr01.eqfr5.blizzardonline.net [80.81.195.26]
6/ 100 = 6% |
8 37ms 9/ 100 = 9% 3/ 100 = 3% ae1-br01-eqfr5.as57976.net [137.221.80.33]
0/ 100 = 0% |
9 38ms 7/ 100 = 7% 1/ 100 = 1% et-0-0-2-br01-eqam1.as57976.net [137.221.65.29]
0/ 100 = 0% |
10 37ms 6/ 100 = 6% 0/ 100 = 0% 137.221.78.79
1/ 100 = 1% |
11 37ms 7/ 100 = 7% 0/ 100 = 0% 185.60.112.157
Ablaufverfolgung beendet.
C:\Windows\system32>pathping 185.60.112.157
Routenverfolgung zu "185.60.112.157" über maximal 30 Hops
0 DESKTOP-7TLN1UL.fritz.box [192.168.178.25]
1 fritz.box [192.168.178.1]
2 85.16.121.172
3 85.16.250.240
4 85.16.249.117
5 bbrt.ol-1-1-xe-3-2-0.ewe-ip-backbone.de [80.228.90.86]
6 212.6.115.118
7 pr01.eqfr5.blizzardonline.net [80.81.195.26]
8 ae1-br01-eqfr5.as57976.net [137.221.80.33]
9 et-0-0-2-br01-eqam1.as57976.net [137.221.65.29]
10 137.221.78.79
11 185.60.112.157
Berechnung der Statistiken dauert ca. 275 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 DESKTOP-7TLN1UL.fritz.box [192.168.178.25]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% fritz.box [192.168.178.1]
0/ 100 = 0% |
2 4ms 0/ 100 = 0% 0/ 100 = 0% 85.16.121.172
0/ 100 = 0% |
3 5ms 0/ 100 = 0% 0/ 100 = 0% 85.16.250.240
0/ 100 = 0% |
4 6ms 0/ 100 = 0% 0/ 100 = 0% 85.16.249.117
0/ 100 = 0% |
5 6ms 0/ 100 = 0% 0/ 100 = 0% bbrt.ol-1-1-xe-3-2-0.ewe-ip-backbone.de [80.228.90.86]
0/ 100 = 0% |
6 9ms 0/ 100 = 0% 0/ 100 = 0% 212.6.115.118
0/ 100 = 0% |
7 17ms 0/ 100 = 0% 0/ 100 = 0% pr01.eqfr5.blizzardonline.net [80.81.195.26]
4/ 100 = 4% |
8 39ms 4/ 100 = 4% 0/ 100 = 0% ae1-br01-eqfr5.as57976.net [137.221.80.33]
0/ 100 = 0% |
9 38ms 10/ 100 = 10% 6/ 100 = 6% et-0-0-2-br01-eqam1.as57976.net [137.221.65.29]
0/ 100 = 0% |
10 37ms 5/ 100 = 5% 1/ 100 = 1% 137.221.78.79
0/ 100 = 0% |
11 35ms 4/ 100 = 4% 0/ 100 = 0% 185.60.112.157
Ablaufverfolgung beendet.
C:\Windows\system32>
Microsoft Windows [Version 10.0.18363.815]
(c) 2019 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Windows\system32>pathping 185.60.112.158
Routenverfolgung zu "185.60.112.158" über maximal 30 Hops
0 DESKTOP-7TLN1UL.fritz.box [192.168.178.25]
1 fritz.box [192.168.178.1]
2 85.16.121.172
3 85.16.250.240
4 85.16.249.117
5 bbrt.ol-1-1-xe-3-2-0.ewe-ip-backbone.de [80.228.90.86]
6 212.6.115.118
7 pr01.eqfr5.blizzardonline.net [80.81.195.26]
8 ae1-br01-eqfr5.as57976.net [137.221.80.33]
9 et-0-0-2-br01-eqam1.as57976.net [137.221.65.29]
10 137.221.78.79
11 137.221.66.45
12 185.60.112.158
Berechnung der Statistiken dauert ca. 300 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 DESKTOP-7TLN1UL.fritz.box [192.168.178.25]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% fritz.box [192.168.178.1]
0/ 100 = 0% |
2 4ms 0/ 100 = 0% 0/ 100 = 0% 85.16.121.172
0/ 100 = 0% |
3 5ms 0/ 100 = 0% 0/ 100 = 0% 85.16.250.240
0/ 100 = 0% |
4 5ms 0/ 100 = 0% 0/ 100 = 0% 85.16.249.117
0/ 100 = 0% |
5 6ms 0/ 100 = 0% 0/ 100 = 0% bbrt.ol-1-1-xe-3-2-0.ewe-ip-backbone.de [80.228.90.86]
0/ 100 = 0% |
6 9ms 0/ 100 = 0% 0/ 100 = 0% 212.6.115.118
0/ 100 = 0% |
7 16ms 0/ 100 = 0% 0/ 100 = 0% pr01.eqfr5.blizzardonline.net [80.81.195.26]
3/ 100 = 3% |
8 40ms 8/ 100 = 8% 5/ 100 = 5% ae1-br01-eqfr5.as57976.net [137.221.80.33]
0/ 100 = 0% |
9 41ms 3/ 100 = 3% 0/ 100 = 0% et-0-0-2-br01-eqam1.as57976.net [137.221.65.29]
1/ 100 = 1% |
10 39ms 5/ 100 = 5% 1/ 100 = 1% 137.221.78.79
0/ 100 = 0% |
11 --- 100/ 100 =100% 96/ 100 = 96% 137.221.66.45
0/ 100 = 0% |
12 36ms 4/ 100 = 4% 0/ 100 = 0% 185.60.112.158
Ablaufverfolgung beendet.
C:\Windows\system32>pathping 185.60.112.158
Routenverfolgung zu "185.60.112.158" über maximal 30 Hops
0 DESKTOP-7TLN1UL.fritz.box [192.168.178.25]
1 fritz.box [192.168.178.1]
2 85.16.121.172
3 85.16.250.240
4 85.16.249.117
5 bbrt.ol-1-1-xe-3-2-0.ewe-ip-backbone.de [80.228.90.86]
6 212.6.115.118
7 pr01.eqfr5.blizzardonline.net [80.81.195.26]
8 ae1-br01-eqfr5.as57976.net [137.221.80.33]
9 et-0-0-2-br01-eqam1.as57976.net [137.221.65.29]
10 137.221.78.79
11 137.221.66.45
12 185.60.112.158
Berechnung der Statistiken dauert ca. 300 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 DESKTOP-7TLN1UL.fritz.box [192.168.178.25]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% fritz.box [192.168.178.1]
0/ 100 = 0% |
2 4ms 0/ 100 = 0% 0/ 100 = 0% 85.16.121.172
0/ 100 = 0% |
3 5ms 0/ 100 = 0% 0/ 100 = 0% 85.16.250.240
0/ 100 = 0% |
4 7ms 0/ 100 = 0% 0/ 100 = 0% 85.16.249.117
0/ 100 = 0% |
5 6ms 0/ 100 = 0% 0/ 100 = 0% bbrt.ol-1-1-xe-3-2-0.ewe-ip-backbone.de [80.228.90.86]
0/ 100 = 0% |
6 9ms 0/ 100 = 0% 0/ 100 = 0% 212.6.115.118
0/ 100 = 0% |
7 18ms 0/ 100 = 0% 0/ 100 = 0% pr01.eqfr5.blizzardonline.net [80.81.195.26]
3/ 100 = 3% |
8 39ms 3/ 100 = 3% 0/ 100 = 0% ae1-br01-eqfr5.as57976.net [137.221.80.33]
1/ 100 = 1% |
9 38ms 11/ 100 = 11% 7/ 100 = 7% et-0-0-2-br01-eqam1.as57976.net [137.221.65.29]
0/ 100 = 0% |
10 38ms 7/ 100 = 7% 3/ 100 = 3% 137.221.78.79
0/ 100 = 0% |
11 --- 100/ 100 =100% 96/ 100 = 96% 137.221.66.45
0/ 100 = 0% |
12 35ms 4/ 100 = 4% 0/ 100 = 0% 185.60.112.158
Ablaufverfolgung beendet.
C:\Windows\system32>pathping 185.60.112.158
Routenverfolgung zu "185.60.112.158" über maximal 30 Hops
0 DESKTOP-7TLN1UL.fritz.box [192.168.178.25]
1 fritz.box [192.168.178.1]
2 85.16.121.172
3 85.16.250.240
4 85.16.249.117
5 bbrt.ol-1-1-xe-3-2-0.ewe-ip-backbone.de [80.228.90.86]
6 212.6.115.118
7 pr01.eqfr5.blizzardonline.net [80.81.195.26]
8 ae1-br01-eqfr5.as57976.net [137.221.80.33]
9 et-0-0-2-br01-eqam1.as57976.net [137.221.65.29]
10 137.221.78.79
11 137.221.66.45
12 * 185.60.112.158
Berechnung der Statistiken dauert ca. 300 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 DESKTOP-7TLN1UL.fritz.box [192.168.178.25]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% fritz.box [192.168.178.1]
0/ 100 = 0% |
2 5ms 0/ 100 = 0% 0/ 100 = 0% 85.16.121.172
0/ 100 = 0% |
3 5ms 0/ 100 = 0% 0/ 100 = 0% 85.16.250.240
0/ 100 = 0% |
4 5ms 0/ 100 = 0% 0/ 100 = 0% 85.16.249.117
0/ 100 = 0% |
5 6ms 0/ 100 = 0% 0/ 100 = 0% bbrt.ol-1-1-xe-3-2-0.ewe-ip-backbone.de [80.228.90.86]
0/ 100 = 0% |
6 9ms 0/ 100 = 0% 0/ 100 = 0% 212.6.115.118
0/ 100 = 0% |
7 17ms 0/ 100 = 0% 0/ 100 = 0% pr01.eqfr5.blizzardonline.net [80.81.195.26]
3/ 100 = 3% |
8 38ms 3/ 100 = 3% 0/ 100 = 0% ae1-br01-eqfr5.as57976.net [137.221.80.33]
3/ 100 = 3% |
9 38ms 8/ 100 = 8% 2/ 100 = 2% et-0-0-2-br01-eqam1.as57976.net [137.221.65.29]
0/ 100 = 0% |
10 37ms 6/ 100 = 6% 0/ 100 = 0% 137.221.78.79
1/ 100 = 1% |
11 --- 100/ 100 =100% 93/ 100 = 93% 137.221.66.45
0/ 100 = 0% |
12 34ms 7/ 100 = 7% 0/ 100 = 0% 185.60.112.158
Ablaufverfolgung beendet.
C:\Windows\system32>
Hi!
Bei mir aus Österreich auch … das Problem fängt aber erst bei Blizzard an; pingen kann ich zu allen möglichen Locations, ohne Probleme! Punkte hab ich durch Bindestriche ersetzt, sonst kann man es wieder nicht abschicken …
Microsoft Windows [Version 10.0.18363.815]
© 2019 Microsoft Corporation. Alle Rechte vorbehalten.
Routenverfolgung zu „185.60.114.159“ über maximal 30 Hops
0 Tidestorm.home [10.0.0.12]
1 a1modem.home [10.0.0.138]
2 93-82-71-254.adsl.highway.telekom.at [93.82.71.254]
3 195.3.66.193
4 195.3.68.6
5 * lg1-1171-as8447-a1-net [195.3.64.2]
6 pr01-eqfr5-blizzardonline-net [80.81.195.26]
7 137.221.80.35
8 et-0-0-2-br01-eqpa4-as57976-net [137.221.65.26]
9 be1-pe2-eqpa4-as57976-net [137.221.77.69]
10 185.60.114.159
Berechnung der Statistiken dauert ca. 250 Sekunden…
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 Tidestorm.home [10.0.0.12]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% a1modem.home [10.0.0.138]
0/ 100 = 0% |
2 8ms 0/ 100 = 0% 0/ 100 = 0% 93-82-71-254.adsl.highway.telekom.at [93.82.71.254]
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% 195.3.66.193
0/ 100 = 0% |
4 11ms 0/ 100 = 0% 0/ 100 = 0% 195.3.68.6
0/ 100 = 0% |
5 21ms 0/ 100 = 0% 0/ 100 = 0% lg1-1171-as8447-a1-net [195.3.64.2]
0/ 100 = 0% |
6 — 100/ 100 =100% 100/ 100 =100% pr01-eqfr5-blizzardonline-net [80.81.195.26]
0/ 100 = 0% |
7 47ms 3/ 100 = 3% 3/ 100 = 3% 137.221.80.35
0/ 100 = 0% |
8 39ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-2-br01-eqpa4-as57976-net [137.221.65.26]
5/ 100 = 5% |
9 58ms 5/ 100 = 5% 0/ 100 = 0% be1-pe2-eqpa4-as57976-net [137.221.77.69]
6/ 100 = 6% |
10 53ms 11/ 100 = 11% 0/ 100 = 0% 185.60.114.159
Ablaufverfolgung beendet.
Nicht nur wow laggt, sondern Overwatch auch, da merkt man den erhöhten Ping deutlich.^^
Im englischen bereich gibt es dazu auch schon ein Thema
Was mich nur weiterhin wundert, dass man nirgends eine aussage dazu von Blizzard finden kann.
Sonst sind die mit sowas immer schnell.
Es wird immer schlimmer und schlimmer, will man sich noch bis Shadowlands irgendwie durchquälen und wird sich dann überhaupt was ändern an der Performance?
Nachts läuft alles fluffig , looten, Gildenbank , portale und Aktionen sind alle on point aber sobald es Richtung Prime Time geht nurnoch delay des Todes.
Eben durchs Pandaria Portal gegangen , 3 sekunden passiert erstmal nix. Worldboss Mechaniken ausweichen … AHAHHAHAH nix da, Friedhof.
Das macht schon kein Spaß mehr