#High latency on route to portland datacenter
1 messages · Page 1 of 1 (latest)
Same, multiple ISP's used same result. wiped shadow and reset. no changed
Post here ping plotter results, both directions, Shadow <-> your local device.
Maybe somebody will be able to read and understand those.
Appears to be going via London 🤷♂️ What about Shadow > Local ?
Righto. The massive increase this time is a AT&T hop (17) but loads of timeouts in between. Best be would be to send to Shadow. See if anything they can do.
any updates Aireze?
Also there's a small amount of packet loss on your local router that can lead to your stream freezing.
slow and steady back and forth with shadow support nothing has changed yet for me.
right im ok with some frames here and there. but going from 30-35ms to 170-180 ms is killing me
im in CA on ATT and i had problems with por data center before, I changed my supscription to the texas servers and it fixed it last time!
whats your ISP Brotha?
How can I switch my data center? I’m having the same problem
sadly you need to cancel your account and start a new account but start out your application that your in texas.
or maybe email tech support
emailed shadow pc about this issue and this is my recieved respponse:
Thank you for your message!
Unfortunately, it is impossible to migrate your Shadow POWER+ account to our Dallas data centre. Currently Shadow POWER is not available in our Dallas data centre.
You could be experiencing these issues because we had to move your Shadow PC to a new Data Center since Shadow Power wasn't available in your Data Center.
Thank you for your understanding and please let us know if you have any other questions .
Best,
new info. ran through PRIVADO-VPN and got a 33ms lattency
@rugged patrol did this ever work out for you? I'm experiencing the same thing. in CA with att fiber.
yes i used privado vpn on my pc and ipad. fixed lattency to 30ms on both platforms
had this same problem last year. it was to do with att routing
I’m having the same issue—so you launched privado-vpn on your local and that fixed it? Set to any place in particular?