Visitor

 • 

1 Message

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. 

Oldest First
Selected Oldest First
No Responses!
forum icon

New to the Community?

Start Here