JWP Posted July 3, 2019 Report Posted July 3, 2019 I can't imagine why... Other than I can't even complete a trace route to the server IP address. unless 147.135.8.195 isn't the IP... Probably won't be on Wednesday night. See you all Thursday... If I can connect.
Staff Death Posted July 3, 2019 Staff Report Posted July 3, 2019 Pinging the IP/hostname will always timeout due to firewall implementations. You'll need to do a TCP route with the the access point (28015) for US pure. Your trace route looks good, latency is normal. I'm sure you know, but Windows does not have a native library for TCP tracing so you'd need to download something like wincap.
JWP Posted July 3, 2019 Author Report Posted July 3, 2019 I mean it was so bad, after I minute I couldn't play as I had about a 30 second delay between requesting an action ex: opening a door, and the action completing. After about a minute of play time nothing worked. Running it through: sudo traceroute -T -p 28015 147.135.8.135 on my Linux machine gets timeouts starting at step 9. Last connection be7.was1-vin1-vac-a75.wa.us 198.27.73.167 at 152.666 ms But that's today. Yesterday PC and Linux we're about the same results.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now