Minecraft - Connecting to my server takes a long time

Hi @18odegardl,

This can be related to two things I suppose, either your network configuration or your Droplet experience high load thus the Droplet having a hard time loading up resources.

I’ll recommend you to enter your Droplet, use htop and see what happens when you try to connect. If you see some drastic changes in CPU utilization, RAM usage and so on then maybe you might need to look into upgrading the Droplet.

The other problem mentioned may be a network one. In this case maybe it’s best to contact DigitalOcean support to see if they have any suggestions on that.

Hello, @18odegardl

To add more on this.

Could you please let me know if you were able to replicate the issue when testing from different ISPs?

What you can do is to perform a traceroute to your server and see if there is a packet loss on some of the hops, as this will help you to determinate if there is a networking issue. Keep in mind that a lot of ISPs will block ICMP requests and those are used from traceoute so if there is packet loss this doesn’t mean that there is a “real” issue as the requests made by your traceroute command can be blocked intentionally.

I’ve performed a mtr (my traceroute) for a short period of time and I can see that there is a packet loss on this IP - 129.250.6.203 which seems to be associated with NTT America INC, You can see the copy of my traceroute:

 3. 83.217.227.49                                                                                                                                            0.0%   390    6.6   5.1   3.0  11.2   1.2
    
 4. ae-3.r24.frnkge08.de.bb.gin.ntt.net                                                                                                                                  0.0%   390   30.1  29.7  26.9  57.2   2.5
 5. ae-3.r24.frnkge08.de.bb.gin.ntt.net                                                                                                                                 74.1%   390   29.5  51.1  27.4 166.6  37.9
    ae-11.r21.nwrknj03.us.bb.gin.ntt.net
 6. ae-11.r01.nycmny17.us.bb.gin.ntt.net                                                                                                                                 0.0%   390  120.9 120.5 118.1 125.2   1.1
 7. ce-0-13-0-2.r01.nycmny17.us.ce.gin.ntt.net                                                                                                                           0.0%   390  120.0 121.0 118.3 157.5   3.7
 8. ???
 9. ???
10. ???
11. 157.230.202.26                                                                                                                                                       0.0%   389  129.3 128.7 126.5 140.6   1.2

You can check if your traffic goes through this IP address as well and check for any packet loss.

Let me know how it goes.