Tracert issue after switching VPS location Dallas > LA

[Sil3nt]

Ping 64.94.100.205
[v-64-94-100-205.unman-vds.internap-la.nfoservers.com]
Round trip time to 64.94.100.205: 609 ms
Round trip time to 64.94.100.205: 30 ms
Round trip time to 64.94.100.205: 30 ms
Round trip time to 64.94.100.205: 30 ms
Round trip time to 64.94.100.205: 30 ms
Round trip time to 64.94.100.205: 30 ms
Round trip time to 64.94.100.205: 30 ms
Round trip time to 64.94.100.205: 30 ms
Round trip time to 64.94.100.205: 30 ms
Round trip time to 64.94.100.205: 30 ms

I have correctly changed IPv4 properties and disabled Windows Firewall as suggested by Support but still having problems. OS: WinServer2012 R2

[Edge100x]

Did you mean to post a trace? What is the issue that you are seeing?

[Sil3nt]

Did you mean to post a trace? What is the issue that you are seeing?

[Edge100x]

From what you posted, you're likely pinging/tracing something that hasn't been contacted recently, and the ARP entry had timed out. When an ARP entry times out (which is after about 30 seconds), the router has to take a little extra time re-establishing it, causing the first ping response to be elevated. This would not represent a problem with the service.

If you're seeing a further problem with latency when actually using the service, please don't hesitate to contact us directly.

Both LA and Dallas have been performing without problems that I have seen.