akylen wrote: ↑11 Nov 2025, 19:47
ManWhoSoldTheWorld wrote: ↑12 Oct 2025, 12:45
Unreazz wrote: ↑11 Oct 2025, 13:38
If you can't hit shiet then probably it is yeah. but you are doomed anyways if its ISP since there is not much what you can do...
Moving in to a new flat, in two weeks, where the Internet access is delivered from my own company - Let the debugging begin!
Updates ?
Hi! Yes

After connecting the new access router in the newly built flat, the Internet Exchange is now just one hop away. I’ve got very effective routing toward the global IP Transit and associated networks. However, RTTs have doubled to Frankfurt and are 60–80% higher to Amsterdam and London. It turns out that some of my traffic isn’t going through the IP Transit but instead takes direct peering paths — which, while intended for more efficient routing, actually performed worse in this case.
The company I work for owns all the network infrastructure (Access, Metro, and Core), so I’ve been able to debug it quite thoroughly. It seems we have some buffering on the border nodes handling direct peering. Long story short → we’re upgrading those border nodes, and I’ve optimized the peering routes toward all Faceit CS2 servers in Europe.
With default Windows settings, I get a bufferbloat grade of “A.” By lowering the PCIe NIC RX and TX buffers, it improves to A+. I can comfortably hold angles in CS2 when connected via the IP Transit path, but when traffic goes through the direct peering route, it’s unplayable. Hopefully the ongoing remediation steps will fix that.
Aside from the network side, I’ve also noticed some odd behavior in the render pipeline. It seems like Windows performs a link training during boot that ignores my monitor’s custom timings — easily fixed by restarting the driver, but still strange. It’s a new and exciting experience every time I boot the computer.