I'm skeptical, but I'll keep my tracer and ping tracker running today.
I'm skeptical, but I'll keep my tracer and ping tracker running today.
Also skeptical. Still got a couple more hours until that 12-hour cycle starts again.
FWIW, in my haste to get *something* working in readiness for 6.4, I signed up for a different ISP, Xfinity, and put my PS5 on that service last night (plus a laptop to run traceroute/ping)
On Xfinity, pings/latency stayed around 70ms and no lag or rubberbanding.
I did a couple traceroutes at the same time, one going out of ATT Fiber and one going out Xfinity but same physical location / house.
They both went through some of the nodes we've been seeing, like going through the Chicago, San Jose and Sacramento NTT nodes and included IPs like 128.241.2.18 and 129.250.4.239 but Xfinity never went through 129.250.7.57.
The ATT connection had 20% packet loss and 120ms pings spiking to 200ms but the Xfinity connection was perfectly fine.
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.

Reply With Quote



