Oh I love it clueless people...
Note : I'm not defending Turbine, there is some server lag... but there's just so many thing wrongs in the quote below that I can't resist.
scythes wrote on Sep 4
th, 2014 at 7:05am:
most of the ppl i run with have fast internet,and a high end pc.and we still get server lag
No. Yes you get lag, but it's not possible for you to tell if it's server Lag or Carrier lag.
Wipe wrote on Sep 4
th, 2014 at 7:07am:
GMT Friday evenings is sure way to get some lag on Ghallanda.
Not a single raid without some amount of lag. Not one.
Usually the Friday Raidathon of The Spellswords doesn't encounter lag... and since we are EU based and all... Raids starts at 7:30 Uk Time...
ghostbane wrote on Sep 4
th, 2014 at 12:54pm:
I have a top notch gaming rig I built myself and a good internet connection. On multiple occasions I've experienced lag that was on the server side. How can I confirm this? TEAMSPEAK. 10-15 people in TS, many of us from different countries and therefore following different ISP main trunk paths (routes) with some of us in different dungeons and everyone gets lag spikes at the same time... that is not due to shitty connections or rigs on our side.
In addition, I have simultaneously been in LOTRO on multiple occasions where the lag spike that hits DDO also hits LOTRO. Sorry, but I've been in IT 20 years and my experience tells me that is not a coincidence as it happens too frequently.
If they run LOTRO on the same server clusters that DDO run on, then it could be a server/hardware issue, but I don't know that information. So for now, I will assume they do not run it on the same hardware and the issue is more likely a network based issue either at the data-center or a nearby router/segment hop somewhere very close to it.
Typically,
this is not SERVER lag. It already happened numerous times... There's threads here and in the main forum about it.
Anyway, I'm going to repost it and all the explanations :
Turbine has a SPOF between their network and PNAP. PNAP has a SPOF between them and Cogent ( the preferred carrier for Turbine ) in the case of Turbine.
DDO tracert from $ORK :
H:\>tracert gls.ddo.com
Tracing route to gls.ddo.com [74.201.102.13]
over a maximum of 30 hops:
10 57 ms 76 ms 55 ms 193.180.17.236
11 55 ms 56 ms 55 ms 78.77.163.217
12 56 ms 56 ms 56 ms s-b1-link.telia.net [213.155.136.7]
13 85 ms 56 ms 56 ms s-bb3-link.telia.net [62.115.137.158]
14 64 ms 67 ms 65 ms kbn-bb3-link.telia.net [62.115.139.169]
15 66 ms 66 ms 66 ms kbn-b3-link.telia.net [213.155.135.179]
16 66 ms 67 ms 66 ms hu0-5-0-0.rcr21.cph01.atlas.cogentco.com [130.117.14.33]
17 72 ms 72 ms 72 ms be2306.ccr42.ham01.atlas.cogentco.com [130.117.3.237]
18 79 ms 79 ms 79 ms be2187.ccr42.ams03.atlas.cogentco.com [154.54.74.125]
19 85 ms 84 ms 84 ms be2276.ccr22.lon13.atlas.cogentco.com [154.54.36.57]
20 163 ms 185 ms 163 ms be2389.ccr22.bos01.atlas.cogentco.com [154.54.44.181]
21 214 ms 164 ms 165 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
22 158 ms 161 ms 159 ms 38.122.52.50
23 258 ms 161 ms 166 ms border1.te7-1-bbnet1.bsn003.pnap.net [63.251.128.43]
24 157 ms 157 ms 157 ms turbine-7.border1.bsn003.pnap.net [64.95.76.202]
25 162 ms 164 ms 165 ms 74.201.102.154
26 164 ms 164 ms 169 ms 74.201.102.13
Everything before hop 10 is internal corporate notwork, so it's unimportant... I've purged it.
If DDO and LoTRO freeze at the same time, from All over the world... the culprit is : turbine-7.border1.bsn003.pnap.net or border1.te7-1-bbnet1.bsn003.pnap.net
That's not a Turbine router... it's a PNAP router.
Why I can say that ? Because ALL traffic that goes to a Turbine server go through these two routers. That's basic routing protocol... that's my job troubleshooting these fucking things.
As you can see LOTRO uses the same two routers... ( well for me it follow the same path. )
H:\>tracert gls.lotro.com
Tracing route to gls.lotro.com [74.201.102.12]
over a maximum of 30 hops:
10 55 ms 55 ms 55 ms 193.180.17.236
11 55 ms 60 ms 56 ms 78.77.163.217
12 56 ms 56 ms 56 ms s-b6-link.telia.net [62.115.138.53]
13 56 ms 57 ms 56 ms s-bb3-link.telia.net [62.115.136.20]
14 65 ms 75 ms 66 ms kbn-bb3-link.telia.net [62.115.139.171]
15 67 ms 70 ms 67 ms kbn-b3-link.telia.net [62.115.142.75]
16 67 ms 67 ms 67 ms hu0-5-0-0.rcr21.cph01.atlas.cogentco.com [130.117.14.33]
17 71 ms 73 ms 71 ms be2303.ccr41.ham01.atlas.cogentco.com [130.117.3.161]
18 79 ms 79 ms 80 ms be2186.ccr41.ams03.atlas.cogentco.com [154.54.74.121]
19 86 ms 89 ms 85 ms be2275.ccr21.lon13.atlas.cogentco.com [130.117.51.253]
20 157 ms 156 ms 157 ms be2388.ccr21.bos01.atlas.cogentco.com [154.54.44.177]
21 173 ms 163 ms 166 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
22 167 ms 163 ms 162 ms 38.104.252.70
23 157 ms 159 ms 156 ms border1.te8-1-bbnet2.bsn003.pnap.net [63.251.128.107]
24 161 ms 158 ms 157 ms turbine-7.border1.bsn003.pnap.net [64.95.76.202]
25 161 ms 163 ms 162 ms 74.201.102.154
26 164 ms 163 ms 162 ms 74.201.102.12
Trace complete.
Now if only a part of the world is hit by lag... it's another router somewhere else, as I pointed in one of the previous threads.
To detail further ( as I said that cogent and PNAP also have a SPOF ) :
te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
62 ms 38.104.252.70
These two culprits are the peering routers between Cogent and PNAP... if any encounters a problem you will get lag... Since, the previous one ( be2388.ccr21.bos01.atlas.cogentco.com ) aggregates most of the traffic that comes into Boston from far away, you have good chances to go through it...
So that makes 5 different machines, that can generate widespread, worldwide impacting lag...that are NOT servers, and that do not belongs to Turbine.
Add to that Hop 25 ( that's the first Turbine system... and it's not a server but a router ) and the eventual transparent firewall somewhere between it and the border router...
And you've got 7 sources of lag, that are NOT servers... and only 2 of those sources are controlled by Turbine.
So before pointing fingers towards servers give proof of it. As we used to say around here : Screenshot or it didn't happen... Make a traceroute when you get hit by lag... and post it... it will give proof of where the lag is...
If the traceroute is clean but you lag like there is no tomorrow in game, then it will be the server.