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

I am also seeing the same issue.  2 techs have come out and confirmed no issue at my house.  Seeing high ping time on the same 24.124.128.162 address every night.  I've been on the phone with Comcast many times over the last 2 weeks with no sign of this being resolved any time soon.  Any prior tickets, threads, reports of this issue are all closed as "resolved" and no one reaches out to confirm.  

It is EVERY night that this occurs.   Sunday is the worst starting at 1pm and going until 1am.  Average nights are around 5pm until 12:30am.  8pm is when the packet drops at that IP address start to occur.

I also have 4 others in the south seattle area that route through this IP reporting the same problem every night.

 2  10 ms  9 ms  13 ms 96.120.102.129
 3  11 ms  11 ms  8 ms po-306-1293-rur201.burien.wa.seattle.comcast.net [96.110.248.13]
 4  8 ms  8 ms  9 ms po-2-rur202.burien.wa.seattle.comcast.net [69.139.162.106]
 5  9 ms  9 ms  10 ms po-200-xar02.burien.wa.seattle.comcast.net [69.139.162.53]
 6  73 ms  79 ms  76 ms 24.124.128.162

all traffic out of my area looks like this in the evening.  All response times are low until the 24.124.128.162 address.  Again, 2 techs have been to my house and have proven that the issue is not at my house.  

The problem clearly appears to be the node or next jump after the Burien datacenter.

Now if we can just get someone from Comcast to take action.

Don't worry it's not just you experiencing this problem - https://www.reddit.com/r/Comcast_Xfinity/comments/1365tgz/still_having_latency_issues_around_5pm_for_the/

So, I'm sitting here watching the pings double from 15ms to 30ms right at 5pm. That must be some bandwidth monster of a backup kicking off......

And as others mentioned in the reddit thread there is 15% (and climbing) packet loss out of that hop. 

up to 40ms as I typed this...    (sad) 

Today I was once again told the issue has been "escalated". But that is what I am told each time I call. The case is still pending awaiting the tech to call me. Everyone should be calling in each day to get some visibility on this issue. My concern is that we had a latency issue in 2020 in Renton that was a thousand times worse than this and it took over a year to get repaired.

We are facing the same issue in Burien for the past few weeks. Low Latency applications are basically unusable at this time.

The issue is still occurring: 5/5/2023

https://www.reddit.com/r/Comcast_Xfinity/comments/131hu1j/internet_slowdown_in_seattle_area_from_4pm2am/. Another post here with more people affected. The actual number of people affected is large not just us who know how to diagnose. 

On the off chance that someone at Xfinity reads these I posted this in the customer service section.

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

@user_631655: The trace in the Reddit post you linked does show that 24.124.128.162 is slow to respond to trace packets, but the fact that hops past than one respond quickly indicates that the router at that address is doing its job: forwarding data packets. That means the delay in responding to trace packets, while annoying, is most likely not actually slowing down data transfer. Please see https://www.dslreports.com/faq/14068.

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 before the evening everyone gets 12-20ms at that that ip and just didnt include 1-4. Check the linked posts on it too silly. It's doing its job but slower after 5pm that's the whole point.

... before the evening everyone gets 12-20ms at that that ip and just didnt include 1-4 ...

Could you post a complete trace showing the problem? Including all hops from source to target?

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.

Issue still occurring. 5/6/2023

Start: 2023-05-06T18:55:20-0700
HOST: <Host>                      Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- <wan ip>                   0.0%    10    0.2   0.1   0.1   0.2   0.0
  2.|-- <private ip>               0.0%    10    0.5   0.5   0.5   0.6   0.0
  3.|-- 96.120.101.137             0.0%    10    8.9   8.9   7.5  11.1   1.0
  4.|-- 24.153.84.65               0.0%    10   16.9  10.5   7.5  16.9   2.8
  5.|-- 69.139.162.106             0.0%    10   11.1  10.8   7.6  18.1   2.8
  6.|-- 69.139.162.53              0.0%    10   10.3  12.0   8.1  30.1   6.4
  7.|-- 24.124.128.162             0.0%    10   81.2  79.6  68.8  91.8   5.7
  8.|-- 50.218.57.26               0.0%    10   68.2  78.7  68.2  89.4   7.0
  9.|-- 142.251.50.41              0.0%    10   17.2  18.1  11.5  22.8   3.5
 10.|-- 142.251.55.201             0.0%    10   16.4  12.3   9.0  25.1   5.0
 11.|-- 8.8.8.8                    0.0%    10   10.8  11.5   8.0  19.4   3.2

(edit, traceroute to google dns)

According this reddit post, the issue is as follows.

UPDATE4: Per u/shoosting**'s tech: "I got a great tech today. He came out said basically that I'm not the only one experiencing the problem and that he was going to reach out to maintenance to ask what's up.**

The response he got back was that they are/were performing upgrades and some of that work is held back by permitting right now. Because of this, it is saturating the route through 24.124.128.162. Unfortunately, no timeframe is available for when this issue will be fixed because it's stuck in red tape.

However, and r/Comcast_Xfinity listen up because this feedback needs to get escalated up the chain, I'm not mad now. I have knowledge of what the problem is and know that Comcast is working on the issue. [Edited: "Language"] Sure, but not being kept in the dark and having Comcast acknowledge that the issue is not on my end (after all the data I've provided) is a relief. Keeping this all internal and not telling the customer is really what gets us frustrated. If all of us are reporting the same problem and showing the same details of said problem, then sending tech's out or running us through the support agent gauntlet is just going to make everyone upset."

Can we get a confirmation that this is the issue? If the time frame for the fix is available, that would also be helpful, but if not, that's understandable.