[Edited]: High ping time on Seattle area node 24.124.128.162 during evening/night hours.

wow I live in WA this was not only me .. ping goes up after 5pm no matter what this is crazy

... traceroute to google dns ...

Again, in that trace the "delays" at hops 7 and 8 are only apparent delays, not real ones. Replies to trace packets are a bit sluggish, but data packets are being forwarded on quickly. If they were not, we wouldn't see packets are reaching the destination and replies coming back in an average of just 11 ms. As stated above, such "delays" are annoying when running pings and traces, but not actually slowing down data transfer. And again, please see https://www.dslreports.com/faq/14068, which applies to delayed trace packets as well as lost trace packets.

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

@BruceW 

The issue starts at 24.124.128.162 and the pings stay high all the way to the destination. (With packet loss) 

Before breaking out "Pingplotter" I noticed high pings and lag to my azure VM in the evenings.

My fiends that live north of Seattle don't see the issue as I suspect they are being routed through a different psychical port on this virtual IP.

... The issue starts at 24.124.128.162 and the pings stay high all the way to the destination ...

Could you post a trace that shows that? So far in this thread we've only seen partial traces, or traces to Google's DNS. Partial traces aren't really helpful, and I assume that Google DNS is not the host of interest. A complete trace to a destination you are having a problem with would be much more meaningful.

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

I would show a Valorant trace if I could, since I know for sure it's being affected (80+ ms ping), but it keeps ending being "blackholed," i.e. "???" showing up in mtr/Request timed out. This is why I did a Google DNS trace. This is the trace for the server of another popular online application, Overwatch, but I don't know if it's representative of the actual gameplay as I don't play it. It does seem like it is affected.

Overwatch:

Start: 2023-05-07T17:56:35-0700
HOST: xxxxxxxxxxxxxxx             Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- blah                       0.0%    10    0.2   0.2   0.1   0.2   0.0
  2.|-- blah                       0.0%    10    4.7   0.9   0.5   4.7   1.3
  3.|-- 96.120.101.137             0.0%    10    8.8   9.5   7.3  11.3   1.1
  4.|-- 24.153.84.65               0.0%    10    9.7  10.3   7.6  18.8   3.1
  5.|-- 69.139.162.106             0.0%    10    9.7   9.8   8.6  12.5   1.5
  6.|-- 69.139.162.53              0.0%    10   10.3  10.3   7.8  13.8   1.6
  7.|-- 24.124.128.162             0.0%    10   68.0  72.9  63.6  81.4   5.4
  8.|-- 68.86.93.5                 0.0%    10   60.3  69.7  60.3  75.5   4.9
  9.|-- 96.110.32.230              0.0%    10   71.9  74.5  65.6  79.6   4.5
 10.|-- 50.242.149.178             0.0%    10   76.0  77.5  71.5  84.1   4.2
 11.|-- 137.221.73.33              0.0%    10   43.0  44.0  34.6  76.6  12.2
 12.|-- 137.221.65.40              0.0%    10   35.7  35.5  32.5  37.2   1.3
 13.|-- 137.221.65.117             0.0%    10   36.0  35.7  33.4  43.0   2.8
 14.|-- 137.221.65.6               0.0%    10   53.9  44.9  32.3  85.1  17.1
 15.|-- 137.221.68.93              0.0%    10   33.9  35.4  32.6  41.5   2.5
 16.|-- 24.105.30.129              0.0%    10   34.7  37.6  34.1  47.4   3.9

Valorant, if you are curious:

Start: 2023-05-07T18:03:45-0700
HOST: xxxxxxxxxxxxxxxx            Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- blah                       0.0%     5    0.2   0.2   0.1   0.4   0.1
  2.|-- blah                       0.0%     5    0.5   0.6   0.5   0.7   0.1
  3.|-- 96.120.101.137             0.0%     5    8.8   8.4   7.3  10.0   1.1
  4.|-- 24.153.84.65               0.0%     5    9.6   9.7   7.6  14.3   2.7
  5.|-- 69.139.162.106             0.0%     5   11.4  10.1   7.6  11.9   1.7
  6.|-- 69.139.162.53              0.0%     5    7.2  10.2   6.6  18.7   4.9
  7.|-- 24.124.128.162             0.0%     5   72.7  73.8  70.0  77.7   3.1
  8.|-- 68.86.93.5                 0.0%     5   70.4  72.4  69.1  77.1   3.2
  9.|-- 96.110.39.206              0.0%     5   74.2  72.8  64.5  77.0   5.2
 10.|-- ???                       100.0     5    0.0   0.0   0.0   0.0   0.0

Issue still occurring 5/7/2023 6:00pm with multiple more people confirming slowdowns in the evening specifically with video streaming and ping latency in video games. Ran traceroutes in the afternoon and its fine and then increase of 70ms on the suspicous ips at around 6:00pm. This makes streams/videos buffer when they did not previously and game ping increase by at least a multiple of 2x in all games. Reddit post a lot more active than here with more logs. Multiple people talking about switching companies and those who only have xfinity as their choice are calling techs non stop. Tracerts are helping and the suspicious IPs are the same but its hard to pinpoint anything with a problem that spans from south Seattle to at least Federal way so you know... we dont got the resources but I know who does. Moledig has the right idea. 

FYI, I'm on the northeast eastside of Renton. 

So, the tech contractor came out today and I explained the issue. After talking to his manager, he did the only thing he could do and opened an internal trouble ticket with Xfinity. This won't resolve the issue but if enough people get enough cases open it might get some visibility.

Trace to VM, it is located in one of the Easter Washington datacenters. If I ping back to 24.124.128.162 from the VM the pings are less than 10.

(Left off the IP of the VM for obvious reasons) 😊

Can confirm that the exact same problem is occurring to me. From 5PM to midnight, every day (week day or weekend), ping goes 120ms+ and the speeds go under 100Kbps, coupled with connection drops every few minutes. It became quite literally unusable - a 4G LTE device produces a more stable and fast connection at that point.

Like clockwork, here we go again with the service degradation for May 8th:

I used the Direct Message button on this page to send a message to "Xfinity Support" and was told.

"Our techs are aware of the issue and are investigating the cause to get this resolved as quickly as possible." - @XfinityTimothyA

We are getting the same message in my other thread.

‎Need network support in Seattle area on node/router/switch 24.124.128.162 | Xfinity Community Forum

Is it just me who is fascinated with how such a large company needs to take a month to investigate a node issue that is clearly reproducible and affects quite a few customers in the region?

Running tracert right this moment, seems like the same node is having issues today as well.

  3    13 ms     9 ms    10 ms  po-304-1245-rur201.burien.wa.seattle.comcast.net [96.110.248.45]
  4    11 ms    11 ms    11 ms  po-2-rur202.burien.wa.seattle.comcast.net [69.139.162.106]
  5    10 ms    10 ms     9 ms  po-200-xar02.burien.wa.seattle.comcast.net [69.139.162.53]
  6    76 ms    72 ms    73 ms  24.124.128.162
  7    13 ms    10 ms    12 ms  50.222.176.218
  8    13 ms    11 ms    12 ms  142.251.50.45
  9    80 ms    81 ms    72 ms  142.251.50.245
 10    11 ms    11 ms    17 ms  sea09s28-in-f14.1e100.net [142.251.33.78]

Hey, me too! Xfinity, are you looking at this?

It's been happening since 2023-04-18 as others have mentioned:

~ $ ping ping-naw.ds.on.epicgames.com
PING ping-naw.ds.on.epicgames.com (52.41.253.108) 56(84) bytes of data.
64 bytes from ec2-52-41-253-108.us-west-2.compute.amazonaws.com (52.41.253.108): icmp_seq=1 ttl=26 time=77.9 ms
64 bytes from ec2-52-41-253-108.us-west-2.compute.amazonaws.com (52.41.253.108): icmp_seq=2 ttl=26 time=76.0 ms
64 bytes from ec2-52-41-253-108.us-west-2.compute.amazonaws.com (52.41.253.108): icmp_seq=3 ttl=26 time=82.5 ms
64 bytes from ec2-52-41-253-108.us-west-2.compute.amazonaws.com (52.41.253.108): icmp_seq=4 ttl=26 time=80.6 ms
64 bytes from ec2-52-41-253-108.us-west-2.compute.amazonaws.com (52.41.253.108): icmp_seq=5 ttl=26 time=74.6 ms
64 bytes from ec2-52-41-253-108.us-west-2.compute.amazonaws.com (52.41.253.108): icmp_seq=6 ttl=26 time=67.5 ms
64 bytes from ec2-52-41-253-108.us-west-2.compute.amazonaws.com (52.41.253.108): icmp_seq=7 ttl=26 time=75.0 ms
^C
--- ping-naw.ds.on.epicgames.com ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6008ms
rtt min/avg/max/mdev = 67.493/76.279/82.465/4.490 ms
~ $ traceroute -A ping-naw.ds.on.epicgames.com
traceroute to ping-naw.ds.on.epicgames.com (44.230.113.121), 30 hops max, 60 byte packets
 1  _gateway (192.168.0.1) [*]  0.375 ms  0.508 ms  0.621 ms
 2  ***.***.***.93 (***.***.***.93) [AS7922]  8.356 ms  9.625 ms  14.366 ms
 3  ***.***.wa.seattle.comcast.net (***.***.***.9) [AS7922]  14.529 ms  14.626 ms  15.006 ms
 4  ***.***.wa.seattle.comcast.net (***.***.***.106) [AS7922]  14.293 ms  15.891 ms  15.882 ms
 5  ***.***.wa.seattle.comcast.net (***.***.***.53) [AS7922]  16.151 ms  16.017 ms  16.301 ms
 6  24.124.128.162 (24.124.128.162) [AS7922]  83.459 ms  77.039 ms  77.311 ms
 7  be-36111-cs01.seattle.wa.ibone.comcast.net (68.86.93.1) [AS7922]  80.702 ms be-36131-cs03.seattle.wa.ibone.comcast.net (68.86.93.9) [AS7922]  81.515 ms  80.862 ms
 8  * be-2411-pe11.seattle.wa.ibone.comcast.net (96.110.32.238) [AS7922]  77.425 ms be-2412-pe12.seattle.wa.ibone.comcast.net (96.110.34.142) [AS7922]  77.197 ms
 9  75.149.228.178 (75.149.228.178) [AS7922]  83.890 ms 66.208.233.10 (66.208.233.10) [AS33668]  105.102 ms 75.149.228.178 (75.149.228.178) [AS7922]  84.254 ms
10  52.95.53.195 (52.95.53.195) [AS16509/AS14618]  78.822 ms 150.222.214.187 (150.222.214.187) [AS16509]  90.324 ms *
11  52.95.53.145 (52.95.53.145) [AS16509/AS14618]  87.351 ms 52.95.54.234 (52.95.54.234) [AS16509/AS14618]  84.680 ms 52.95.53.129 (52.95.53.129) [AS16509/AS14618]  83.717 ms
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  150.222.251.140 (150.222.251.140) [AS16509]  85.146 ms 52.93.131.140 (52.93.131.140) [AS16509]  71.857 ms 150.222.255.124 (150.222.255.124) [AS16509]  85.846 ms
18  * * *
19  * * *
20  * * *
21  * * *
22  * * 54.239.45.105 (54.239.45.105) [AS16509]  76.106 ms
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Strangely, Google seems fine but only over IPv6:

~ $ ping www.google.com
PING www.google.com(sea09s29-in-x04.1e100.net (2607:f8b0:400a:80a::2004)) 56 data bytes
64 bytes from sea09s29-in-x04.1e100.net (2607:f8b0:400a:80a::2004): icmp_seq=1 ttl=58 time=7.08 ms
64 bytes from sea09s29-in-x04.1e100.net (2607:f8b0:400a:80a::2004): icmp_seq=2 ttl=58 time=10.0 ms
64 bytes from sea09s29-in-x04.1e100.net (2607:f8b0:400a:80a::2004): icmp_seq=3 ttl=58 time=8.46 ms
64 bytes from sea09s29-in-x04.1e100.net (2607:f8b0:400a:80a::2004): icmp_seq=4 ttl=58 time=10.1 ms
64 bytes from sea09s29-in-x04.1e100.net (2607:f8b0:400a:80a::2004): icmp_seq=5 ttl=58 time=4.58 ms
^C
--- www.google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4007ms
rtt min/avg/max/mdev = 4.578/8.037/10.066/2.052 ms
~ $ ping4 www.google.com
PING  (172.217.14.196) 56(84) bytes of data.
64 bytes from sea30s01-in-f4.1e100.net (172.217.14.196): icmp_seq=1 ttl=57 time=78.2 ms
64 bytes from sea30s01-in-f4.1e100.net (172.217.14.196): icmp_seq=2 ttl=57 time=73.0 ms
64 bytes from sea30s01-in-f4.1e100.net (172.217.14.196): icmp_seq=3 ttl=57 time=72.5 ms
64 bytes from sea30s01-in-f4.1e100.net (172.217.14.196): icmp_seq=4 ttl=57 time=66.2 ms
64 bytes from sea30s01-in-f4.1e100.net (172.217.14.196): icmp_seq=5 ttl=57 time=64.9 ms
64 bytes from sea30s01-in-f4.1e100.net (172.217.14.196): icmp_seq=6 ttl=57 time=70.9 ms
^C
---  ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5008ms
rtt min/avg/max/mdev = 64.888/70.949/78.151/4.432 m

Fortnite is showing around 100ms in-game, which introduces noticeable lag. Yes, everything is hard-wired and yes, I have rebooted things to see if it miraculously fixes it.