Skip to main content

    Support

    Offers

U
user_cuix7i
1st Topic
1st Reply
1st Accepted Solution

6 Messages

Monday, March 31st, 2025 8:20 PM

1000 MS ping spikes while gaming. I ran tests and it seems to stem from a node in Boston that has constant packetloss

Started getting awful ping spikes in games around 4-5 months ago. Tried doing everything possible to fix on my end, it happens on numerous modems. 

I ended up running a traceroute test to find the source of the problems. There seems to be a node from Boston that has constant packet loss of both sent and received packets. It is 15-20% packet loss constantly. I believe this is where the issue is lying. Could someone please look into fixing/swapping out this node. Pictures of test below , tested on a riot games IP

Question

 • 

Updated 

24 hours ago

18

3

user_cuix7i

6 Messages

4 days ago

Here are the tests that show the constant packet loss. This happens constantly time of day doesn’t matter https://imgur.com/a/fBY0Tqg

1

user_cuix7i

6 Messages

be-307-arsc1.needham.ma.boston.comcast.net
96.110.118.69

this is the node having issues. The drops are worse to riot/game servers but it’s there with Google and other tests as well. Please fix this 🙏🏻 

Like

Reply

4 days ago

0

BruceW

Gold Problem Solver

 • 

26.3K Messages

4 days ago

Please see https://web.archive.org/web/20230802010554/https://www.dslreports.com/faq/14068:

Why am I seeing so much packet loss in my provider's network?

If you are also seeing packet loss from these points all the way to the final hop of your test, that points to a problem on the device first showing packet loss or on the inbound connection to that device. However, if you are not seeing packet loss all the way to the final hop, this apparent packet loss may not be an issue.
Some providers are rate-limiting how often they respond with the TTL-exceeded ICMP packets used by traceroute and similar tools like the Packet Loss Test. This is done to prevent attacks against these routers, since responding to these packets requires much more CPU time than simply forwarding the packet does. If the router is set up to rate-limit, it will respond to a certain number of traceroute packets per second, and once that many have been received, it will stop responding to them for that second -- which will appear as packet loss. You are not losing any "real" traffic, assuming the final hop of your traceroute isn't showing any loss.

In the image where 490 packets were sent, the target received 489, so just 1 packet was "lost". In the image where 813 packets were sent, the target received 811, so just 2 packets were "lost". This indicates that the router you are concerned about is doing its job: forwarding data packets. The occasional apparent delay in or failure to respond to trace packets, while annoying, is most likely not actually slowing down data transfer. If it was we'd see high RTT values and/or packet loss carrying through to later hops, and we don't. You may indeed have a communication problem, but the trace does not show that. Except: see ETA below.

Interpreting trace results is tricky. What appears to be "late" or is reported as "lost" could mean 1) the packet did not reach or was delayed in reaching that hop, or 2) the router at that hop didn't reply or was slow to reply, or 3) the reply from that hop didn't make it back or was delayed in making it back to the trace program.

ETA: I'm puzzled by the 172.27.x.y IP at hop #2. It's a private IP, not the public IP I would expect to see after your in-home gateway router. Any idea what that is?
The very high "Worst" RTTs in the one of the traceroutes suggests that there is a problem with the connection between your gateway and the first Comcast hop. You might want to check out Internet Troubleshooting Tips.
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.

(edited)

1

user_cuix7i

6 Messages

It’s happened through 4 different modems/routers it isn’t a hardware or cord issue. The lag is only occurring on the Boston node so it’s on Comcast’s end. It’s only noticeable in games so they won’t fix it

Like

Reply

24 hours ago

0

XfinityEva

Official Employee

 • 

1.6K Messages

4 days ago

Thank you, we appreciate you taking these steps with your connectivity concerns. We would recommend checking out our Internet Troubleshooting Tips here for more in depth troubleshooting. 

3

0

user_cuix7i

6 Messages

Sorry but troubleshooting on my end cannot fix this. You can see from the tests I provided that there is a Comcast node dropping large amounts of packets constantly 

Like

Reply

4 days ago

0

user_cuix7i

6 Messages

Is there anyway to open a ticket with tier 2 support who would know more about routing?

Like

Reply

4 days ago

0

XfinityRaf

Official Employee

 • 

809 Messages

If you could send our team a direct message with your full name and full address, we can further investigate.
 

To send a "Direct Message" ("Private") message:

• Click "Sign In" if necessary

• Click the "Direct Message chat" icon

• Click the "New message" (pencil and paper) icon

• Type "Xfinity Support" in the "To:" line and select "Xfinity Support" from the drop-down list which appears. The "Xfinity Support" graphic replaces the "To:" line

• Type your message in the text area near the bottom of the window

• Press Enter to send it

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

Like

Reply

4 days ago

0

forum icon

New to the Community?

Start Here