[Ping] Game uplayable?

[Baingoleth]

Its not even busy right now exactly. I just got out of a 8vs8vs8 PvP run, and its spiked right now. I guess a quite a bit of people are on right now, but not as many during peak peak hours? But still?

Anyway, updated a post just before you posted and will repost this tracert

1.......<1ms.........<1ms............<1ms.........Router
2.......104ms...........101ms...........100ms.......Other
3........114ms...........118ms..........111ms........Local
4.......120ms...........117ms..........122ms.......Local
5.......123ms...........123ms..........128ms....GA-comcast
6........114ms...........123ms.........118ms......marietta.ga...comcast.net [68.86.88.178}
7.......128ms...........128ms.........120ms........50.242.151.58
8......136ms.............189ms.........178ms........Atlnha05 [129.250.5.59]
9......125ms.............126ms........140ms........atlnga05 [129.250.5.202]
10....155ms.............174ms.........155ms........dllstx09 [129.250.4.116]
11....168ms..............170ms.........176ms.......snjsca04 [129.250.4.154]
12....218ms..............208ms........188ms.......snjsca04 [129.250.6.119]
13....193ms..............299ms........205ms........scrmca02 [129.250.7.53]
14....204ms..............228ms........239ms.......scrmca02 [129.250.195.46]
15....187ms.............95ms...........92ms........FFXIV 204.2.229.254
16....184ms.............174ms..........178ms......Malboro 204.2.229.101


I find it odd that two of the packets or whatever they are, right before hitting malboro, and i guess the XIV cluster, it gets down to 95 and 92 randomly. Makes 0 sense to me.



My PC is hardwired to my router. Same for my security camera. The rest of my devices are wi-fi. Only "really" have issues with XIV, but I only really play XIV if i'm on the internet. I dont do much else on the internet haha.

Considering hop #2 is usually ~9ms, I would think that is something out in your neighbourhood. I don't want to say for certain without looking at a return path monitor but I would check if there is some bad ingress getting onto your line somewhere between your modem and whatever Comcast equipment is hop #2. Maybe the device at hop #2 is malfunctioning causing the massive pings. If you need your case escalated, send the first traceroute with hop #2 @ 9ms along with another one with hop #2 @ 100ms to Comcast and ask them to forward it on to whoever investigates node ingress in the back office. Maybe only a supervisor can do this. If you had service calls already, I would hope your home wiring has been swept correctly and the issue is not with your coax wiring. Again, maybe the people who watch for impairments in the back office already know about this but I have seen ingress and equipment issues get resolved quicker if customers start to escalate with good evidence. At least, we'd get a warning at my cable company every time node errors spike but impairments that affect an entire node that start to cause escalations goes out to maintenance usually same day. Can maintenance always find the problem right away? Not always but at least the impairment becomes a priority.

Also, you might see ICMP responses come back with a lower ping from a hop further away sometimes. Sometimes packets arrive out of order and need to be re-ordered. Sometimes hops are further away initiate a response quicker than a hop closer to you.