Had a short talk with Sandy about the TS d/cs and everything and what some issues could be and it came to this: what could really, really help is if we got some traces from EVERYONE that's experiencing these D/Cs, packet loss, increased ping, whatever as well as a time stamp of when it's happening. So please, start posting these below otherwise it stalls our efforts on fixing the issues. If you do not, you have no right to whine about said issues. I'll start: View: http://gyazo.com/654af60ee660f46d50d020d58f87922f 2:57 AM EST, June 16th, 2015 Directions: Open command prompt (on Windows - consult a Mac/Linux guide else) and type "tracert prts.info" (minus quotation "" marks) when experiencing the issues. Thanks guys!
These problems have become more apparent to me, I'll update this post with an edit first thing tomorrow with my trace route.
It can be hard to catch the packet loss via command prompt. I would recommend using a program like Pingplotter which you set up to ping a server of your choice every x seconds/minutes and let it run in the background for as long as youd like or pause it whenever and it logs and graphs the data for you. You can then export the whole test results easily to their own file type read only by the app (cuz it shows the graph and all that) or you can export the logs to notepad to be saved as whatever format or paste in pastebin. Pingplotter is by far the best Ive found but it is a 30 day trial. Its a must have for any network issues. There are many similar apps out there. I also have a ghetto notepad program that does the same basic idea I could share.
Both work fine. ts.pr-gaming.net only had to be used for a little while because Sandy forgot to renew the domain for a short time. Regardless, you could even use pr-gaming.net and it wouldn't matter - you're trying to trace the PR server and the results will be the same no matter what in the end.
text is much better than an image - but if an image is all you can muster, that will have to do, I suppose. If you are using windows I'd recommend winMTR. Given winmtr.net appears to be down, we're left with sourceforge http://sourceforge.net/projects/winmtr/ Put it in a folder and run it from there - I think, from memory, you need to run it as administrator so that it can open the sockets required to do the trace. It has the option to export to text and has a much nicer readout, combining ping and trace data. It will give you a great visual idea of what is happening while it is running. What does it show? When sending data across the net, it is handed from server to server. If one of those servers is overloaded or having trouble you will see packet loss - this is what contributes to disconnects, poor TS quality etc. If it's a problem with the colo, you would expect to see packet lost appear around onewiltshire, or sharktech. If your packet loss occurs prior to these servers, it is just the internet being the internet. Feel free to email your traces to me. Please ensure date, time and your IP are included. To make this easier, I save my exported text as yyyymmdd_hhmm_myip_server e.g. 20150618_1645WST_myip_prts.info If you don't know my email, ask me on steam.
Microsoft Windows [Version 6.3.9600] (c) 2013 Microsoft Corporation. All rights reserved. C:\Users\Supplice>tracert prts.info Tracing route to prts.info [107.167.11.151] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.0.1 2 37 ms 28 ms 29 ms user-0c9abu1.cable.mindspring.com [24.149.47.193 ] 3 124 ms 30 ms 19 ms tge0-0-2.rochnyei01h.northeast.rr.com [24.93.8.1 82] 4 12 ms 10 ms 12 ms agg35.rochnyei02r.northeast.rr.com [24.58.44.218 ] 5 13 ms 10 ms 10 ms be28.rochnyei01r.northeast.rr.com [24.58.32.74] 6 23 ms 26 ms 26 ms bu-ether45.chcgildt87w-bcr00.tbone.rr.com [107.1 4.19.106] 7 23 ms 23 ms 23 ms 0.ae1.pr1.chi10.tbone.rr.com [107.14.17.194] 8 26 ms 24 ms 26 ms te0-1-0-22.ccr41.ord03.atlas.cogentco.com [154.5 4.11.145] 9 25 ms 24 ms 26 ms be2217.ccr42.ord01.atlas.cogentco.com [154.54.24 .205] 10 123 ms 46 ms 47 ms be2157.ccr22.mci01.atlas.cogentco.com [154.54.6. 117] 11 45 ms 47 ms 48 ms be2010.ccr22.dfw01.atlas.cogentco.com [154.54.46 .218] 12 52 ms 53 ms 54 ms be2537.ccr22.iah01.atlas.cogentco.com [154.54.45 .21] 13 81 ms 81 ms 81 ms be2066.ccr22.lax01.atlas.cogentco.com [154.54.7. 54] 14 86 ms 85 ms 85 ms be2017.ccr21.lax04.atlas.cogentco.com [154.54.0. 237] 15 86 ms 83 ms 82 ms po5.cogent.edge01.onewileshire.la.ca.us.sharktec h.net [107.167.0.249] 16 * * * Request timed out. 17 * 94 ms * customer.sharktech.net [107.167.11.146] 18 * * * Request timed out. 19 * 98 ms * customer.sharktech.net [107.167.11.151] 20 * * 95 ms customer.sharktech.net [107.167.11.151] Trace complete. C:\Users\Supplice>
Really weird issues of horrendous lag/disconnects from TS/other {PR} servers around 9:30-10:30 ESTish - only weird really because it generally seems to happen more late in the night, like around 1-3 AM, and it was a lot more brutal than usual. Anyway: During: Microsoft Windows [Version 6.3.9600] (c) 2013 Microsoft Corporation. All rights reserved. C:\Users\Supplice>tracert pr-gaming.net Tracing route to pr-gaming.net [107.167.11.147] over a maximum of 30 hops: 1 1 ms 1 ms <1 ms 192.168.0.1 2 23 ms 20 ms 47 ms user-0c9abu1.cable.mindspring.com [24.149.47.193 ] 3 126 ms 276 ms 26 ms tge0-0-2.rochnyei01h.northeast.rr.com [24.93.8.1 82] 4 13 ms 13 ms 9 ms be35.rochnyei02r.northeast.rr.com [24.58.44.218] 5 16 ms 11 ms 14 ms be28.rochnyei01r.northeast.rr.com [24.58.32.74] 6 32 ms 28 ms 30 ms bu-ether25.chcgildt87w-bcr00.tbone.rr.com [107.1 4.19.28] 7 26 ms 24 ms 24 ms 0.ae2.pr1.chi10.tbone.rr.com [107.14.17.196] 8 123 ms 26 ms 25 ms agg-eth2-pe05.350ecermak.il.ibone.comcast.net [7 5.149.230.69] 9 26 ms 31 ms 27 ms he-2-0-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.86.33] 10 57 ms 54 ms 57 ms be-10617-cr02.denver.co.ibone.comcast.net [68.86 .85.170] 11 57 ms 55 ms 54 ms he-0-2-0-0-cr01.denverqwest.co.ibone.comcast.net [68.86.89.30] 12 86 ms 75 ms 75 ms he-10-1-3-cr01.sunnyvale.ca.ibone.comcast.net [6 8.86.89.129] 13 123 ms 83 ms 84 ms be-10915-cr02.losangeles.ca.ibone.comcast.net [6 8.86.86.98] 14 77 ms 80 ms 78 ms he-0-0-0-1-pe01.losangeles.ca.ibone.comcast.net [68.86.85.30] 15 * * * Request timed out. 16 * * * Request timed out. 17 167 ms * 167 ms customer.sharktech.net [107.167.11.146] 18 * * 165 ms customer.sharktech.net [107.167.11.147] Trace complete. C:\Users\Supplice>tracert pr-gaming.net Tracing route to pr-gaming.net [107.167.11.147] over a maximum of 30 hops: 1 1 ms 44 ms 65 ms 192.168.0.1 2 22 ms 20 ms 19 ms user-0c9abu1.cable.mindspring.com [24.149.47.193 ] 3 83 ms 32 ms 31 ms tge0-0-2.rochnyei01h.northeast.rr.com [24.93.8.1 82] 4 11 ms 10 ms 14 ms be35.rochnyei02r.northeast.rr.com [24.58.44.218] 5 13 ms 14 ms 12 ms be28.rochnyei01r.northeast.rr.com [24.58.32.74] 6 28 ms 26 ms 27 ms bu-ether25.chcgildt87w-bcr00.tbone.rr.com [107.1 4.19.28] 7 25 ms 24 ms 24 ms 0.ae2.pr1.chi10.tbone.rr.com [107.14.17.196] 8 23 ms 24 ms 22 ms agg-eth2-pe05.350ecermak.il.ibone.comcast.net [7 5.149.230.69] 9 26 ms 119 ms 27 ms he-2-0-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.86.33] 10 58 ms 56 ms 56 ms be-10617-cr02.denver.co.ibone.comcast.net [68.86 .85.170] 11 53 ms 55 ms 55 ms he-0-2-0-0-cr01.denverqwest.co.ibone.comcast.net [68.86.89.30] 12 73 ms 75 ms * he-10-1-3-cr01.sunnyvale.ca.ibone.comcast.net [6 8.86.89.129] 13 82 ms 129 ms 82 ms be-10915-cr02.losangeles.ca.ibone.comcast.net [6 8.86.86.98] 14 80 ms 78 ms 79 ms he-0-0-0-1-pe01.losangeles.ca.ibone.comcast.net [68.86.85.30] 15 * * 85 ms po3.comcast.edge01.onewilshire.la.ca.sharktech.n et [107.167.0.225] 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 79 ms 76 ms 75 ms customer.sharktech.net [107.167.11.147] Trace complete. After: C:\Users\Supplice>tracert pr-gaming.net Tracing route to pr-gaming.net [107.167.11.147] over a maximum of 30 hops: 1 26 ms <1 ms 1 ms 192.168.0.1 2 31 ms 21 ms 11 ms user-0c9abu1.cable.mindspring.com [24.149.47.193 ] 3 31 ms 31 ms 31 ms tge0-0-2.rochnyei01h.northeast.rr.com [24.93.8.1 82] 4 13 ms 11 ms 10 ms be35.rochnyei02r.northeast.rr.com [24.58.44.218] 5 15 ms 15 ms 14 ms be28.rochnyei01r.northeast.rr.com [24.58.32.74] 6 26 ms 27 ms 27 ms bu-ether25.chcgildt87w-bcr00.tbone.rr.com [107.1 4.19.28] 7 26 ms 25 ms 24 ms 0.ae2.pr1.chi10.tbone.rr.com [107.14.17.196] 8 28 ms 26 ms 60 ms agg-eth2-pe05.350ecermak.il.ibone.comcast.net [7 5.149.230.69] 9 50 ms 29 ms 28 ms he-2-0-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.86.33] 10 55 ms 57 ms 55 ms be-10617-cr02.denver.co.ibone.comcast.net [68.86 .85.170] 11 55 ms 71 ms 54 ms he-0-2-0-0-cr01.denverqwest.co.ibone.comcast.net [68.86.89.30] 12 * 75 ms 75 ms he-10-1-3-cr01.sunnyvale.ca.ibone.comcast.net [6 8.86.89.129] 13 86 ms 80 ms 81 ms be-10915-cr02.losangeles.ca.ibone.comcast.net [6 8.86.86.98] 14 77 ms 76 ms 78 ms he-0-0-0-1-pe01.losangeles.ca.ibone.comcast.net [68.86.85.30] 15 81 ms 82 ms 132 ms po3.comcast.edge01.onewilshire.la.ca.sharktech.n et [107.167.0.225] 16 * * * Request timed out. 17 77 ms 76 ms 78 ms customer.sharktech.net [107.167.11.146] 18 75 ms 78 ms 76 ms customer.sharktech.net [107.167.11.147] Trace complete. C:\Users\Supplice>
That one may be CPU induced. Last couple ARK patches were very hard on the CPU with even a few players, and I think @King8Bit's tweaks have started to attract more players. Fortunately the update delivered this morning seems to have stabilized it somewhat. Let me know if we have repeats.
Well, I'll try... Had to work 1-5 (turned into 1-6) today, end up working 3-9 tomorrow and Monday (which basically means get home and straight to bed) so... It'll probably mean all up to other people with shifts like that. This one's up to @tythekillaoo and the like.
