Skip to main content
apakis
1st Topic
1st Like

Visitor

 • 

4 Messages

Monday, August 3rd, 2026 11:56 PM

High Latency/Congestion at Dallas ibone node (be-34932-cs03.dallas.tx.ibone.comcast.net)

Hi!

I am experiencing severe latency spikes starting at a specific Comcast core backbone router in Dallas. The connection is completely clean through Tennessee, but latency explodes from ~17ms to nearly 300ms the moment it hits the Dallas ibone node.
Because the high latency persists through all subsequent hops into the destination network, I think this is a genuine routing/link bottleneck but I also do not know for sure. I just know that when I play what I am trying to play my match gets terminated by matchmaking handler rules due to the high latency persisting. Could a forum moderator please escalate this traceroute to the Network Operations Center (NOC) or Tier 3 routing engineers to check the health/capacity of this link? Below I have provided the tests I ran after noticing this. 

This is being tested with an address that I think is associated with handling peer to peer connections for the game I am trying to play that I first noticed this issue on. It is a Google Cloud address. 

tracert:

Tracing route to 193.153.173.34.bc.googleusercontent.com [34.173.153.1.93]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  10.0.0.1
  2    17 ms    17 ms    13 ms  100.92.75.122
  3    15 ms    13 ms    12 ms  po-123-rur401.winchester.tn.malt.comcast.net [68.85.54.221]
  4    15 ms    17 ms    26 ms  po-2-rur402.winchester.tn.malt.comcast.net [96.108.30.170]
  5    18 ms    17 ms     8 ms  po-400-xar02.winchester.tn.malt.comcast.net [96.108.30.49]
  6    16 ms    14 ms    14 ms  68.86.240.1
  7    21 ms    17 ms    16 ms  68.86.240.22
  8   310 ms   309 ms   242 ms  be-34932-cs03.dallas.tx.ibone.comcast.net [68.86.95.121]
  9   255 ms   278 ms   301 ms  be-3311-pe11.1950stemmons.tx.ibone.comcast.net [96.110.34.90]
 10   259 ms   290 ms   284 ms  193.153.173.34.bc.googleusercontent.com [34.173.153.193]

sustained ping test:

Ping statistics for 34.173.153.193:
Packets: Sent = 423, Received = 417, Lost = 6 (1% loss),

Approximate round trip times in milli-seconds:
Minimum = 223ms, Maximum = 335ms, Average = 302ms

For what it is worth, the loss looks ok...latency bad. 

Question

 • 

Updated 

33 seconds ago

 • Edited

29

2

Oldest First
Selected Oldest First
user_ukllvk

Visitor

 • 

1 Message

2 hours ago

Summary: Approximately 250ms of latency is being added on a single hop within Comcast's network, affecting all traffic routed through the Dallas backbone site. Requesting escalation to network engineering.

Local network confirmed healthy: Traces to 1.1.1.1 complete in 16ms via 162.151.119.230. Hops 1–7 are consistently 8–17ms across all tests. Last mile, modem, and CMTS are not implicated.

Affected destinations (all 260–335ms round trip): 8.8.8.8 (304ms), Google web 192.178.152.139 (335ms), Linode Dallas 50.116.25.154 (282ms), Linode Newark 50.116.57.237 (279ms), OpenDNS 208.67.222.222 (288ms), ICANN root server 199.7.83.42 (266ms).

Common failure point: Every affected trace is normal through 68.86.240.22, then enters cs03.dallas.tx.ibone.comcast.net and jumps immediately. Example from the 199.7.83.42 trace — hop 7 68.86.240.22 at 10ms, hop 8 68.86.95.121 at 247ms. Affected interfaces observed: 68.86.95.113, 68.86.95.117, 68.86.95.121, 68.86.106.170, 96.110.34.82, 96.110.34.86, 96.110.34.106, 96.110.34.161, 96.110.42.210.

Why this is not a false positive: Elevated latency is present at the destination endpoints, not only at intermediate hops, so it is not ICMP deprioritization. The minimum latency at the affected hop is ~223ms in sustained PingPlotter monitoring, which indicates a path/transport problem rather than congestion — congestion produces a low minimum with a high average. Six destinations across unrelated networks are affected, ruling out a peering issue with any single provider. Nine distinct router interfaces are affected, ruling out a single-device fault.

Request: Please review the transport between the Winchester/Nashville TN aggregation and the 1950 Stemmons Freeway, Dallas TX backbone facility. PingPlotter screenshots and .pp2 sample sets available on request.

1

apakis

Visitor

 • 

4 Messages


Yeah, I did another tracert on a peer to peer endpoint for a game and this one exits cs02 instead of cs03 with approximately the same latency figures: 170.100.167.239 over a maximum of 30 hops
1     1 ms    <1 ms    <1 ms  10.0.0.1
2    15 ms    13 ms    17 ms  100.92.75.123
3    13 ms    13 ms    17 ms  po-123-rur402.winchester.tn.malt.comcast.net [68.85.54.225]
4    17 ms    17 ms    13 ms  po-400-xar02.winchester.tn.malt.comcast.net [96.108.30.49]
5    16 ms    13 ms    13 ms  68.86.240.1
6    18 ms    17 ms    17 ms  68.86.240.22
7   299 ms   220 ms   180 ms  be-34922-cs02.dallas.tx.ibone.comcast.net [68.86.95.117]
8   231 ms   259 ms   285 ms  be-3211-pe11.1950stemmons.tx.ibone.comcast.net [96.110.34.86]
9     *        *        *     Request timed out.
10   257 ms   283 ms   302 ms  dls-b23-link.ip.twelve99.net [62.115.138.65]
11   298 ms   315 ms   316 ms

I am going to run some more.

(edited)

Like

Reply

2 hours ago

0

user_a1f093

Visitor

 • 

4 Messages

2 hours ago

I am in Memphis Tn. Normally have a 20-30ms ping to nearly anywhere. Today it went up to over 300ms to any server outside of Memphis. 1gb download speeds, 350mb/s uploads. Everything is fine......until I try to go outside the area. Xfinity support is all but useless.

6

forum icon

New to the Community?

Start Here