Unusual Lag Spikes?

Quote:

---

Originally Posted by szalkerous

Anyone been in game post-hotfix downtime that can verify if it is fixed?

---

The lag issues are most likely network related as usual. As has been noted in several of the other recent lag threads, some key circuits went down last night.

So me and my static's OT are Comcast. Both had terrible lag spikes last night in Thordan. This is funny because the two of us NEVER have connection issues. We're usually the ones rolling our eyes when others in the group complain about lag. Karma is a bitch I suppose.

Check out status reports for services at www.downdetector.com/companies . Just might start to see a pattern...

http://downdetector.com/status/comcast-xfinity
http://downdetector.com/status/att
http://downdetector.com/status/time-warner-cable
http://downdetector.com/status/verizon-communications
http://downdetector.com/status/playstation-network
http://downdetector.com/status/xbox-live

Seems fixed for me.

Quote:

---

Originally Posted by Raist

Are you sure that is the IP you are now using? I don't mean looking it up at ARR Status either---those haven't been entirely accurate for well over a year now. Have you looked up what IP you are using when fully logged into the game (with something like resmon or netstat)?

Reason I ask is we have seen a lot of people got switched to IP's above 100 when they broke out the new EU location. Those older lower IP's may not be actually hosting world services now.

Edit: Looks like 199.91.189.39 may not be running world service anymore. It is still responding to pings when things are down for the patch--should be timing out when the worlds are taken down. Did catch a hop in the Newark area that is going AWOL atm though when pinging around just now. So, looks like more of the usual infrastructure crud we've wrangled with for nigh on 20 years now.

---

Nope that is indeed the Famfrit server IP. Also I'm pinging again right now as well as in game. Currently no issues.

Quote:

---

Originally Posted by Raist

May want to verify what address you actually use once we can get back in game (resmon or netstat when fully logged in). The IP's got reshuffled with the opening of the new EU datacenter--many are now above 100. That .35 IP (amongst others in the lower ranges) are still responding to pings when the worlds have gone offline. They shouldn't be. The newer ones we've seen in play since the new EU datacenter opened are currently down as they should be.

---

http://i.imgur.com/rHAfBOk.png

That's with a fresh log-in. So, unless the resource monitor is lying, that's what I've got. And even tonight, though this guildhest went off without any noticeable latency issues, when I do tracert it STILL bugs out at that fourth hop...

EDIT: well despite the above, at least the symptoms appear to be gone. Here's my ping report. Cross my fingers that it stays like this.

Code:

---

Ping statistics for 199.91.189.35:
    Packets: Sent = 200, Received = 200, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 28ms, Maximum = 59ms, Average = 39ms

---

Nope STILL rubber-banding in Seal Rock, and this was even just 24-man. Even for a reset night it's never this bad. :|

Getting more lag spikes tonight for the 3rd night in a row. The game seems perfectly fine during the early mornings to mid afternoon, but around 7 PM EST is when the spikes start happening to the point where it becomes unplayable. And this is the only online game I play where the issues are very noticeable.

Anyone else still suffering from these issues? I've a mind to call Comcast tomorrow to see what's going on over on their end.

Still getting it. Behemoth :/

I've been noticing a few all day today. Nothing major for the most part, just times where skills wouldn't react properly or NPC interfaces would take a moment to load up. I did have a moment earlier when running the expert roulette though where I had a full "everything stops for a few moments" spike, and when I mentioned it another party member said the same had happened to them.....

seeing a good bit of skip still through the NY/NJ corridors. Ohio still a hot mess for some providers. Chicago is going off the reservation as usual as well. Austin/Houston/Dallas are getting a bit rebellious too... nothing new. Ohio.. OMG.. those poor guys in Ohio just can't get a break...and it's running down into Kentucky as well. LA...well... Southern California in general is knackered up like it usually does. Seattle is even getting in on some of the action too, so people sling-shotting Vancouver over to Ontario may be getting more congestion than they are accustomed to atm.

Basically, the usual hotbeds for congestion seem to be in play again. May simply need to be leaning on your ISP's to clean things up.

Net usage on some key indexes are currently up 20-30% above the norm in North America today. The ISP's need to step up their game and improve their infrastructure to get with the times...more and more we depend on the internet for so many facets of our lives, and they just aren't keeping up worth a squat in some regions.

Here's an interesting app that tracks the stats by industry/regions. The page has other apps in the left side bar with more stats on the internet as well. Might help people understand it a bit better to see some numbers on the situation:
http://www4.akamai.com/html/technolo...try/index.html

Started up again for me this evening while I was crafting. I noticed it beginning around 9:15 EST. Made for slow going with all the skill lag.

Again, Comcast, No. Virginia.

edited to add: I am on PC, not console.

Logged in, still lagging =/

I cant get into any instance withotu getting horrible lag. Tried savage 1, thordan, couldnt do it :mad:

Still getting it bad, full on 'everything freezes in place' for like 4-5 seconds at a time. DPSing I'm not too nervous on, but I'm afraid to try to heal anything.

Occasionally when there seems to be talk of lag spikes or when someone brings it up I usually ask if they are on console or PC. My assumption is if most of the folks getting lag is on PSN then its a Sony thing. Or else its either a regional thing for the ISP or hardware at Square Enix. God forbid its a small attempt by someone to dos a service somewhere.

I'll probably call Comcast tomorrow if it doesn't improve. I'm going to blame "Cyber Monday" for the time being.

Comcast has been made aware of the issue with their DNS routing tables and have escalated the case. Provided them all of the logs ive been gathering the past couple days. Hopefully something soon can be done.

I was on between 6 and 10PM EST, and I had zero lag, which is a black and white improvement from the past two days.

Coming from comcast this "we are aware of it" means nothing.

FYI, as of this very moment, I'm recording a 17% packet loss over 60 seconds to Excalibur.

Still getting it. It appears to happen around night time. Server congestion maybe?

Not sure if this is a related issue....

http://www.theregister.co.uk/2015/11...eported_in_us/

Quote:

---

Originally Posted by Kurogaea

Still getting it. It appears to happen around night time. Server congestion maybe?

---

No, it's been pretty much sleuthed out to be a problem with the Level3 backbone.

been like this for me since the last hotfix, not sure thats going on but omg is the lag bad.
This is the first time I have had lag issues with the game

This is making Void Ark impossible, everyone is lagging horribly at Cuchulainn and wiping over and over.

Still practically unplayable here as well going on 4 days now (started monday) on Behemoth server. Most of my FC is experiencing the same lag spikes. I've heard using a VPN can alleviate the lag, but I'd rather play my game without third party software involved, getting to be bothersome!

The server hates the Diadem nerfs and is rebelling. Also I'm getting hit with massive lag over the past couple days as well and don't know why. Excalibur, again.

Still getting lag spikes, but I'm not with Comcast (Shaw is my ISP, western Canada). Nothing to report from their end, and I don't experience lag any where else.

Quote:

---

Originally Posted by KaijinRhada

Still getting lag spikes, but I'm not with Comcast (Shaw is my ISP, western Canada). Nothing to report from their end, and I don't experience lag any where else.

---

It's all about who your ISP teams up with as a backbone provider. If you do a tracert from you to the server IP, I bet you'll find Level3 in there around hop 6 or 7. That seems to be a common denominator as people with them in their routing can VPN around it and avoid the dropped packets entirely.

Here's an example of hops 5-12 for me on Comcast in the Boston area, headed to the Excalibur server (on a good day):

Code:

---

  5    15 ms    11 ms    16 ms  be-77-ar01.needham.ma.boston.comcast.net [68.87.146.194]
  6    10 ms    10 ms    14 ms  4.68.71.217
  7    44 ms    42 ms    45 ms  ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
  8    40 ms    38 ms    41 ms  ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
  9    39 ms    39 ms    42 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
 10    57 ms    56 ms    56 ms  192.34.76.10
 11    56 ms    57 ms    54 ms  199.91.189.242
 12    57 ms    54 ms    57 ms  199.91.189.45

---

During this lag, hops 8-12 (for me, your results may vary) will have extremely high response or will drop entirely. It's even easier to do a 100 count ping to the server and compile the packet loss percentage from that.

Code:

---

C:\>ping 199.91.189.45 -n 100

...

Ping statistics for 199.91.189.45:
    Packets: Sent = 100, Received = 93, Lost = 7 (7% loss),
Approximate round trip times in milli-seconds:
    Minimum = 53ms, Maximum = 64ms, Average = 55ms

---

You should have 0% loss if things are working correctly. I've been seeing between 5 and 20 percent loss during evening primetime this week.

Code:

---

7    44 ms    42 ms    45 ms  ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
8    40 ms    38 ms    41 ms  ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]

---

Oh that pesky level3 car2 hop, when will they ever fix that route? It's been showing up in buggered routes for years

I noticed while crafting that every time I lag is usually around 0000 hours (midnight) UK time.

This has been happening for over few days. Hope they look into it

I haven't (I believe) experienced any serious lag yet since I started playing. Can anybody describe what the lag looks/feels like?

Half my raid group is still experiencing lag, rubber banding, and DCs. We actually had to stop practice Tuesday night because we couldn't deal with resin placement during the jump. We were totally shocked to actually clear last night because our first few attempts were plagued with lag.

Quote:

---

Originally Posted by KaijinRhada

Still getting lag spikes, but I'm not with Comcast (Shaw is my ISP, western Canada). Nothing to report from their end, and I don't experience lag any where else.

---

It would be like this video here. At about 20 seconds you can see everyone stop, and then speed up to get to where they would be if they had kept running. Make that happen every 4-5 seconds and you have my experience in PVP and Trials all this weekend; to say nothing of trying to get around the city or open world.

Another symptom is having instant buffs show up 1-2 seconds after hitting the buttons. I've NEVER had this before. Example:
>Hit Swiftcast (Controller)
>Mouse over and click Summon Pet Macro
>Summon Pet hardcasts slow
>2 seconds later, Swiftcast starts ticking down on the buff bar

I knew I forgot to include something, so here's my fresh tracert from tonight (after step 2). It looks the same even if I use the IP from before, 199.91.189.35

Code:

---

Tracing route to 199.91.189.45 over a maximum of 30 hops

  3    10 ms    11 ms    9 ms  te-1-12-0-12-ar01.area4.il.chicago.comcast.net [
68.87.232.93]
  4    *        *        *    Request timed out.
  5    30 ms    30 ms    31 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

  6    30 ms    31 ms    30 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

  7    30 ms    31 ms    30 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
  8    28 ms    28 ms    27 ms  192.34.76.10
  9    28 ms    41 ms    28 ms  199.91.189.242
 10    29 ms    27 ms    28 ms  199.91.189.45

Trace complete.

---

Quote:

---

Originally Posted by Dotsusama

I knew I forgot to include something, so here's my fresh tracert from tonight (after step 2). It looks the same even if I use the IP from before, 199.91.189.35

Code:

---

Tracing route to 199.91.189.45 over a maximum of 30 hops

  3    10 ms    11 ms    9 ms  te-1-12-0-12-ar01.area4.il.chicago.comcast.net [
68.87.232.93]
  4    *        *        *    Request timed out.
  5    30 ms    30 ms    31 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

  6    30 ms    31 ms    30 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

  7    30 ms    31 ms    30 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
  8    28 ms    28 ms    27 ms  192.34.76.10
  9    28 ms    41 ms    28 ms  199.91.189.242
 10    29 ms    27 ms    28 ms  199.91.189.45

Trace complete.

---

---

With that redacted report, would have to say someone needs to investigate what is going on at the exchange point into Level3. Typically the reason it is enforcing a rule to not respond to ICMP at such a hop is because of imminent congestive failure. If you ever see a response from hop 4 when you run a trace, this is most likely the case.

If there is congestion or bad jitter at the omitted hops 1 or 2 it can also be impacting things further down. It is all cumulative. So if there is bad congestion locally and then again at somewhere like Vancouver/Ontario/Toronto along a Canadian path, the Great Lakes/Ohio/North East for northern US path, or Southern Cal/Texas/Kentucky otherwise (not sure exactly how far west you are, common points of congestion we've seen), it can be compounding the issue.

Also, keep in mind one of the drawbacks to low latency: because it scales against your normal latency, it doesn't take nearly as much variance to lead to an out-of-order packet. That can trigger retransmits and lead to stuttering/rubber-banding as well, even though your latency is normally low. In that sample we are seeing right at a 50% variance being triggered by something in groups of only 3 pings. Not a very good sign.

Quote:

---

Originally Posted by Raist

snip

---

I just cut the first two out of habit for public posting, both those first two hops are consistently 8~10ms each. I think out of the dozen or so times I've run this I've seen a response and an actual IP from 4 like... once. I even did a search on it so thankfully it was still in my history! It's another Level3 at 4.68.63.125.

EDIT (I keep doing this...): I mentioned it before, but I'm in Chicago proper, like some other users here with the complaints, and using Xfinity/Comcast. I did the tracert at work which is just a couple of blocks away, and that office uses AT&T Uverse DSL and STILL has the same damage at step 4.

yeah... that's a troubled spot for them too. Long/Lat (38/-97) in the geo data puts it around Wichita. Seen them report problems there frequently. Would hazard a guess that may be a solid point to investigate.

Looks like Level3 is still dealing with some downed circuits in general. Reports of one going down in Dallas today, and a sort of "rolling blackout" effect seems to be happening in California today as well. There was a tweet that they were working with TWC to address one circuit about 8 hours ago. Doesn't show where though. Could be along that Louisville/Cincinnati/Columbus/Cleveland run that has been flaking out for a little over a week now.

Level3 just seems to be knackered up in general these days...more so than usual. IDK why some ISP's are so reluctant to switch away from them, even if just for 30 days or until their next announcement cycle kicks off.

Keep DCing randomly, not my computer's problem or internet's problem either.... :(

Quote:

---

Originally Posted by MihaelB

Keep DCing randomly, not my computer's problem or internet's problem either.... :(

---

Did you check every hop between you and SE's servers? Hard to say with such certainty that it isn't an internet related problem without looking closely at the route.

Edit:
Just took a quick look at my route. Signs of heavy congestion here in South Carolina (around the Conway/Myrtle Beach area--high tourism/retail area), and again showing up around the New York/New Jersey segments. Not enough to trip me up much yet, but the potential is there if packet loss starts happening.