Visitor
•
9 Messages
High Latency/Congestion at Dallas ibone node (be-34932-cs03.dallas.tx.ibone.comcast.net)
EDIT (11:00 PM CDT): Now confirmed across all four Dallas core switches: cs01 (68.86.95.113), cs02 (.117), cs03 (.121), cs04 (.125), with pe11 interfaces 96.110.34.82/.86/.90/.94. Four reporting customers on different rur interfaces (68.85.54.221, 68.85.54.225, 162.151.131.237, 68.86.246.25) and two different xar02 port-channels (96.108.29.54, 96.108.30.49). The only hops common to every affected trace are 68.86.240.1 and 68.86.240.22, both responding normally at 12–17ms.
Since all four ECMP members are degraded identically, this is not a device fault. Requesting review of the transport egressing 68.86.240.22 toward the 1950 Stemmons Dallas facility, and any change made August 2-August 3.
Hi!
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.
user_ukllvk
Visitor
•
2 Messages
10 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.1complete in 16ms via162.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 web192.178.152.139(335ms), Linode Dallas50.116.25.154(282ms), Linode Newark50.116.57.237(279ms), OpenDNS208.67.222.222(288ms), ICANN root server199.7.83.42(266ms).Common failure point: Every affected trace is normal through
68.86.240.22, then enterscs03.dallas.tx.ibone.comcast.netand jumps immediately. Example from the199.7.83.42trace — hop 768.86.240.22at 10ms, hop 868.86.95.121at 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
user_a1f093
Visitor
•
4 Messages
9 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.
10
user_ukllvk
Visitor
•
2 Messages
7 hours ago
Issue Resolved around 11:05pm CST.
2
0
apakis
Visitor
•
9 Messages
6 hours ago
Well, it looks to be holding now. I’ll knock on wood though. If a representative is able to post to say whether or not we were on the right track just for my own curiosity’s sake, I would appreciate it, but if not, all good.
0
0