Raids and spell lag

Is your internet being routed through switchnap?

I know and any suggestion that the information that tracert would supply was protested against...followed by a dev requesting tracerts....go figure.

Hopefully next time things go south peeps will do some tracerouts.

Suggesting because someone didn't post a tracert in this thread they didn't send one at all. Nice logic!

Did you send one? I'm not suggesting anyone did not but I AM encouraging to peeps follow dev requests and
send them.

lol wut? You're suggesting exactly that.

I mean, you know SoE moved their servers to Vegas right, and that the company is Switch, and they are hosting the stuff in their NAP. The Hardware may not physically be SoE's, but it was most certainly their problem, since they are a customer of Switch. So yes, we had to get SoE to realize this is in fact your problem. Funny that, once they did, and once they looked into, it got fixed in a matter of days after going on for weeks.

I just did a tracert to freeport.everquest2.com and there is a drastic change in the routing. I used to go through about 6 hops of cogico which are not there now, and my 23 hops is down to 16.

Not a single switchnap in the list either.

tracert freeport.everquest2.com

Tracing route to lvseq2-09-01.everquest2.com [69.174.200.90]
over a maximum of 30 hops:

5 6 ms 6 ms 9 ms bx2-torontoxn_xe2-3-0.net.bell.ca [64.230.49.61]

6 10 ms 6 ms 6 ms peer-limelight_bx4-toronto63.net.bell.ca [64.230
.134.38]
7 10 ms 16 ms 6 ms ve5.fr3.yyz.llnw.net [69.28.171.141]
8 62 ms 67 ms 62 ms tge3-1.fr3.yvr2.llnw.net [68.142.125.22]
9 70 ms 96 ms 93 ms tge8-4.fr4.sea2.llnw.net [68.142.80.253]
10 91 ms 95 ms 99 ms tge2-4.fr4.las.llnw.net [69.28.172.97]
11 91 ms 97 ms 99 ms tge1-1.fr3.las.llnw.net [69.28.172.17]
12 102 ms 220 ms 201 ms switch.ge3-1.fr3.las.llnw.net [208.111.176.2]
13 92 ms 94 ms 167 ms cust-199.189.116.246.sinap-tix.com [199.189.116.
246]
14 94 ms 137 ms 167 ms sony.demarc3.sinap-tix.com [64.79.157.78]
15 111 ms 125 ms 160 ms vl3105.lvssw-1.sonyonline.net [64.37.168.30]
16 107 ms 119 ms 93 ms lvseq2-09-01.everquest2.com [69.174.200.90]

Trace complete.

Hop 12 is on the bad side 14 and 15 are also a bit high, was this during a peak play time?

sinap is part of switchnap

64.79.156.1
te2-7.las-sagg7-1.sinap-tix.com.
64.79.156.3
cust-64.79.156.3.switchnap.com
sinap-tix.com name server ns2.switchnap.com


These have nothing to do with SOE necessarily just a quick check with some DNS tools pulled this up.

Some of the reconfiguring that switchnap did to improve would definately have the potential to do this.

That was just before I posted it...hardly anywhere near peak in any US timezone.

Edit: didn't realise sinap-tix was an alternate name for switchnap.

Wow, what an E-Hero! Do you really think that a company as large as Sony predominately searches for solutions on player forums to resolve severe technical issues with their data centers? I'm sure your efforts were appreciated, and for that sir, you deserve a gold star. I never threw out that this wasn't a possibility, I just stated that all signs point to an internal issue considering how concentrated the problem was. I stand behind the fact that this thought was not unreasonable.

Your implication was here:

I'm guessing it was your rebuttal to my opinion of who was responsible for people not being able to play the game, and you felt the need to explain that the entire infrastructure for the world wide web could interfere with it, as well as anyone's local power plant. I mean with insight like this, its amazing Sony doesn't use these forums to solve technical problems more often.

I didn't provide any tracert data because I personally wasn't experiencing any unusual lag. Regardless of my indirect involvement, frustration from this event is equally justified considering the encounters are unplayable with a large percentage of the raid 20 seconds behind the encounter. The "norm" for lag in this game is horrible even with faulty cabinet space provided by Switchnap ( purchased by Sony ) not in the equation , and is predominately the reason so many of us have such little faith in SoE's concerns and solutions regarding latency. This thread was not solely created to mitigate problems involved with Switchnap - it was created to shine some light on the ridiculous amounts of lag that have plagued this game for years which still remains largely unresolved.

We had minimal raid lag during our raids Mon & Tue night; so (knock on wood) so far so good.

Seems many here do understand how much of business is "symbiotic" As an example I happen to work at a power plant. Should we have to shut down because of a pump failure people do not call the group we contract with to overhaul and maintain the pump, they call us the power company. We make their power and when it is lost we are responsible for getting it back.

Now the pump contract company could care less if we make power unless we make then care. Just so happens this has happened to us and we "worked with said company" to ensure their practices support more reliable overhauls and general maintenance of the pump. This literally included sending some of our technicians to oversight the work at their factory and requiring the company to update its procedures to increase the quality of their work.

The company acquiesced because they needed our business, no amount of complaining customers without power calling "the pump company" would have changed this company's practice as long as the power company didn't recognize and hold accountable the pump company who made the pump.

Bottom line, this is no different than SOE contracting with an ISP, the ISP really could care less if SOE's games are unplayable unless SOE makes the ISP care. Some have suggested we should be more focused on calling the service providers, I ask why? As long as SOE pays the bill and doesn't not have an issue we can complain and petition said ISP all we want, they won't care, we are not paying them SOE is. So it is SOE that must be petitioned when the problem is likely affiliated with anyone they contract with not those companies directly.

As noted above, once SOE focused on the problem resolutions started occurring, this is because they are precisely the organization responsible for the health of the product after client side issues are ruled out. Anyone who has run or understands western business would understand this.

Sorry for the wall of text, this is a complicated relationship to describe

Double post

So now you admit it was not SOE's own hardware (only because you literally have no choice), despite your prior refusal to consider anything but.

Glad we can now both agree that you were wrong.

I think you should go back and read some more, you're just incredibly dense. Switch is hosting SoE's stuff. It may not physically be their hardware, but that doesn't mean they aren't leasing it and the services. That means it is SoE's problem. How this simple concept eludes you I don't really understand. If a drunk driver knocks out a telephone poll and I lose power it is still the power companies problem. If a tree falls in front of my house and takes out my cable line it is still the cable companies responsibility to fix it. If the company you host your website through has a server in a remote data center go down causing your site to go down you still call the webhost. If I order something on Amazon that is shipped from someone else and there is a problem I still call Amazon.

The world, how it works, so many mysteries.

I have no idea how you jumped (maybe more like rocketed over a canyon) to that conclusion.

There is a difference between problem, and responsibility.

If SOE guaranteed subscribers 100% up-time, and unlimited accessibility (no lag), it is SOE's responsibility to make sure everything is running flawlessly. But they do not guarantee such. While it is in SOE's interest to provide customers good service, they are not bound by contract (responsible) to resolve the problem.

You were claiming it was SOE at fault (their servers), and SOE's responsibility to fix. The facts are SOE was not at fault, and SOE did not fix it.

It is the companies problem, because they want people to use their service, so they can charge customers for it. However, depending on your local infrastructure design, and sub-provider system, the responsibility to repair the damage can fall upon different parties (namely, who ever owns it).

So the cable company is responsible for their own cable? Cool story.

1) Was it the webhosts fault? No.
2) Is it the webhosts responsibility to fix? Depends on their contract with the client.
3) Is in the interest of the webhost to request a fix anyway? Yes.
4) Is it the data centers responsibility to fix? Depends on the contract with the webhost.

It was not Amazon at fault. However, it is in their interest to follow up on it, and Amazon's business model will factor in a percentage of issues with deliveries/refunds/fraud (approx 6% annually).

End of the day, you were adamant it was SOE's servers. It was not.

SoE's servers are hosted by Switch. Yes, it is SoE's problem.

Edit: Especially when SoE wide

From about 8pm PST onward tonight I was getting HORRENDOUS lag when I usually got none even when lots of people got it. Here are some choice tracert I got during the process. I also got some bad ones related to sinap-tix.com but I have seem to have lost them.

Code:

Tracing route to lvseq2-04-01.everquest2.com [69.174.200.40]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2    6 ms    4 ms    5 ms  74.100.141.1
  3    29 ms    10 ms    8 ms  G0-3-0-1.LSANCA-LCR-22.verizon-gni.net [130.81.1
78.238]
  4    6 ms    7 ms    7 ms  so-3-1-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.199.40]
  5    8 ms    7 ms    8 ms  0.so-2-1-0.XT2.LAX7.ALTER.NET [152.63.10.149]
  6    7 ms    7 ms    7 ms  0.xe-11-1-0.XL4.LAX1.ALTER.NET [152.63.112.117]
 
  7    7 ms    7 ms    7 ms  0.xe-11-1-0.GW2.LAX1.ALTER.NET [152.63.4.193]
  8    10 ms    9 ms    8 ms  customer.alter.net.customer.alter.net [152.179.1
03.2]
  9    11 ms    9 ms    12 ms  te-2-0-0-6-cr01.losangeles.ca.ibone.comcast.net
[68.86.82.57]
10    10 ms    10 ms    9 ms  he-0-0-0-0-pe02.600wseventh.ca.ibone.comcast.net
[68.86.83.18]
11    8 ms    16 ms    7 ms  66.208.233.14
12  317 ms  328 ms  316 ms  ve6.fr4.lax.llnw.net [69.28.171.206]
13  318 ms  320 ms  319 ms  tge2-4.fr3.las.llnw.net [69.28.172.85]
14  319 ms  319 ms  319 ms  switch.ge3-1.fr3.las.llnw.net [208.111.176.2]
15  334 ms  335 ms    *    cust-199.189.116.246.sinap-tix.com [199.189.116.
246]
16  332 ms    *      331 ms  sony.demarc3.sinap-tix.com [64.79.157.78]
17  331 ms  333 ms  331 ms  vl3102.lvssw-2.sonyonline.net [64.37.168.10]
18  331 ms  331 ms    *    lvseq2-04-01.everquest2.com [69.174.200.40]
19    *      31 ms    32 ms  lvseq2-04-01.everquest2.com [69.174.200.40]
 
Trace complete.

Code:

Tracing route to lvseq2-04-01.everquest2.com [69.174.200.40]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     5 ms     4 ms     4 ms  74.100.141.1
  3     7 ms     7 ms     7 ms  G0-3-0-1.LSANCA-LCR-22.verizon-gni.net [130.81.1
78.238]
  4     6 ms     6 ms     6 ms  so-3-1-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.199.40]
  5    40 ms     6 ms     7 ms  0.so-2-1-0.XT2.LAX7.ALTER.NET [152.63.10.149]
  6     7 ms    36 ms     6 ms  0.xe-11-1-0.XL4.LAX1.ALTER.NET [152.63.112.117]

  7     6 ms     7 ms     7 ms  0.xe-11-1-0.GW2.LAX1.ALTER.NET [152.63.4.193]
  8     8 ms     9 ms    10 ms  customer.alter.net.customer.alter.net [152.179.1
03.2]
  9    12 ms    11 ms    10 ms  te-2-0-0-6-cr01.losangeles.ca.ibone.comcast.net
[68.86.82.57]
 10     8 ms     9 ms     9 ms  he-0-0-0-0-pe02.600wseventh.ca.ibone.comcast.net
 [68.86.83.18]
 11     7 ms    25 ms     8 ms  66.208.216.218
 12     9 ms    18 ms     8 ms  ve6.fr4.lax.llnw.net [69.28.171.206]
 13    16 ms    15 ms    15 ms  tge2-4.fr3.las.llnw.net [69.28.172.85]
 14    14 ms    14 ms    13 ms  switch.ge3-1.fr3.las.llnw.net [208.111.176.2]
 15   130 ms   223 ms   203 ms  cust-199.189.116.246.sinap-tix.com [199.189.116.
246]
 16    31 ms    31 ms    31 ms  sony.demarc3.sinap-tix.com [64.79.157.78]
 17    34 ms    32 ms    31 ms  vl3102.lvssw-2.sonyonline.net [64.37.168.10]
 18    31 ms    32 ms    32 ms  lvseq2-04-01.everquest2.com [69.174.200.40]

Trace complete.

Code:

Tracing route to lvseq2-04-01.everquest2.com [69.174.200.40]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2    4 ms    4 ms    5 ms  74.100.141.1
  3    10 ms    6 ms    9 ms  G0-3-0-1.LSANCA-LCR-22.verizon-gni.net [130.81.1
78.238]
  4    22 ms    6 ms    6 ms  so-3-1-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.199.40]
  5    6 ms    7 ms    6 ms  0.so-2-1-0.XT2.LAX7.ALTER.NET [152.63.10.149]
  6    7 ms    7 ms    7 ms  0.xe-11-1-0.XL4.LAX1.ALTER.NET [152.63.112.117]
 
  7    7 ms    36 ms    73 ms  0.xe-11-1-0.GW2.LAX1.ALTER.NET [152.63.4.193]
  8  287 ms  323 ms  288 ms  customer.alter.net.customer.alter.net [152.179.1
03.2]
  9  284 ms    *      286 ms  te-2-0-0-6-cr01.losangeles.ca.ibone.comcast.net
[68.86.82.57]
10  191 ms  124 ms    70 ms  he-0-0-0-0-pe02.600wseventh.ca.ibone.comcast.net
[68.86.83.18]
11    17 ms    16 ms    8 ms  66.208.233.14
12    19 ms    8 ms    16 ms  ve6.fr4.lax.llnw.net [69.28.171.206]
13    32 ms    19 ms    24 ms  tge2-4.fr3.las.llnw.net [69.28.172.85]
14    15 ms    14 ms    14 ms  switch.ge3-1.fr3.las.llnw.net [208.111.176.2]
15    30 ms    30 ms    30 ms  cust-199.189.116.246.sinap-tix.com [199.189.116.
246]
16    30 ms    30 ms    30 ms  sony.demarc3.sinap-tix.com [64.79.157.78]
17    31 ms    30 ms    35 ms  vl3102.lvssw-2.sonyonline.net [64.37.168.10]
18    30 ms    31 ms    30 ms  lvseq2-04-01.everquest2.com [69.174.200.40]
 
Trace complete.

Code:

Tracing route to lvseq2-04-01.everquest2.com [69.174.200.40]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2    4 ms    5 ms    4 ms  74.100.141.1
  3    9 ms    6 ms    7 ms  G0-3-0-1.LSANCA-LCR-22.verizon-gni.net [130.81.1
78.238]
  4    6 ms    6 ms    6 ms  so-3-1-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.199.40]
  5    7 ms    7 ms    7 ms  0.so-2-1-0.XT2.LAX7.ALTER.NET [152.63.10.149]
  6    7 ms    8 ms    7 ms  0.xe-11-1-0.XL4.LAX1.ALTER.NET [152.63.112.117]
 
  7    7 ms    7 ms    7 ms  0.xe-11-1-0.GW2.LAX1.ALTER.NET [152.63.4.193]
  8  293 ms  293 ms  293 ms  customer.alter.net.customer.alter.net [152.179.1
03.2]
  9  297 ms  298 ms  295 ms  te-2-0-0-6-cr01.losangeles.ca.ibone.comcast.net
[68.86.82.57]
10  294 ms  292 ms  293 ms  he-0-0-0-0-pe02.600wseventh.ca.ibone.comcast.net
[68.86.83.18]
11  304 ms  291 ms  289 ms  66.208.229.234
12    9 ms    26 ms    8 ms  ve6.fr4.lax.llnw.net [69.28.171.206]
13    24 ms    24 ms    34 ms  tge2-4.fr3.las.llnw.net [69.28.172.85]
14    14 ms    14 ms    15 ms  switch.ge3-1.fr3.las.llnw.net [208.111.176.2]
15    31 ms    30 ms    30 ms  cust-199.189.116.246.sinap-tix.com [199.189.116.
246]
16    31 ms    30 ms    31 ms  sony.demarc3.sinap-tix.com [64.79.157.78]
17  235 ms  278 ms  322 ms  vl3102.lvssw-2.sonyonline.net [64.37.168.10]
18    *        *      320 ms  lvseq2-04-01.everquest2.com [69.174.200.40]
 
Trace complete.

Code:

Tracing route to lvseq2-04-01.everquest2.com [69.174.200.40]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2    5 ms    4 ms    4 ms  74.100.141.1
  3    9 ms    10 ms    12 ms  G0-3-0-1.LSANCA-LCR-22.verizon-gni.net [130.81.1
78.238]
  4    8 ms    7 ms    7 ms  so-3-1-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.199.40]
  5    7 ms    8 ms    7 ms  0.so-2-1-0.XT2.LAX7.ALTER.NET [152.63.10.149]
  6    9 ms    7 ms    8 ms  0.xe-11-1-0.XL4.LAX1.ALTER.NET [152.63.112.117]
 
  7    9 ms    7 ms    7 ms  0.xe-11-1-0.GW2.LAX1.ALTER.NET [152.63.4.193]
  8    8 ms    10 ms    9 ms  customer.alter.net.customer.alter.net [152.179.1
03.2]
  9    12 ms    12 ms    13 ms  te-2-0-0-6-cr01.losangeles.ca.ibone.comcast.net
[68.86.82.57]
10    10 ms    10 ms    9 ms  he-0-0-0-0-pe02.600wseventh.ca.ibone.comcast.net
[68.86.83.18]
11    13 ms    8 ms    8 ms  66.208.229.234
12    11 ms    9 ms    9 ms  ve6.fr4.lax.llnw.net [69.28.171.206]
13    16 ms    16 ms    28 ms  tge2-4.fr3.las.llnw.net [69.28.172.85]
14    15 ms    15 ms    14 ms  switch.ge3-1.fr3.las.llnw.net [208.111.176.2]
15    30 ms    32 ms    31 ms  cust-199.189.116.246.sinap-tix.com [199.189.116.
246]
16  109 ms  128 ms  152 ms  sony.demarc3.sinap-tix.com [64.79.157.78]
17  322 ms  331 ms    *    vl3102.lvssw-2.sonyonline.net [64.37.168.10]
18  326 ms  327 ms  326 ms  lvseq2-04-01.everquest2.com [69.174.200.40]
 
Trace complete.

Code:

Tracing route to lvseq2-04-01.everquest2.com [69.174.200.40]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2    4 ms    4 ms    4 ms  74.100.141.1
  3    7 ms    7 ms    9 ms  G0-3-0-1.LSANCA-LCR-22.verizon-gni.net [130.81.1
78.238]
  4    6 ms    6 ms    6 ms  so-3-1-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.199.40]
  5    6 ms    6 ms    6 ms  0.so-2-1-0.XT2.LAX7.ALTER.NET [152.63.10.149]
  6    7 ms    6 ms    7 ms  0.xe-11-1-0.XL4.LAX1.ALTER.NET [152.63.112.117]
 
  7    6 ms    69 ms    6 ms  0.xe-11-1-0.GW2.LAX1.ALTER.NET [152.63.4.193]
  8    32 ms    9 ms    8 ms  customer.alter.net.customer.alter.net [152.179.1
03.2]
  9    12 ms    10 ms    12 ms  te-2-0-0-6-cr01.losangeles.ca.ibone.comcast.net
[68.86.82.57]
10    10 ms    10 ms    8 ms  he-0-0-0-0-pe02.600wseventh.ca.ibone.comcast.net
[68.86.83.18]
11    8 ms    12 ms    17 ms  66.208.229.234
12    18 ms    9 ms    8 ms  ve6.fr4.lax.llnw.net [69.28.171.206]
13    23 ms    25 ms    32 ms  tge2-4.fr3.las.llnw.net [69.28.172.85]
14    14 ms    14 ms    14 ms  switch.ge3-1.fr3.las.llnw.net [208.111.176.2]
15    30 ms    32 ms    30 ms  cust-199.189.116.246.sinap-tix.com [199.189.116.
246]
16    91 ms  110 ms  134 ms  sony.demarc3.sinap-tix.com [64.79.157.78]
17  310 ms  321 ms    *    vl3102.lvssw-2.sonyonline.net [64.37.168.10]
18  317 ms  317 ms  318 ms  lvseq2-04-01.everquest2.com [69.174.200.40]
 
Trace complete.