[Germany - Osnatel/EWE-Tel] Lagspike & packetloss Issues
|
Hi
I decide to make my own lagspike & packetloss thread. I would like to share my WinMTR here. I am using ethernet and i have no trouble with internet-surfing, Streams or League of Legends. These lagspikes happens with all PoE Server for me, Battleping as a workaroud didn`t change much for me. If you need some WinMTR to another Host just tell me the IP and i will do it. Amsterdamm (usually my best connection) 29.09 Evening Running Hideout http://pastebin.com/Jxt78ZRB 30.09, 07:00am Running Hideout / Docks run http://pastebin.com/MnLRunk4 30.09, 05:56pm Running Hideout / Docks runs http://pastebin.com/ZJT5GUdX 01.10.2015 01:19pm Hideout / Docks http://pastebin.com/waggsHyv London 30.09, 06:15pm Hideout / Docks http://pastebin.com/KjZAKr7s 01.10, 02:25pm Dailies http://pastebin.com/eBMbCqdM 01.10, 02:40pm Dailies http://pastebin.com/Un09VLW9 02.10, 10:45am Afk in town http://pastebin.com/zU4LS5XL 02.10, 02.06pm afk http://pastebin.com/ERd1Aqqs 03.10, 09:56am off http://pastebin.com/cwBHuZhD 05.10, 09:15am http://pastebin.com/RRk8D5Y9 06.10, 09:21am http://pastebin.com/CVCDqv3S 06.10, 06:48pm http://pastebin.com/bcZLhUFk 07.10, 09:54am http://pastebin.com/reK8mc0q Australia 30.09, 06:24pm Hideout http://pastebin.com/bW3edQ0N Edit: Choosed to contact my ISP. I tried to explain my problem and the WinMTR results. I forgot to ask them if i should send my WinMTR to them. Will call them tomorrow to get an update. Last edited by FieselWiesel on Oct 7, 2015, 3:55:31 AM
|
|
|
Hi
There is in update: As you can see in this: http://pastebin.com/waggsHyv WinMTR, my ISP changed the trace route (hop 1,2, 4 and 5). My early packet loss is gone and lag spikes are reduced by a lot! Only po1.fcr01.sr01.ams01.networklayer.com (last before game server amsterdamm) got a small problem now. My game is playable with a few spikes now. I think there is no way for me to fix the last router from networklayer? Edit: Changed to London and did 2 WinMTR: 0% packet loss, slightly higher ingame latenzy. Think London is my gateway to go at the moment. Last edited by FieselWiesel on Oct 2, 2015, 5:42:47 AM
|
|
|
New day, new trouble...
Today i woke up, started my PC and after that PoE. Logged in to London Gateway AND....lag spikes! lag spikes and more lagspikes.... Fuck the 2.04 patch!...oh wait maybe not....lets use WinMTR to check my connection... http://pastebin.com/zU4LS5XL WHAT THE F*CK??!! Dear ISP this is the fu**ing same shitt i had 2 days ago! Remember? Lag spikes --> called my ISP --> one day later --> trace rout changed, lag spikes gone --> play --> sleep --> trace rout changed --> lagspikes everywhere again! Call ISP: waiting loop.......waiting loop..........oh and...hmm....waiting loop..... Last edited by FieselWiesel on Oct 2, 2015, 5:41:54 AM
|
|
|
Called my ISP, with bad results. They told me my internet is okay and my packetloss and lag spikes are normal (WTF?!)
My next step was: I wrote an e-mail @Osnatel and EWE-Tel, including all my WinMTR`s in this topic. This results proof that something strange is going on with ewe-tels hops. Osnatel answered first: Thank you for your Message, we will take a look and contact you later, meantime be patient plz. (looks like an automatic response) I will wait....today...weekend (that sux...!!) my e-mail in German:
Spoiler
Name: XXX Telefonnummer: XXX Anschrift: XXX Kundennummer: XXX E-Mail: XXX Liebes Osnatel und EWE-Tel Team, Vor zwei Tagen habe ich mich bei der Osnatel das erste Mal telefonisch gemeldet. Dabei habe ich erklärt das ich Probleme bei dem Online-Spiel Path of Exile (PoE) habe. Ich habe immer wieder mit hohen Latenzen (Lag-Spikes) zu kämpfen. Der Support von PoE hat mir geraten eine Diagnose mit dem Tool WinMTR durchzuführen. Dieses Tool zeigt die trace route, also den Weg, welche meine Daten von meinem PC zu dem Spielserver nehmen. Dieses Tool habe ich zu unterschiedlichen Zeiten laufen lassen und dabei ließ sich erkennen, dass es schon bei den ersten beiden hops von ihnen zu Problemen kommt: IP: 212.95.98.252, Georgsmarinen Hütte IP: 212.95.100.149, Osnabrück Ein Tag nachdem ich ihnen telefonisch mitgeteilt habe, dass diese Probleme bestehen, wurde meine trace route verändert. Alte trace route (30.09.2015): |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | multi.box - 0 | 545 | 545 | 0 | 0 | 1 | 0 | | 212.95.98.252 - 9 | 401 | 365 | 0 | 13 | 51 | 11 | | 212.95.100.149 - 8 | 413 | 380 | 8 | 13 | 75 | 15 | | bbrt-ol-1-xe-3-1-0.ewe-ip-backbone.de - 9 | 401 | 365 | 0 | 18 | 82 | 40 | | bbrt.hb-0-1-xe-9-3-0.ewe-ip-backbone.de - 7 | 429 | 400 | 12 | 16 | 77 | 13 | | bbrt.hb-2-xe-11-1-0.ewe-ip-backbone.de - 9 | 409 | 375 | 12 | 16 | 68 | 31 | |bbrt.lon-0-10ge-7-0-0.ewe-ip-backbone.de - 8 | 413 | 380 | 31 | 35 | 70 | 38 | | bbr01.lon01.networklayer.com - 7 | 429 | 400 | 30 | 32 | 78 | 34 | | ae5.dar01.lon02.networklayer.com - 7 | 437 | 410 | 30 | 33 | 68 | 37 | | po1.fcr01b.lon02.networklayer.com - 10 | 401 | 364 | 32 | 34 | 70 | 32 | |159.122.193.164-static.reverse.softlayer.com - 7 | 429 | 400 | 30 | 32 | 69 | 34 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider Neue trace route (01.10.2015): |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | multi.box - 0 | 544 | 544 | 0 | 0 | 1 | 0 | | 212.95.98.253 - 0 | 544 | 544 | 9 | 11 | 97 | 9 | | xe-3-0-0.bbrt-1.os.osnanet.de - 0 | 544 | 544 | 9 | 15 | 89 | 9 | | bbrt-ol-1-xe-3-1-0.ewe-ip-backbone.de - 0 | 544 | 544 | 13 | 18 | 86 | 13 | |bbrt.ol-0-1-xe-11-0-0.ewe-ip-backbone.de - 0 | 544 | 544 | 14 | 20 | 110 | 36 | | bbrt.hb-2-xe-4-2-0.ewe-ip-backbone.de - 0 | 544 | 544 | 15 | 20 | 80 | 16 | | 80.228.90.89 - 0 | 544 | 544 | 29 | 33 | 119 | 30 | | bbr01.lon01.networklayer.com - 0 | 544 | 544 | 32 | 35 | 102 | 32 | | ae5.dar01.lon02.networklayer.com - 0 | 544 | 544 | 32 | 34 | 83 | 33 | | po1.fcr01b.lon02.networklayer.com - 0 | 544 | 544 | 33 | 36 | 110 | 35 | |159.122.193.164-static.reverse.softlayer.com - 0 | 544 | 544 | 32 | 34 | 91 | 32 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider Bei der alten trace route kam es schon beim ersten hop von ihnen zu einem Packetloss von 9%. Dieser Fehler zieht sich durch die gesamte trace route, daher schließe ich einen Anzeigefehler oder abgeblockte ICMP Packete aus. Bei der neuen trace route wurden mehrere hops durch andere ersetzt und der Packetloss sowie die Lag-Spikes waren sowohl im Spiel als auch in der Anzeige von WinMTR verschwunden. Leider musste ich heute morgen (02.10.2015) feststellen, dass ich wieder Probleme in dem Spiel PoE hatte. Aus diesem Grund habe ich WinMTR erneut gestartet und musste feststellen, dass die trace route erneut verändert wurde. Trace route vom 02.10.2015: |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | multi.box - 0 | 1401 | 1401 | 0 | 0 | 1 | 0 | | 212.95.98.252 - 7 | 1101 | 1026 | 9 | 14 | 518 | 9 | | 212.95.100.149 - 9 | 1061 | 976 | 8 | 16 | 116 | 9 | | bbrt-ol-1-xe-3-1-0.ewe-ip-backbone.de - 8 | 1073 | 990 | 14 | 19 | 117 | 15 | | bbrt.hb-0-1-xe-0-0-0.ewe-ip-backbone.de - 8 | 1076 | 994 | 13 | 18 | 119 | 14 | | bbrt.hb-2-xe-11-1-0.ewe-ip-backbone.de - 6 | 1141 | 1076 | 14 | 19 | 116 | 16 | |bbrt.lon-0-10ge-7-0-0.ewe-ip-backbone.de - 9 | 1057 | 971 | 32 | 37 | 139 | 33 | | bbr01.lon01.networklayer.com - 8 | 1096 | 1019 | 33 | 38 | 136 | 38 | | ae5.dar01.lon02.networklayer.com - 7 | 1115 | 1043 | 33 | 37 | 138 | 36 | | po1.fcr01b.lon02.networklayer.com - 8 | 1085 | 1006 | 33 | 36 | 137 | 34 | |159.122.193.164-static.reverse.softlayer.com - 10 | 1021 | 926 | 31 | 35 | 137 | 32 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider Wie man sieht, werde ich wieder über die hops vom 30.09.2015 geleitet und sowohl der Packetloss als auch die Lag-Spikes sind wieder da. Mir stellt sich die Frage, wieso ich nach Meldung der Störung erst über eine reibungslos funktionierende trace route umgeleitet werde und einen Tag später wieder über die Problematische? Da es scheinbar möglich ist meine Probleme mit der Internetleitung zu beheben, gehe ich davon aus das dies nun umgehend geschieht. Im Anhang finden sie meine WinMTR Ergebnisse, die auf www.pastebin.com übersichtlicher und besser dargestellt werden können, als in diesem Textdokument. MfG XXX Nachtrag: Nach einem unbefriedigendem Gespräch mit dem Service der Osnatel habe ich mich dazu entschlossen diese E-Mail an info@osnatel.de sowie über das Kontaktformular auf der EWE-Tel Internetseite zu senden. Anhang 29.09.2015 PoE Server Amsterdamm http://pastebin.com/Jxt78ZRB 30.09.2015 PoE Server Amsterdamm 07:00 Uhr: http://pastebin.com/MnLRunk4 17:56 Uhr http://pastebin.com/ZJT5GUdX PoE Server London 18:15 Uhr: http://pastebin.com/KjZAKr7s PoE Server Australia 18:24 Uhr: http://pastebin.com/bW3edQ0N 01.10.2015 PoE Server Amsterdamm 13:19 Uhr: http://pastebin.com/waggsHyv Hier sieht man das es auf der trace route nach Amsterdamm noch einen defekten hop gibt, welcher nicht von ihnen ist, daher bin ich von meinem ursprünglichen Spielserver Amsterdamm auf den in London gewechselt. PoE Server London 14:25 Uhr: http://pastebin.com/eBMbCqdM 14:40 Uhr http://pastebin.com/Un09VLW9 02.10.2015 PoE Server London 10:45 Uhr: http://pastebin.com/Un09VLW9 14:06 Uhr: http://pastebin.com/ERd1Aqqs Last edited by FieselWiesel on Oct 2, 2015, 9:50:15 AM
|
|
|
Same for London gate.
Its just unplayable in maps. | |
|
Why do you feel the need to use a gateway thousands of miles from you, there is no possible way it's not going to have high latency....all you need to provide is the test ran wile you play on the gateway that you are having a problem on.
But no, packet loss and lag spikes are not normal, your isp is bullshitting you...it's what the frontline help dose, you could press the issue and ask to speak to a higher level technician. And it's starting at the second hop....it's definitely not something GGG can help you with...only your ISP can do that. Ancestral Bond. It's a thing that does stuff. -Vipermagi
He who controls the pants controls the galaxy. - Rick & Morty S3E1 |
|
|
Hi Thanks for your answer.
Usually my best gateway is Amsterdamm, second best is London / Frankfurt. On 01.10.2015 i got another trace route and a hop from networklayer was the only one from me to amsterdamm that got some packet loss. Thats why i played on London and did my next tests to London. Other WinMTR`s like Australia or USA was just to test something out. Tried to skip these shitty hops next to me in any way. Didn`t worked :S but was worth a try i think. stable latenzy of 100-150 with 0% packet loss would be better than 32-45ms with lag spikes from 100 to 800ms and 8+% packet loss. E-Mailed both Osnatel and EwE-Tel, no answer yet. Seems like i have to wait for monday :S (this saturday is a public holiday) |
|
|
see this post:
https://www.pathofexile.com/forum/view-thread/1435036 |
|
|
Well my ISP isnt Deutsche Telekom but yeah thats the problem of a lot of players. Nevertheless my trace route is way to long for Amsterdamm / London / Frankfurt and if Deutsche Telekom wouldn`t be a**holes, im sure my traceroute would be shorter and better. i am not going through a single telekom hop, but across the world just to avoid this company.
|
|
|
New day...new luck?
This morning i checked my e-mail: no response Check WinMTR: http://pastebin.com/cwBHuZhD I am using my standart trace route with the 2 problematic hops in the beginning but at the moment they are working *yeah* Log in: London Gateway works like a charm! I am sceptic if this is forever...but i will use the window and play a bit cya later! |
|
