Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
5 903 ms 1046 ms 1055 ms be3000.ccr21.sjc03.atlas.cogentco.com [154.54.11.45]
6 372 ms 555 ms 48 ms be2047.ccr22.sjc01.atlas.cogentco.com [154.54.5.113]
7 587 ms 624 ms 732 ms be2166.mpd21.sfo01.atlas.cogentco.com [154.54.28.69]
8 786 ms 566 ms 838 ms be2134.mpd21.mci01.atlas.cogentco.com [154.54.6.38]
9 800 ms 912 ms 870 ms be2158.mpd21.ord01.atlas.cogentco.com [154.54.7.130]
10 862 ms 1024 ms 591 ms be2139.ccr21.bos01.atlas.cogentco.com [154.54.43.178]
11 567 ms 577 ms 501 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
12 585 ms 646 ms 646 ms 38.111.40.114
13 122 ms 99 ms 90 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
With latency this bad, this is most likely a problem with either your router or gateway modem, (including hops 2 - 4 would probably provide the proof one way or the other...)
By excluding your ISP results, you've made it impossible to determine if its your ISP that is causing the problem or not...
With latency this bad, this is most likely a problem with either your router or gateway modem, (including hops 2 - 4 would probably provide the proof one way or the other...)
By excluding your ISP results, you've made it impossible to determine if its your ISP that is causing the problem or not...
By not including my ISP I show that the problem is on their side because regardless of my latency the server side is far worse. The latency on my side is in the single to teens ms range, so sorry garbage about it's your computer isn't going to fly.
By not including my ISP I show that the problem is on their side because regardless of my latency the server side is far worse. The latency on my side is in the single to teens ms range, so sorry garbage about it's your computer isn't going to fly.
Try substituting the 'pathping' command for the 'tracert' command, as you could be suffering from dropped packet problems, even with good latency values...
Try substituting the 'pathping' command for the 'tracert' command, as you could be suffering from dropped packet problems, even with good latency values...
If you want to ignore the numbers posted be my guest.
If you're not going to supply the requested information, its obvious you can't be helped with your connection issues...
Tell you why your opinion didn't matter off the bat, instead of saying try to run the pathping right away you got the oh so high and mighty it's your computer ideal in your head and didn't look at the original numbers I posted. And I did you pathping 5 min for completion not acceptable help someone without the mind set of it's only you and try to diagnose the problem and my IP address has nothing to do with a problem on the server side.
If you don't work for this game, offer honest suggestions, prior to assuming anything.
I never had problems this bad. Lags, rubberbanding and now I can't even login anymore...
5 64 ms 64 ms 64 ms te0-7-0-10.mag21.fra03.atlas.cogentco.com [130.1
17.14.105]
6 64 ms 64 ms 73 ms be2028.mpd21.fra03.atlas.cogentco.com [154.54.74
.137]
7 78 ms 93 ms 80 ms be2263.mpd21.ams03.atlas.cogentco.com [154.54.61
.5]
8 87 ms 85 ms 85 ms be2184.ccr21.lpl01.atlas.cogentco.com [154.54.37
.70]
9 107 ms 107 ms 107 ms be2386.ccr21.bos01.atlas.cogentco.com [154.54.44
.161]
10 115 ms 115 ms 115 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
11 167 ms 159 ms 162 ms 38.111.40.114
12 156 ms * * patchserver2.crypticstudios.com [208.95.185.41]
13 158 ms 157 ms 158 ms patchserver2.crypticstudios.com [208.95.185.41]
I have been playing STO since launch, and have never had a problem until about 1 month ago. Now, whenever I log in, everthing is stop and go. Just parking at ESD, I can see all the ships flying around me freeze for a second, then move for a few seconds, then freeze again. Also, just logging in and loading takes way too long. Sometimes, it takes several minutes just for my BO ability trays to fill in.
However, I can play any other online game with high to max settings for several hours, and not have a single stutter.
So far, I have updated all my drivers, uninstalled and reinstalled STO, and even increased my speed with my ISP. Still, the problem persists.
I really hope that someone can help me resolve this issue so that I can play STO again.
My ISP is Mediacom. I live on the east coast of the U.S.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.10.1
2 17 ms 17 ms 19 ms 173-30-144-1.client.mchsi.com [173.30.144.1]
3 12 ms 18 ms 10 ms 172.30.30.57
4 32 ms 43 ms 40 ms 172.30.28.253
5 39 ms 39 ms 41 ms 172.30.30.54
6 36 ms 47 ms 36 ms 12.248.110.13
7 43 ms 39 ms 39 ms cr1.attga.ip.att.net [12.122.117.82]
8 39 ms 35 ms 37 ms gar3.brhal.ip.att.net [12.122.141.189]
9 89 ms 92 ms 85 ms te0-7-0-1.ccr21.atl02.atlas.cogentco.com [154.54.13.173]
10 90 ms 103 ms 81 ms be2053.mpd22.atl01.atlas.cogentco.com [154.54.3.145]
11 105 ms 99 ms 88 ms be2171.mpd22.dca01.atlas.cogentco.com [154.54.31.110]
12 106 ms 91 ms 100 ms be2150.mpd21.jfk02.atlas.cogentco.com [154.54.31.130]
13 107 ms 109 ms 110 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30.42]
14 113 ms 129 ms 111 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
15 113 ms 119 ms 108 ms 38.111.40.114
16 108 ms 107 ms 109 ms patchserver2.crypticstudios.com [208.95.185.41]
...
I really hope that someone can help me resolve this issue so that I can play STO again.
My ISP is Mediacom. I live on the east coast of the U.S.
Your 'Trace Route' diagnostics show network latency within acceptable limits, but your 'Net Test' results indicate that you are suffering from connection quality issues on your connection to the network where the STO Servers are located.
Try substituting the 'pathping' command for the 'tracert' command, and post the results, as this will show if you are suffering from 'Dropped Packets' on your connection, and where they are occuring...
Hmmm... Dropped Packets all over the place, with the worst being Hop #6 at 100%, which appears to happen from just after the ATT Gateway from your ISP, is so bad as to make all further readings unreliable...
You should probably complain to your ISP so they can check their gateway connection to the ATT.net backbone to see if its their problem, and if it isn't, to complain to ATT to get them to correct the issue...
The other thing you could try is the 'Proxy' option in the launcher, which may, (or may not) divert you onto a less congested Internet connection path to the STO servers...
I have been suffering constant crashes and DCs...ran a tracert and got this....
Nothing apparently wrong with the 'Path Ping' as the latency is well within acceptable limits, and no sign of dropped packets...
A 'Net Test' diagnostic would have been nice to see if you have the sustained network throughput needed, but the 'Path Ping' results suggest that your problems aren't network connection related, and instead, may be something systemic to your system that is causing the crashes and disconnects.
Ok. Let's make this a little easier, especially for those who haven't got a clue as to what you're talking about when you refer to pings and tracerts. This is real simple. If the problem were gameside, then everyone would be having play issues and the forums would be flooded with new posts. Since this is not the case, the problem is going to be on your (the player) end. Its either your router, your modem, your service, or your computer.
Now, its a fact that any router will eventually run into problems the older it gets. I don't care if you paid 10 bucks on ebay or 500 to some high end company. Even brand new routers sometimes have defects. So, before you dismiss the possibility that your router could be the problem, try getting up and resetting it ( this applies to the modem as well, so do both). Simply look on the back of the router and press the power button. Then unplug the modem and wait for all the lights to turn off. Then plug in the modem and turn the router back on.
If the above does not fix your problem, make sure your computer is connected to the internet. On older windows and windows 7/vist/xp, there is a function bar at the bottom of the desktop screen. This will have an indicator similar to most cell phone service bars. If there is a flag, and exclamation mark, or whatever else besides just white bars, then your computer is not connected to the internet for some reason. Check your internet settings in your control panel.
If your computer is setup correctly and should be connected to the internet, check your router and modem lights and make sure they are linked to the internet. If they are not, then your service is down. This actually happens fairly commonly around 2am when most people are not using it so the provider can make necassary repairs and run maintenance. You can call to confirm. Do not freak out.
Finally, if everything is working, and you can get on other sites without an issue, but still can't log into the game, make sure there is server maintenance scheduled. If you get a message about the server not being available, then that means that everyone has been booted from the game so Cryptic and pwe can do whatever they need to do, and the game will be back online in a couple of hours.
You don't need to start messing with pings and tracerts and all this other nonsense to find out why you can't play. If you have lag, and everyone else seems to be whooping your TRIBBLE, and it isn't normal for you, then your internet is probably bogged down. To prevent this kind of problem, here are a few tips to follow;
1) Do regular maintenance of your pc and router/modem. Run a defrag and cleaner on your pc once in a while (I do mine about once a month with smart defrag and Ccleaner). And resetyour router and modem while your pc is running its defrag routine (note, there should be NOTHING running other than defrag).
Again, this is for all those who are getting headaches from reading what the OP posted and trying to make sense of it.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dslrouter.westell.com [192.168.1.1]
2 111 ms 106 ms 112 ms drr03.athn.oh.frontiernet.net [74.42.148.83]
3 * 111 ms 108 ms ge--7-2-0---0.arr01.athn.oh.frontiernet.net [50.
42.13.41]
4 154 ms 143 ms 147 ms ae7---0.cor02.chcg.il.frontiernet.net [74.40.1.1
25]
5 * * * Request timed out.
6 * 157 ms * 206.111.2.145.ptr.us.xo.net [206.111.2.145]
7 208 ms * 212 ms 207.88.14.193.ptr.us.xo.net [207.88.14.193]
8 207 ms 209 ms 206 ms ae0d0.mcr2.cambridge-ma.us.xo.net [216.156.0.30]
9 184 ms 179 ms 184 ms 209.117.103.10
10 336 ms * 151 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
11 187 ms * 173 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
12 * 246 ms 244 ms patchserver2.crypticstudios.com [208.95.185.41]
...
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dslrouter.westell.com [192.168.1.1]
2 111 ms 106 ms 112 ms drr03.athn.oh.frontiernet.net [74.42.148.83]
...
Hope this helps Please help...
This is a unusually high value for the the first hop. Normally, you would expect values in the 5 to 10ms range...
Try rebooting/power cycle your router/gateway, and see if that improves things... If it doesn't, then you should contact your ISP Tech Support, and have them send someone out to take a look at the unit...
1 0 ms [10.0.0.1]
2 29 ms [50.167.220.1]
3 21 ms xe-11-0-0-32767-sur01.r2conyers.ga.atlanta.comcast.net [68.85.173.49]
4 10 ms xe-10-0-3-0-ar01.b0atlanta.ga.atlanta.comcast.net [68.86.106.254]
5 10 ms he-5-15-0-0-10-cr01.56marietta.ga.ibone.comcast.net [68.86.87.201]
6 * [-]
7 67 ms te0-0-0-19.ccr21.atl02.atlas.cogentco.com [154.54.10.233]
8 62 ms be2053.mpd22.atl01.atlas.cogentco.com [154.54.3.145]
9 71 ms be2168.ccr21.dca01.atlas.cogentco.com [154.54.31.94]
10 67 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31.118]
11 81 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30.38]
12 144 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
13 46 ms [38.111.40.114]
14 37 ms [208.95.186.32]
Ping statistics for 208.95.186.32
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 37ms, Maximum = 37ms, Average = 37ms
I have all my drivers updated and STO is the ONLY game or instance where this happens to my PC. However, I get constant lock ups in STO that requires hard resets and i am worried it will damage my HDD.
My Spec:
AMD 9590 5Ghz 8 Core CPU ( Temp at 58C at high load)
ASUS Sabretooth 990FX R2.0 Mobo
8GB RAM ( 1333Mhz)
Sapphire R9 290 Tri-X OC Graphics card. ( Temp 65-70C at high load)
Samsung EVO 256GB SSD
Windows 8.1
I use this rig to run BF4 on Ultra settings without a problem. I hope you can help since this is game breaking for me.
My game is horribly lagging . I am not expert in this . So is there any problem here?
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 7 ms <1 ms 1 ms sx763.sx76x.gigaset.net [192.168.1.1]
2 * * * Request timed out.
3 20 ms 21 ms 23 ms 172.29.33.53
4 24 ms 34 ms 24 ms gdr10-hdr01.ip.t-com.hr [195.29.241.114]
5 66 ms 207 ms 218 ms te7-8.ccr01.zag01.atlas.cogentco.com [149.6.30.9
3]
6 33 ms 32 ms 32 ms te0-7-0-18.ccr21.vie01.atlas.cogentco.com [130.1
17.48.145]
7 39 ms 41 ms 41 ms be2223.ccr22.muc01.atlas.cogentco.com [130.117.4
9.137]
8 46 ms 44 ms 45 ms be2230.mpd21.fra03.atlas.cogentco.com [154.54.38
.97]
9 52 ms 51 ms 53 ms be2264.mpd22.ams03.atlas.cogentco.com [154.54.6.
209]
10 59 ms 63 ms 59 ms be2277.mpd21.lon13.atlas.cogentco.com [154.54.62
.145]
11 126 ms 129 ms 130 ms be2390.ccr21.bos01.atlas.cogentco.com [154.54.44
.221]
12 129 ms 130 ms 128 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
13 197 ms 198 ms 196 ms 38.111.40.114
14 193 ms 195 ms 193 ms patchserver2.crypticstudios.com [208.95.185.41]
mine only crashes while i play not when loading i have 2gb of ram is there a way to fix that part or should i buy the max ram which is 4gb graphic is intel dual core
having an issue with launcher timing out, it simply will not connect. I can load and browse any web page, youtube, the movie site i use, and play any of my other 6 games without issue, STO is the only one not working. Been having issues ranging from white/multi color plaid textures, horrible lag/rubberbanding, random DC's, 10s to 1 1/2 min server not responding with 'massive catchup' and now not even being able to load launcher.
Tracing route to 208.95.168.32 over a maximum of 30 hops
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>tracert 208.95.186.32
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 1 ms 4 ms 1 ms Left Blank for Security Reasons
2 36 ms 36 ms 34 ms fl-71-3-216-1.dhcp.embarqhsd.net [71.3.216.1]
3 36 ms 37 ms 50 ms fl-184-7-223-38.sta.centurylinkservices.net [184
.7.223.38]
4 34 ms 35 ms 34 ms bb-ftmyflxa-jx9-02-ae0.core.centurytel.net [208.
110.248.86]
5 36 ms 36 ms 36 ms bb-ftmyflxa-jx9-01-ae0.core.centurytel.net [208.
110.248.85]
6 41 ms 41 ms 41 ms bb-wnpkflxe-jx9-01-xe-11-1-0.0.core.centurytel.n
et [208.110.248.185]
7 57 ms 57 ms 58 ms bb-rcmtncxa-jx9-02-xe-1-2-0.core.centurytel.net
[208.110.248.157]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 75 ms 76 ms 75 ms bst-edge-05.inet.qwest.net [67.14.30.126]
12 78 ms 78 ms 79 ms 65.120.117.250
13 77 ms 78 ms 78 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
14 192 ms 195 ms 197 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
15 179 ms 179 ms 182 ms 208.95.186.32
Trace complete.
C:\Windows\system32>
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>pathping 208.95.186.32
Tracing route to 208.95.186.32 over a maximum of 30 hops
having issues since the patch......takes forever to log into the actualy game as it gets stuck at loading New Romulus screen...then i got in and got kicked off after about 20 minutes...cant even get to the log in client (Using ARC)
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Windows\system32>tracert 208.95.186.32
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 NO NEED TO KNOW
2 9 ms 13 ms 13 ms 10.87.96.1
3 8 ms 8 ms 9 ms dtr01rancca-tge-0-1-1-0.ranc.ca.charter.com [96.
34.100.92]
4 12 ms 22 ms 12 ms crr01rvsdca-tge-0-4-0-4.rvsd.ca.charter.com [96.
34.100.208]
5 14 ms 14 ms 18 ms bbr01rvsdca-bue-2.rvsd.ca.charter.com [96.34.2.6
6]
6 20 ms 24 ms 20 ms bbr01mtpkca-bue-4.mtpk.ca.charter.com [96.34.0.2
3]
7 51 ms 54 ms * be4016.ccr23.lax05.atlas.cogentco.com [38.104.84
.101]
8 64 ms 55 ms 50 ms be2181.mpd21.lax01.atlas.cogentco.com [154.54.41
.113]
9 57 ms 57 ms 53 ms be2066.ccr22.iah01.atlas.cogentco.com [154.54.7.
53]
10 77 ms 77 ms 78 ms be2175.mpd22.atl01.atlas.cogentco.com [154.54.29
.221]
11 78 ms 77 ms 76 ms be2171.mpd22.dca01.atlas.cogentco.com [154.54.31
.110]
12 * * 131 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31
.118]
13 136 ms 136 ms 140 ms be2097.ccr22.bos01.atlas.cogentco.com [154.54.30
.118]
14 130 ms 132 ms * te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
15 137 ms * 147 ms 38.111.40.114
16 * 140 ms 174 ms 208.95.186.32
Trace complete.
C:\Windows\system32>
not sure why, but ONLY STO is having this issue...I can play every other online game just fine.
2nd trace....now i cant connect to account authorization at the login patcher
C:\Windows\system32>tracert 208.95.186.32
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 NO NEED TO KNOW
2 11 ms 12 ms 17 ms 10.87.96.1
3 11 ms 14 ms 11 ms dtr01rancca-tge-0-1-1-0.ranc.ca.charter.com [96.
34.100.92]
4 28 ms 15 ms 14 ms crr01rvsdca-tge-0-4-0-4.rvsd.ca.charter.com [96.
34.100.208]
5 23 ms 14 ms 14 ms bbr01rvsdca-bue-2.rvsd.ca.charter.com [96.34.2.6
6]
6 22 ms 23 ms 32 ms bbr01mtpkca-bue-4.mtpk.ca.charter.com [96.34.0.2
3]
7 64 ms 57 ms 51 ms be4016.ccr23.lax05.atlas.cogentco.com [38.104.84
.101]
8 58 ms 67 ms 64 ms be2181.mpd21.lax01.atlas.cogentco.com [154.54.41
.113]
9 54 ms 52 ms 52 ms be2065.ccr21.iah01.atlas.cogentco.com [154.54.5.
65]
10 85 ms 92 ms 85 ms be2175.mpd22.atl01.atlas.cogentco.com [154.54.29
.221]
11 84 ms 79 ms 94 ms be2171.mpd22.dca01.atlas.cogentco.com [154.54.31
.110]
12 130 ms 102 ms 96 ms be2149.ccr22.jfk02.atlas.cogentco.com [154.54.31
.126]
13 93 ms 105 ms 95 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30
.38]
14 99 ms 91 ms 129 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
15 88 ms 98 ms 97 ms 38.111.40.114
16 97 ms 88 ms 87 ms 208.95.186.32
Trace complete.
C:\Windows\system32>
EDIT: AGAIN:....hmm seems to just be server issues (not unexpected ofc.....) its back to working...but for how long :P
I find this line of replies sadly hilarious. We put a lot of work into the massive list of fixes/changes above, and ya'll are hung up on the ability to skip our content. =p
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 2 ms 1 ms 1 ms 192.168.1.1
2 27 ms 28 ms 28 ms uni1bras1.antel.net.uy [200.40.22.2]
3 29 ms 24 ms 28 ms ibb2uni2-7-2-90.antel.net.uy [200.40.22.161]
4 162 ms 161 ms 159 ms ibe2uni2-0-0-0-2.antel.net.uy [200.40.16.146]
5 162 ms 163 ms 164 ms ibr2nap3-0-1-4-0.antel.net.uy [200.40.16.158]
6 189 ms * 193 ms sl-st50-mia-.sprintlink.net [160.81.59.81]
7 * * * Request timed out.
8 * 254 ms 179 ms 144.232.25.70
9 164 ms 159 ms 163 ms be2054.ccr21.mia01.atlas.cogentco.com [154.54.80.41]
10 178 ms 178 ms 178 ms be2122.ccr21.atl01.atlas.cogentco.com [154.54.24.193]
11 188 ms 188 ms 185 ms be2171.mpd22.dca01.atlas.cogentco.com [154.54.31.110]
12 191 ms 195 ms 202 ms be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40.74]
13 202 ms 201 ms 201 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30.14]
14 202 ms 199 ms 197 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
15 197 ms 198 ms 198 ms 38.111.40.114
16 197 ms 196 ms 199 ms 208.95.186.32
Traceren van de route naar 208.95.186.32 via maximaal 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 7 ms 7 ms 10.15.7.1
3 10 ms 8 ms 9 ms 212.142.61.249
4 12 ms 39 ms 13 ms 84.116.244.21
5 13 ms 13 ms 13 ms 84.116.135.194
6 13 ms 12 ms 12 ms xe-0-1-0.cir1.amsterdam2-nh.nl.xo.net [195.69.145.200]
7 22 ms 23 ms 51 ms ae1d0.cir1.london2-eng.uk.xo.net [207.88.15.70]
8 106 ms 107 ms 107 ms vb1042.rar3.nyc-ny.us.xo.net [207.88.13.202]
9 111 ms 109 ms 107 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26]
10 106 ms 106 ms 106 ms ae1d0.mcr2.cambridge-ma.us.xo.net [216.156.1.14]
11 110 ms 108 ms 109 ms 209.117.103.10
12 105 ms 104 ms 106 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
13 109 ms 106 ms 108 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
14 106 ms 122 ms 106 ms 208.95.186.32
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Mike>tracert 208.95.186.32
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 7 ms 8 ms 8 ms 10.109.244.1
2 8 ms 8 ms 10 ms pres-core-2b-ae7-717.network.virginmedia.net [80
.0.161.177]
3 11 ms 13 ms 11 ms manc-bb-1d-ae11-0.network.virginmedia.net [213.1
05.159.197]
4 30 ms 30 ms 52 ms ams2-ic-1-ae0-0.network.virginmedia.net [62.253.
188.158]
5 39 ms 31 ms 33 ms be3010.ccr21.ams04.atlas.cogentco.com [130.117.1
5.5]
6 32 ms 31 ms 31 ms be2312.ccr22.ams03.atlas.cogentco.com [154.54.74
.93]
7 31 ms 32 ms 28 ms be2288.mpd22.lon13.atlas.cogentco.com [154.54.62
.149]
8 101 ms 101 ms 100 ms be2389.ccr22.bos01.atlas.cogentco.com [154.54.44
.181]
9 277 ms 216 ms 218 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
10 104 ms 105 ms 105 ms 38.111.40.114
11 102 ms 100 ms 100 ms 208.95.186.32
Tracing route to 208.95.168.32 over a maximum of 30 hops
1 2 ms <1 ms <1 ms 192.168.1.1
2 2 ms 3 ms 1 ms 188-173-60-129.next-gen.ro [188.173.60.129]
3 4 ms 3 ms 3 ms 188-173-48-9.next-gen.ro [188.173.48.9]
4 5 ms 1 ms 3 ms 89.121.204.189
5 44 ms 45 ms 47 ms 10.0.228.61
6 41 ms 41 ms 39 ms 10.0.252.193
7 48 ms 46 ms 47 ms 10.0.240.141
8 46 ms 46 ms 48 ms 10.0.200.62
9 45 ms 44 ms 45 ms l0.milnit1-cr1.bbnplanet.net [195.16.160.17]
10 134 ms 134 ms 134 ms vlan80.csw3.Frankfurt1.Level3.net [4.69.154.190]
11 139 ms 140 ms 141 ms ae-81-81.ebr1.Frankfurt1.Level3.net [4.69.140.9]
12 134 ms 132 ms 132 ms ae-45-45.ebr2.Paris1.Level3.net [4.69.143.134]
13 133 ms 130 ms 131 ms ae-43-43.ebr2.Washington1.Level3.net [4.69.137.5
8]
14 133 ms 133 ms 133 ms ae-72-72.csw2.Washington1.Level3.net [4.69.134.1
50]
15 131 ms 132 ms 185 ms ae-2-70.edge2.Washington4.Level3.net [4.69.149.8
0]
16 136 ms 131 ms 131 ms TWTC-level3-1x10G.Washington.Level3.net [4.53.11
4.10]
17 156 ms 183 ms 156 ms orl1-ar4-xe-2-0-0-0.us.twtelecom.net [66.192.245
.214]
18 160 ms 160 ms 160 ms 66-192-143-30.static.twtelecom.net [66.192.143.3
0]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Comments
With latency this bad, this is most likely a problem with either your router or gateway modem, (including hops 2 - 4 would probably provide the proof one way or the other...)
By excluding your ISP results, you've made it impossible to determine if its your ISP that is causing the problem or not...
By not including my ISP I show that the problem is on their side because regardless of my latency the server side is far worse. The latency on my side is in the single to teens ms range, so sorry garbage about it's your computer isn't going to fly.
Try substituting the 'pathping' command for the 'tracert' command, as you could be suffering from dropped packet problems, even with good latency values...
If you want to ignore the numbers posted be my guest.
If you're not going to supply the requested information, its obvious you can't be helped with your connection issues...
Tell you why your opinion didn't matter off the bat, instead of saying try to run the pathping right away you got the oh so high and mighty it's your computer ideal in your head and didn't look at the original numbers I posted. And I did you pathping 5 min for completion not acceptable help someone without the mind set of it's only you and try to diagnose the problem and my IP address has nothing to do with a problem on the server side.
If you don't work for this game, offer honest suggestions, prior to assuming anything.
5 64 ms 64 ms 64 ms te0-7-0-10.mag21.fra03.atlas.cogentco.com [130.1
17.14.105]
6 64 ms 64 ms 73 ms be2028.mpd21.fra03.atlas.cogentco.com [154.54.74
.137]
7 78 ms 93 ms 80 ms be2263.mpd21.ams03.atlas.cogentco.com [154.54.61
.5]
8 87 ms 85 ms 85 ms be2184.ccr21.lpl01.atlas.cogentco.com [154.54.37
.70]
9 107 ms 107 ms 107 ms be2386.ccr21.bos01.atlas.cogentco.com [154.54.44
.161]
10 115 ms 115 ms 115 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
11 167 ms 159 ms 162 ms 38.111.40.114
12 156 ms * * patchserver2.crypticstudios.com [208.95.185.41]
13 158 ms 157 ms 158 ms patchserver2.crypticstudios.com [208.95.185.41]
However, I can play any other online game with high to max settings for several hours, and not have a single stutter.
So far, I have updated all my drivers, uninstalled and reinstalled STO, and even increased my speed with my ISP. Still, the problem persists.
I really hope that someone can help me resolve this issue so that I can play STO again.
My ISP is Mediacom. I live on the east coast of the U.S.
Your 'Trace Route' diagnostics show network latency within acceptable limits, but your 'Net Test' results indicate that you are suffering from connection quality issues on your connection to the network where the STO Servers are located.
Try substituting the 'pathping' command for the 'tracert' command, and post the results, as this will show if you are suffering from 'Dropped Packets' on your connection, and where they are occuring...
Hmmm... Dropped Packets all over the place, with the worst being Hop #6 at 100%, which appears to happen from just after the ATT Gateway from your ISP, is so bad as to make all further readings unreliable...
You should probably complain to your ISP so they can check their gateway connection to the ATT.net backbone to see if its their problem, and if it isn't, to complain to ATT to get them to correct the issue...
The other thing you could try is the 'Proxy' option in the launcher, which may, (or may not) divert you onto a less congested Internet connection path to the STO servers...
Nothing apparently wrong with the 'Path Ping' as the latency is well within acceptable limits, and no sign of dropped packets...
A 'Net Test' diagnostic would have been nice to see if you have the sustained network throughput needed, but the 'Path Ping' results suggest that your problems aren't network connection related, and instead, may be something systemic to your system that is causing the crashes and disconnects.
Now, its a fact that any router will eventually run into problems the older it gets. I don't care if you paid 10 bucks on ebay or 500 to some high end company. Even brand new routers sometimes have defects. So, before you dismiss the possibility that your router could be the problem, try getting up and resetting it ( this applies to the modem as well, so do both). Simply look on the back of the router and press the power button. Then unplug the modem and wait for all the lights to turn off. Then plug in the modem and turn the router back on.
If the above does not fix your problem, make sure your computer is connected to the internet. On older windows and windows 7/vist/xp, there is a function bar at the bottom of the desktop screen. This will have an indicator similar to most cell phone service bars. If there is a flag, and exclamation mark, or whatever else besides just white bars, then your computer is not connected to the internet for some reason. Check your internet settings in your control panel.
If your computer is setup correctly and should be connected to the internet, check your router and modem lights and make sure they are linked to the internet. If they are not, then your service is down. This actually happens fairly commonly around 2am when most people are not using it so the provider can make necassary repairs and run maintenance. You can call to confirm. Do not freak out.
Finally, if everything is working, and you can get on other sites without an issue, but still can't log into the game, make sure there is server maintenance scheduled. If you get a message about the server not being available, then that means that everyone has been booted from the game so Cryptic and pwe can do whatever they need to do, and the game will be back online in a couple of hours.
You don't need to start messing with pings and tracerts and all this other nonsense to find out why you can't play. If you have lag, and everyone else seems to be whooping your TRIBBLE, and it isn't normal for you, then your internet is probably bogged down. To prevent this kind of problem, here are a few tips to follow;
1) Do regular maintenance of your pc and router/modem. Run a defrag and cleaner on your pc once in a while (I do mine about once a month with smart defrag and Ccleaner). And resetyour router and modem while your pc is running its defrag routine (note, there should be NOTHING running other than defrag).
Again, this is for all those who are getting headaches from reading what the OP posted and trying to make sense of it.
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dslrouter.westell.com [192.168.1.1]
2 111 ms 106 ms 112 ms drr03.athn.oh.frontiernet.net [74.42.148.83]
3 * 111 ms 108 ms ge--7-2-0---0.arr01.athn.oh.frontiernet.net [50.
42.13.41]
4 154 ms 143 ms 147 ms ae7---0.cor02.chcg.il.frontiernet.net [74.40.1.1
25]
5 * * * Request timed out.
6 * 157 ms * 206.111.2.145.ptr.us.xo.net [206.111.2.145]
7 208 ms * 212 ms 207.88.14.193.ptr.us.xo.net [207.88.14.193]
8 207 ms 209 ms 206 ms ae0d0.mcr2.cambridge-ma.us.xo.net [216.156.0.30]
9 184 ms 179 ms 184 ms 209.117.103.10
10 336 ms * 151 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
11 187 ms * 173 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
12 * 246 ms 244 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\Windows\system32>
Hope this helps
This is a unusually high value for the the first hop. Normally, you would expect values in the 5 to 10ms range...
Try rebooting/power cycle your router/gateway, and see if that improves things... If it doesn't, then you should contact your ISP Tech Support, and have them send someone out to take a look at the unit...
Comcast sent me a new modem this week. Now I'm getting terrible lag, server not responding, and rubber banding.
Always Hop #6, always 100% packet loss.
Someone on Comcast forums says Comcast and Cogentco are having "business issues" with each other.
Elite STFs are nasty when you add in a couple of 14 second server not respondings.
Target Name: (resolving host name)
IP: 208.95.186.32
Date/Time: 2/8/2014 9:21:55 AM
1 0 ms [10.0.0.1]
2 29 ms [50.167.220.1]
3 21 ms xe-11-0-0-32767-sur01.r2conyers.ga.atlanta.comcast.net [68.85.173.49]
4 10 ms xe-10-0-3-0-ar01.b0atlanta.ga.atlanta.comcast.net [68.86.106.254]
5 10 ms he-5-15-0-0-10-cr01.56marietta.ga.ibone.comcast.net [68.86.87.201]
6 * [-]
7 67 ms te0-0-0-19.ccr21.atl02.atlas.cogentco.com [154.54.10.233]
8 62 ms be2053.mpd22.atl01.atlas.cogentco.com [154.54.3.145]
9 71 ms be2168.ccr21.dca01.atlas.cogentco.com [154.54.31.94]
10 67 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31.118]
11 81 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30.38]
12 144 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
13 46 ms [38.111.40.114]
14 37 ms [208.95.186.32]
Ping statistics for 208.95.186.32
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 37ms, Maximum = 37ms, Average = 37ms
My Spec:
AMD 9590 5Ghz 8 Core CPU ( Temp at 58C at high load)
ASUS Sabretooth 990FX R2.0 Mobo
8GB RAM ( 1333Mhz)
Sapphire R9 290 Tri-X OC Graphics card. ( Temp 65-70C at high load)
Samsung EVO 256GB SSD
Windows 8.1
I use this rig to run BF4 on Ultra settings without a problem. I hope you can help since this is game breaking for me.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 7 ms <1 ms 1 ms sx763.sx76x.gigaset.net [192.168.1.1]
2 * * * Request timed out.
3 20 ms 21 ms 23 ms 172.29.33.53
4 24 ms 34 ms 24 ms gdr10-hdr01.ip.t-com.hr [195.29.241.114]
5 66 ms 207 ms 218 ms te7-8.ccr01.zag01.atlas.cogentco.com [149.6.30.9
3]
6 33 ms 32 ms 32 ms te0-7-0-18.ccr21.vie01.atlas.cogentco.com [130.1
17.48.145]
7 39 ms 41 ms 41 ms be2223.ccr22.muc01.atlas.cogentco.com [130.117.4
9.137]
8 46 ms 44 ms 45 ms be2230.mpd21.fra03.atlas.cogentco.com [154.54.38
.97]
9 52 ms 51 ms 53 ms be2264.mpd22.ams03.atlas.cogentco.com [154.54.6.
209]
10 59 ms 63 ms 59 ms be2277.mpd21.lon13.atlas.cogentco.com [154.54.62
.145]
11 126 ms 129 ms 130 ms be2390.ccr21.bos01.atlas.cogentco.com [154.54.44
.221]
12 129 ms 130 ms 128 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
13 197 ms 198 ms 196 ms 38.111.40.114
14 193 ms 195 ms 193 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
nettest
contacting nettest server..
Local IP: 83.131.91.239
Ping: 1000.6 msec
Port: 80: 12 KB/sec 1 KB/sec 13 KB/sec 500
Port: 80: 99 KB/sec 3 KB/sec 105 KB/sec 500
Port: 443: 85 KB/sec 3 KB/sec 90 KB/sec 500
Port: 443: 85 KB/sec 3 KB/sec 90 KB/sec 500
Port: 7255: 72 KB/sec 3 KB/sec 78 KB/sec 500
Port: 7255: 93 KB/sec 9 KB/sec 104 KB/sec 500
Port: 7003: 95 KB/sec 9 KB/sec 106 KB/sec 500
Port: 7003: 96 KB/sec 4 KB/sec 102 KB/sec 500
Port: 7202: 80 KB/sec 3 KB/sec 88 KB/sec 500
Port: 7202: 95 KB/sec 3 KB/sec 100 KB/sec 500
Port: 7499: 97 KB/sec 6 KB/sec 103 KB/sec 500
Port: 7499: 98 KB/sec 4 KB/sec 103 KB/sec 500
Port: 80: 111 KB/sec 4 KB/sec 119 KB/sec 500
Idle NIC bandwidth Send: 1 KB/sec Recv: 0 KB/sec
hit return to exit
Tracing route to 208.95.168.32 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms . [192.168.2.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 55 ms 40 ms 40 ms te-0-5-0-1-pe03.seattle.wa.ibone.comcast.net [17
3.167.56.5]
11 40 ms 38 ms 38 ms as4323.seattle.wa.ibone.comcast.net [173.167.56.
50]
12 112 ms 112 ms 112 ms orl1-ar4-xe-0-0-0-0.us.twtelecom.net [66.192.245
.210]
13 131 ms 115 ms 115 ms 66-192-143-30.static.twtelecom.net [66.192.143.3
0]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Tracing route to 208.95.168.41 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms . [192.168.2.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 40 ms 39 ms 40 ms te-0-5-0-1-pe03.seattle.wa.ibone.comcast.net [17
3.167.56.5]
11 49 ms 101 ms 39 ms as4323.seattle.wa.ibone.comcast.net [173.167.56.
50]
12 112 ms 112 ms 112 ms orl1-ar4-xe-0-0-0-0.us.twtelecom.net [66.192.245
.210]
13 117 ms 114 ms 114 ms 66-192-143-30.static.twtelecom.net [66.192.143.3
0]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>tracert 208.95.186.32
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 1 ms 4 ms 1 ms Left Blank for Security Reasons
2 36 ms 36 ms 34 ms fl-71-3-216-1.dhcp.embarqhsd.net [71.3.216.1]
3 36 ms 37 ms 50 ms fl-184-7-223-38.sta.centurylinkservices.net [184
.7.223.38]
4 34 ms 35 ms 34 ms bb-ftmyflxa-jx9-02-ae0.core.centurytel.net [208.
110.248.86]
5 36 ms 36 ms 36 ms bb-ftmyflxa-jx9-01-ae0.core.centurytel.net [208.
110.248.85]
6 41 ms 41 ms 41 ms bb-wnpkflxe-jx9-01-xe-11-1-0.0.core.centurytel.n
et [208.110.248.185]
7 57 ms 57 ms 58 ms bb-rcmtncxa-jx9-02-xe-1-2-0.core.centurytel.net
[208.110.248.157]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 75 ms 76 ms 75 ms bst-edge-05.inet.qwest.net [67.14.30.126]
12 78 ms 78 ms 79 ms 65.120.117.250
13 77 ms 78 ms 78 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
14 192 ms 195 ms 197 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
15 179 ms 179 ms 182 ms 208.95.186.32
Trace complete.
C:\Windows\system32>
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>pathping 208.95.186.32
Tracing route to 208.95.186.32 over a maximum of 30 hops
0 Left blank for Security reasons
1 Left blank for Security reasons
2 fl-71-3-216-1.dhcp.embarqhsd.net [71.3.216.1]
3 fl-184-7-223-20.sta.centurylinkservices.net [184.7.223.20]
4 bb-ftmyflxa-jx9-02-ae0.core.centurytel.net [208.110.248.86]
5 bb-ftmyflxa-jx9-01-ae0.core.centurytel.net [208.110.248.85]
6 bb-wnpkflxe-jx9-01-xe-11-1-0.0.core.centurytel.net [208.110.248.185]
7 bb-rcmtncxa-jx9-02-xe-1-2-0.core.centurytel.net [208.110.248.157]
8 * * *
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Sue-PC.PK5001Z [192.168.0.41]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 35ms 0/ 100 = 0% 0/ 100 = 0% fl-71-3-216-1.dhcp.embarqhsd.net [
71.3.216.1]
0/ 100 = 0% |
3 42ms 0/ 100 = 0% 0/ 100 = 0% fl-184-7-223-20.sta.centurylinkser
vices.net [184.7.223.20]
0/ 100 = 0% |
4 38ms 0/ 100 = 0% 0/ 100 = 0% bb-ftmyflxa-jx9-02-ae0.core.centur
ytel.net [208.110.248.86]
0/ 100 = 0% |
5 38ms 0/ 100 = 0% 0/ 100 = 0% bb-ftmyflxa-jx9-01-ae0.core.centur
ytel.net [208.110.248.85]
0/ 100 = 0% |
6 45ms 0/ 100 = 0% 0/ 100 = 0% bb-wnpkflxe-jx9-01-xe-11-1-0.0.cor
e.centurytel.net [208.110.248.185]
0/ 100 = 0% |
7 64ms 0/ 100 = 0% 0/ 100 = 0% bb-rcmtncxa-jx9-02-xe-1-2-0.core.c
enturytel.net [208.110.248.157]
Trace complete.
C:\Windows\system32>
Seems to be some issue somewhere!!!
Praetor of the -RTS- Romulan Tal Shiar fleet!
not sure why, but ONLY STO is having this issue...I can play every other online game just fine.
2nd trace....now i cant connect to account authorization at the login patcher
EDIT: AGAIN:....hmm seems to just be server issues (not unexpected ofc.....) its back to working...but for how long :P
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 2 ms 1 ms 1 ms 192.168.1.1
2 27 ms 28 ms 28 ms uni1bras1.antel.net.uy [200.40.22.2]
3 29 ms 24 ms 28 ms ibb2uni2-7-2-90.antel.net.uy [200.40.22.161]
4 162 ms 161 ms 159 ms ibe2uni2-0-0-0-2.antel.net.uy [200.40.16.146]
5 162 ms 163 ms 164 ms ibr2nap3-0-1-4-0.antel.net.uy [200.40.16.158]
6 189 ms * 193 ms sl-st50-mia-.sprintlink.net [160.81.59.81]
7 * * * Request timed out.
8 * 254 ms 179 ms 144.232.25.70
9 164 ms 159 ms 163 ms be2054.ccr21.mia01.atlas.cogentco.com [154.54.80.41]
10 178 ms 178 ms 178 ms be2122.ccr21.atl01.atlas.cogentco.com [154.54.24.193]
11 188 ms 188 ms 185 ms be2171.mpd22.dca01.atlas.cogentco.com [154.54.31.110]
12 191 ms 195 ms 202 ms be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40.74]
13 202 ms 201 ms 201 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30.14]
14 202 ms 199 ms 197 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
15 197 ms 198 ms 198 ms 38.111.40.114
16 197 ms 196 ms 199 ms 208.95.186.32
Trace complete.
C:\Users>
C:\Users\Gebruiker>tracert 208.95.186.32
Traceren van de route naar 208.95.186.32 via maximaal 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 7 ms 7 ms 10.15.7.1
3 10 ms 8 ms 9 ms 212.142.61.249
4 12 ms 39 ms 13 ms 84.116.244.21
5 13 ms 13 ms 13 ms 84.116.135.194
6 13 ms 12 ms 12 ms xe-0-1-0.cir1.amsterdam2-nh.nl.xo.net [195.69.145.200]
7 22 ms 23 ms 51 ms ae1d0.cir1.london2-eng.uk.xo.net [207.88.15.70]
8 106 ms 107 ms 107 ms vb1042.rar3.nyc-ny.us.xo.net [207.88.13.202]
9 111 ms 109 ms 107 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26]
10 106 ms 106 ms 106 ms ae1d0.mcr2.cambridge-ma.us.xo.net [216.156.1.14]
11 110 ms 108 ms 109 ms 209.117.103.10
12 105 ms 104 ms 106 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
13 109 ms 106 ms 108 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
14 106 ms 122 ms 106 ms 208.95.186.32
De trace is voltooid.
Rubberbanding like crazy whole the time
Fix the lag and forget ARC !!!
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Mike>tracert 208.95.186.32
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 7 ms 8 ms 8 ms 10.109.244.1
2 8 ms 8 ms 10 ms pres-core-2b-ae7-717.network.virginmedia.net [80
.0.161.177]
3 11 ms 13 ms 11 ms manc-bb-1d-ae11-0.network.virginmedia.net [213.1
05.159.197]
4 30 ms 30 ms 52 ms ams2-ic-1-ae0-0.network.virginmedia.net [62.253.
188.158]
5 39 ms 31 ms 33 ms be3010.ccr21.ams04.atlas.cogentco.com [130.117.1
5.5]
6 32 ms 31 ms 31 ms be2312.ccr22.ams03.atlas.cogentco.com [154.54.74
.93]
7 31 ms 32 ms 28 ms be2288.mpd22.lon13.atlas.cogentco.com [154.54.62
.149]
8 101 ms 101 ms 100 ms be2389.ccr22.bos01.atlas.cogentco.com [154.54.44
.181]
9 277 ms 216 ms 218 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
10 104 ms 105 ms 105 ms 38.111.40.114
11 102 ms 100 ms 100 ms 208.95.186.32
Trace complete.
C:\Users\Mike>
1 2 ms <1 ms <1 ms 192.168.1.1
2 2 ms 3 ms 1 ms 188-173-60-129.next-gen.ro [188.173.60.129]
3 4 ms 3 ms 3 ms 188-173-48-9.next-gen.ro [188.173.48.9]
4 5 ms 1 ms 3 ms 89.121.204.189
5 44 ms 45 ms 47 ms 10.0.228.61
6 41 ms 41 ms 39 ms 10.0.252.193
7 48 ms 46 ms 47 ms 10.0.240.141
8 46 ms 46 ms 48 ms 10.0.200.62
9 45 ms 44 ms 45 ms l0.milnit1-cr1.bbnplanet.net [195.16.160.17]
10 134 ms 134 ms 134 ms vlan80.csw3.Frankfurt1.Level3.net [4.69.154.190]
11 139 ms 140 ms 141 ms ae-81-81.ebr1.Frankfurt1.Level3.net [4.69.140.9]
12 134 ms 132 ms 132 ms ae-45-45.ebr2.Paris1.Level3.net [4.69.143.134]
13 133 ms 130 ms 131 ms ae-43-43.ebr2.Washington1.Level3.net [4.69.137.5
8]
14 133 ms 133 ms 133 ms ae-72-72.csw2.Washington1.Level3.net [4.69.134.1
50]
15 131 ms 132 ms 185 ms ae-2-70.edge2.Washington4.Level3.net [4.69.149.8
0]
16 136 ms 131 ms 131 ms TWTC-level3-1x10G.Washington.Level3.net [4.53.11
4.10]
17 156 ms 183 ms 156 ms orl1-ar4-xe-2-0-0-0.us.twtelecom.net [66.192.245
.214]
18 160 ms 160 ms 160 ms 66-192-143-30.static.twtelecom.net [66.192.143.3
0]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.