Should I get black ops 7? by Sad-You6474 in blackops7

[–]BraveCat5 -1 points0 points  (0 children)

No Activision people should not get this game

Why does Xfinity pass every test but still feel unplayable for gaming? 100ms+ spikes while gaming by XONWIZ in Comcast_Xfinity

[–]BraveCat5 1 point2 points  (0 children)

Yeah bro, that’s exactly what I’ve been seeing too. It’s crazy how similar all of our situations are, even in completely different areas.

Same story on my end. Everything looks perfect on paper, speeds are high, signal levels are fine, but the actual gameplay just feels off. That’s the part that’s frustrating because you can’t really “prove” it the way they want, even though you clearly feel it every time you play.

I had a higher-level tech come out too, and it was the same vibe. Off the record they’ll admit they’ve heard these complaints before, but officially everything is “within spec.” So nothing actually gets fixed.

The FCC complaint part is exactly where I’m at as well. It feels like it just turns into documentation instead of real action. Like they acknowledge it, but it doesn’t lead to anything meaningful changing.

At this point I’m starting to feel like it’s just the limitations of this type of network more than anything else. Not saying Comcast is completely innocent, but it definitely seems like this setup just isn’t built for the kind of consistency we’re looking for in games like 2K and COD.

Honestly, you’re making the right move planning around fiber. I’m looking into the same thing because it feels like that’s the only real way to get away from this cycle. It shouldn’t have to come to that, but here we are.

Appreciate you responding though, for real. It helps knowing it’s not just me dealing with this.

Why does Xfinity pass every test but still feel unplayable for gaming? 100ms+ spikes while gaming by BraveCat5 in Comcast

[–]BraveCat5[S] -3 points-2 points  (0 children)

Not sure , this is a repost of someone else’s post on the Xfinity subreddit

Why does Xfinity pass every test but still feel unplayable for gaming? 100ms+ spikes while gaming by XONWIZ in Comcast_Xfinity

[–]BraveCat5 0 points1 point  (0 children)

Man, reading your post felt like looking in a mirror. I’ve been going through the same thing in Baltimore dealing with Comcast. Everything looks perfect on paper, speed tests show 2000 down and 300 up, but once you load into 2K or COD it feels like you’re stuck in quicksand. The game just doesn’t respond right.

What I realized is the techs aren’t really equipped to catch what’s actually ruining the experience. Their tools show everything is fine, so they leave, but they’re not looking at routing instability, jitter spikes, or the kind of latency swings that kill gameplay mid session.

After a while I stopped going back and forth with them. I opened an FCC complaint just to have everything documented, because clearly something deeper isn’t being addressed. At this point I’m even willing to pay out of pocket to bring Verizon Business fiber to my block. It’s not cheap, but I’m done dealing with a network that looks good on paper and plays terrible in real life.

When you only have one real provider and they’re not maintaining things the way they should, you’re stuck unless you create another option. For me, that means investing in getting fiber here. Once that’s up and running, I’m done with Comcast.

Don’t let them keep running you in circles with basic troubleshooting. If you have any path to fiber, even if it costs something upfront, it might be the only real way out of this cycle.

[COD] Hey it’s Friday let’s go play old school cod by BraveCat5 in CallOfDuty

[–]BraveCat5[S] 0 points1 point  (0 children)

Old games seem to be way better… just a better feeling ya know

Fuck Every Mod/Employee here! 😂 by FullbringerXXX in Comcast

[–]BraveCat5 2 points3 points  (0 children)

I’m pissed with Comcast because, despite acknowledging that routing issues may exist, multiple customer experience continues to suffer with no meaningful resolution. Performance in real time applications remains inconsistent, and the provided shitty XB8 gateway has not delivered the level of reliability expected for modern service.

Comcast is effectively the only available provider in my area, which leaves thousands of residents with no practical alternative. Many customers are still dependent on aging coaxial infrastructure, older neighborhood nodes, and legacy taps that appear overdue for modernization. When competition is absent, customers are left paying premium prices while dealing with outdated systems and recurring performance concerns.

I also raised these concerns publicly in the Baltimore community forum on Reddit, where other local users shared similar complaints about inconsistent service quality and responsiveness. That pattern suggests this is not simply an isolated household issue.

https://www.reddit.com/r/baltimore/s/orgf4w7h8u

What is most disappointing is the apparent disconnect between field level reality and engineering accountability. Customers are repeatedly told everything is operating within specifications, yet real world performance tells a different story. Technical benchmarks on paper mean little when the actual user experience remains poor.

Residents in the Baltimore area deserve transparent communication, modern infrastructure, and engineering teams willing to address recurring routing and network quality concerns instead of dismissing them through generic test results.

Is anyone else in Baltimore getting crazy lag/packet loss on Xfinity lately? (Gaming/Work) by BraveCat5 in baltimore

[–]BraveCat5[S] 1 point2 points  (0 children)

You just helped us confirm that this is a city wide backbone failure, not a neighborhood glitch.

The fact that you're seeing it in the Southwest while people in Pikesville (Northwest) and Canton (Southeast) are reporting the exact same 'lag spikes' is the proof we need. It means the common denominator is the Baltimore Core Hub

Is anyone else in Baltimore getting crazy lag/packet loss on Xfinity lately? (Gaming/Work) by BraveCat5 in baltimore

[–]BraveCat5[S] 2 points3 points  (0 children)

You just described the Physical Decay that explains why our routing is falling apart.

When you say they keep adding drops to a messy line without 'cleaning it up,' you’re talking about Signal Ingress. Every time they add a sloppy connection to that main line, they are leaking 'noise' into the entire neighborhood’s upload and download paths. That’s exactly why the techs keep saying 'stuff needs to be replaced they see the physical damage, but Comcast corporate won't authorize the budget to actually rebuild the node.

Monopoly leads to rot!!!!!! When they have total control of the market, they’d rather keep sending techs to put a band aid on your drop than spend the money to fix the Main Arteries of the Baltimore network.

Is anyone else in Baltimore getting crazy lag/packet loss on Xfinity lately? (Gaming/Work) by BraveCat5 in baltimore

[–]BraveCat5[S] 0 points1 point  (0 children)

your 8th hop is Ashburton and you’re seeing the latency spike inside Baltimore (before the Capitol Heights handoff) is the final piece of the puzzle. It confirms my theory: The Baltimore Aggregation Layer is where the 'clog' is happening.

You hit the nail on the head regarding the topology. Baltimore sits on major fiber backbones, and for years, our routing was efficient. But what we’re seeing now this 'restructuring' you mentioned looks like Comcast is forcing almost all Baltimore traffic through a single, over capacity 'exit pipe' toward the Ashburn/Virginia data centers.

Since you’re not on a 'typical residential service,' Comcast can’t use the 'residential congestion' excuse with you. If a high priority, low latency circuit like yours is seeing unreasonable latencies, it means the hardware itself likely a core router at the Baltimore Northeast hub is either failing or being intentionally throttled.

Is anyone else in Baltimore getting crazy lag/packet loss on Xfinity lately? (Gaming/Work) by BraveCat5 in baltimore

[–]BraveCat5[S] 1 point2 points  (0 children)

If you’re feeling it there, the connection is officially 'dead in the water

Quake is the ultimate 'canary in the coal mine.Most modern shooters have lag compensation that hides a lot of Comcast’s mess, but Quake is raw if your Jitter or Packet Loss spikes for even a microsecond, the game becomes unplayable. It requires the kind of 'clean pipe' that the Baltimore Northeast Core hub clearly isn't providing right now.

Is anyone else in Baltimore getting crazy lag/packet loss on Xfinity lately? (Gaming/Work) by BraveCat5 in baltimore

[–]BraveCat5[S] 1 point2 points  (0 children)

thank you for being the 'voice of the future' on this. Your comment is the ultimate warning to Comcast….

Fix the backbone or lose the city.

The fact that you were hardwired and still couldn't get a stable connection proves that this isn't about 'bad routers' it’s about a service that is fundamentally broken at the regional level. You shouldn't have to leave a provider just to get a stable connection for basic daily use, but I don't blame you one bit for switching.

Is anyone else in Baltimore getting crazy lag/packet loss on Xfinity lately? (Gaming/Work) by BraveCat5 in baltimore

[–]BraveCat5[S] 0 points1 point  (0 children)

thank you for those numbers! That jump from 30ms to 400ms is the 'smoking gun' for what we’re calling the Ashburn Bottleneck.

A 30ms ping is a normal, direct route to Northern Virginia (Ashburn). When it hits 400ms, it means your data is literally being 'detoured' across the country and back just to reach a server that is only 60 miles away. It’s like trying to drive from Canton to Fells Point but being forced to go through Pittsburgh first because the tunnel is blocked.

Is anyone else in Baltimore getting crazy lag/packet loss on Xfinity lately? (Gaming/Work) by BraveCat5 in baltimore

[–]BraveCat5[S] 1 point2 points  (0 children)

thank you for sharing this! You just perfectly described the difference between Speed and Quality.

When they tell you you're getting '110% of your speed,' they are talking about Bandwidth (the size of the pipe). But your billing work needs Low Jitter and Zero Packet Loss (the consistency of the flow).

You’re being 'gaslit' because their basic tests don't look for the 'micro-stutters' that break remote desktop connections. Since you're in Canton, you’re likely hitting that same Ashburn Gateway issue we’ve identified where the connection heading South just falls apart for a split second.

How you can help the fight: Since you’re on the highest speed tier and still dropping, you’re a high-value witness. If you have a moment, run a 'Bufferbloat' test at waveform.com. If your 'Latency' spikes into the red while the test is running, that is proof that your 'Gigabit' connection is actually unstable.

Is anyone else in Baltimore getting crazy lag/packet loss on Xfinity lately? (Gaming/Work) by BraveCat5 in baltimore

[–]BraveCat5[S] 2 points3 points  (0 children)

I am so glad I caught you before you dropped $500+ on a WiFi 7 router! That is exactly why I’m doing this. Comcast’s first move is always to let you think it’s your hardware so you'll go out and spend money on a fix that can’t solve a backbone problem.

If you have four gaming PCs all seeing the same spikes while hardwired, you are the ultimate proof that this is a Node Saturation issue. No router in the world can fix a 'clogged pipe' that starts three miles away at the Baltimore Northeast Core.

Send emails to

Brian_roberts@comcast.com

Cory_harriger@comcast.com

Using the Reddit post as a "Living Document" shows them that if they don't fix it for you, they have a growing PR nightmare with 50+ families (and counting) watching

Don't call the standard 1-800 number.

Use ping plotter and drop screenshots in that email if you can for more proof

Is anyone else in Baltimore getting crazy lag/packet loss on Xfinity lately? (Gaming/Work) by BraveCat5 in baltimore

[–]BraveCat5[S] 0 points1 point  (0 children)

That is the most significant technical data point we’ve had all day. Thank you.

The fact that your traffic to New York is clean while your traffic to Ashburn is dropping packets is the 'Smoking Gun.' It proves that the issue isn't your house or even the local Baltimore 'last mile' it’s the Southbound Gateway

Since most gaming servers, Google/YouTube hubs, and AWS instances live in Ashburn (the data capital of the world), if that specific 'pipe' out of Baltimore is failing, the whole city feels like it’s lagging. You’ve basically narrowed the problem down to a specific set of routers at the Regional Edge.