Visitor

 • 

1 Message

Monday, July 27th, 2026 9:11 PM

Terrible latency after Xfinity maintenence on 07/22

I'm hoping someone from Xfinity can help get this escalated because this appears to be a routing issue rather than a problem with my equipment.

Recently, my latency to servers in Dallas, Chicago, and other central/eastern locations suddenly increased by roughly 20–30ms. Dallas used to be around 30–40ms and is now consistently around 60ms. Chicago used to be around 60ms and is now around 80–90ms.

I first noticed this while playing CS2, but I've since confirmed it isn't specific to CS2 or one server provider. I'm seeing the same increase on Valve servers, FACEIT servers, and independent community servers. I believe this started around the time Xfinity performed maintenance in my area last week on 07/22.

I've done quite a bit of testing to rule out my home network. I'm on Ethernet, latency to my router is <1ms, and I'm seeing 0% packet loss. Ping to 1.1.1.1 averages 23ms and 8.8.8.8 averages 22ms. Xfinity's local Pima/Tucson hops are also consistently around 10–15ms.

Things get strange when the routing is outside Tucson. For example, a Dallas server at 23.156.136.146 averages about 62ms. The traceroute goes from Xfinity's Pima County network west to the Los Angeles Comcast backbone, gets handed to Cogent in LA, and then travels back east through Phoenix, El Paso, and finally Dallas:

Pima/Tucson → Comcast Los Angeles → Cogent Los Angeles → Phoenix → El Paso → Dallas

I tested two unrelated Chicago endpoints as well. 173.45.132.16 averages 71ms and 66.225.198.198 averages 77ms, both with 0% packet loss. Both routes also go through Comcast's Los Angeles backbone before heading toward Chicago.

Even a Hurricane Electric endpoint in Phoenix (184.105.81.173) averages about 33ms and takes:

Tucson → Comcast Los Angeles → HE Los Angeles → Phoenix

I'm not claiming that going through LA is inherently a routing error, but the sudden latency increase to multiple unrelated networks at roughly the same time makes me think something changed with Comcast's backbone routing or peering. My local connection and latency to nearby/western services are otherwise normal.

Is there any way someone can look into this or escalate it to the appropriate network/routing team? Anyone who plays competitive games seriously knows just how unplayable the game becomes at high ping. I'm happy to provide the full traceroutes and additional testing if needed. Rebooting the modem/router has already been done and made no difference.

Oldest First
Selected Oldest First
No Responses!
forum icon

New to the Community?

Start Here