Slowness in tracert to public IP address
We have a basic server configured with Centos7 to which we installed MSSQL Server and it is working well, but it presents a delay in the response to registries and processes far superior to those we have in a similar server hosted in another hosting.
When doing a tracert to the public IP address of this server and compare it with one done on the other, we see that the droplet in Digital Ocean responds up to 5 times slower, because of many jumps in the access network … Is this delay due? Do we have any way to configure a direct ip address to the droplet without so many jumps? we do not find in the configuration options something to do it
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.×