my minecraft had gone crazy yesterday i played and after a couple hour i come back to the computer the ping is about 850ms and i cant play its on all of the servers and i can only play at the afternoon because just in that time period i can actualy join servers and my internet is good i cant even use steam but not minecraft can someone help me D;
Restart. If your ping is still high, then you either:
Have a bad internet connection but think it's good
Are connecting to a server far away
Having issues with drivers
Something else I can't think of at this moment.
first of all i have a good connection im not stupid about those things
second it doesnt matter how much the server is close to me a fact my friend started a server and i couldnt connect to the server
third that might be the problem so can u explain to me what i need to do
Physical distance is not as relevant as network distance. Fire up a command prompt and type tracert then the address to the server with the high ping (just the IP/domain, no port). Copy the results and post here.
If the problem is a server with the address play.someserver.com:25570 for example, you'd do tracert play.someserver.com. If you have trouble trying to copy/paste from the command prompt, direct the output to a text file. Using the same server address for an example, you'd type tracert play.someserver.com >trace.txt. It will sit there appearing to do nothing for a bit, that's normal. Once done you type can type notepad trace.txt and you'll get the output in Notepad.
Looking at that data will let you see if there is a network hop somewhere causing the problem. This also assumes you are using Windows. If it's linux, just swap tracert for traceroute.
Tracing route to mc.hypixel.net [censured]
over a maximum of 30 hops:
1 <1 ms 1 ms 1 ms smartbox.home [censured]
2 9 ms 7 ms 7 ms ip
3 9 ms 9 ms 9 ms ip
4 8 ms 9 ms 8 ms ip
5 * * * Request timed out.
6 10 ms 10 ms 11 ms ip
7 26 ms 11 ms 10 ms ip
8 11 ms 11 ms 12 ms CORE-1.MRK-gig4-5.bb.012.net.il [ip]
9 69 ms 61 ms 74 ms 80.179.166.142.static.012.net.il [ip]
10 74 ms 77 ms 74 ms ffm-s2-rou-1041.DE.eurorings.net [ip]
11 77 ms 107 ms 76 ms ffm-s6-rou-1041.DE.eurorings.net [ip]
12 79 ms 77 ms 79 ms ffm-s1-rou-1101.DE.eurorings.net [ip]
13 76 ms 76 ms 75 ms xe-1-2-0.mpr1.fra4.de.above.net [ip]
14 170 ms 169 ms 164 ms ae27.cs1.fra9.de.eth.zayo.com [ip]
15 169 ms 170 ms 167 ms ae0.cs1.fra6.de.eth.zayo.com [ip]
16 172 ms 171 ms 164 ms ae2.cs1.ams17.nl.eth.zayo.com [ip]
17 165 ms 165 ms 174 ms ae0.cs1.ams10.nl.eth.zayo.com [ip]
18 165 ms 200 ms 169 ms ae6.cs1.lhr11.uk.eth.zayo.com [ip]
19 167 ms 195 ms 169 ms ae5.cs1.lhr11.uk.eth.zayo.com [ip]
20 166 ms 172 ms 187 ms ae3.cs1.ord2.us.eth.zayo.com [ip]
21 168 ms 163 ms 163 ms ae27.cr1.ord2.us.zip.zayo.com [ip]
22 174 ms 168 ms 168 ms ae0.mpr1.ord6.us.zip.zayo.com [ip]
23 162 ms 165 ms 167 ms ip
24 162 ms 164 ms 162 ms ggw2.c09c10.r15.s101.chi03.singlehop.net [ip]
25 164 ms 164 ms 165 ms ip
Where were these numbers taken from? Is it what your ISP says you pay for, are they taken from your router or are they taken using a network speed test (like speedtest.net)? In the first 2 cases they might not show your actuall speeds. In the third case it means your ping should be ok. Your down;oad speed is really high, but the upload speed seems a bit low compared to download.
About that tracert:
You have a "request timed out" error on one of the nodes. Try running tracert again and see if it is still there. If it is, try running tracert, but instead of server adress use google.com. There might be something wrong with one of the routers between you and the server. Unfortunatelly there is nothing you can do about it.
What did the IP do to make you mad? lol You mean censored, not censured
Nothing in there looks particularly bad. The one timeout isn't really a problem. Timeouts during a trace aren't an issue unless they keep going. Traceroute packets target the control plane and these packets are very low priority, so having a router drop one due to being busy or being configured to do so isn't too surprising.
my minecraft had gone crazy yesterday i played and after a couple hour i come back to the computer the ping is about 850ms and i cant play its on all of the servers and i can only play at the afternoon because just in that time period i can actualy join servers and my internet is good i cant even use steam but not minecraft can someone help me D;
Have your tried restarting the internet?
Listen to C418's album "One"
https://www.youtube.com/watch?v=wYNAZz86DVo&list=PLA3c7DWaVs-G8r1lsYr57G8K16EBWNajR&index=1
first of all i have a good connection im not stupid about those things
second it doesnt matter how much the server is close to me a fact my friend started a server and i couldnt connect to the server
third that might be the problem so can u explain to me what i need to do
restarting your router and yes
I need some information form you:
Once you aswear the questions I might be able to tell you how to fix it.
1. with a wire
2. between 3 to 6 because we have 2 routers
3.as i said between 3 to 6
4.yes
5.download:80.7mb upload:1.927mb
6.no
here you go
Physical distance is not as relevant as network distance. Fire up a command prompt and type tracert then the address to the server with the high ping (just the IP/domain, no port). Copy the results and post here.
If the problem is a server with the address play.someserver.com:25570 for example, you'd do tracert play.someserver.com. If you have trouble trying to copy/paste from the command prompt, direct the output to a text file. Using the same server address for an example, you'd type tracert play.someserver.com >trace.txt. It will sit there appearing to do nothing for a bit, that's normal. Once done you type can type notepad trace.txt and you'll get the output in Notepad.
Looking at that data will let you see if there is a network hop somewhere causing the problem. This also assumes you are using Windows. If it's linux, just swap tracert for traceroute.
Tracing route to mc.hypixel.net [censured]
over a maximum of 30 hops:
1 <1 ms 1 ms 1 ms smartbox.home [censured]
2 9 ms 7 ms 7 ms ip
3 9 ms 9 ms 9 ms ip
4 8 ms 9 ms 8 ms ip
5 * * * Request timed out.
6 10 ms 10 ms 11 ms ip
7 26 ms 11 ms 10 ms ip
8 11 ms 11 ms 12 ms CORE-1.MRK-gig4-5.bb.012.net.il [ip]
9 69 ms 61 ms 74 ms 80.179.166.142.static.012.net.il [ip]
10 74 ms 77 ms 74 ms ffm-s2-rou-1041.DE.eurorings.net [ip]
11 77 ms 107 ms 76 ms ffm-s6-rou-1041.DE.eurorings.net [ip]
12 79 ms 77 ms 79 ms ffm-s1-rou-1101.DE.eurorings.net [ip]
13 76 ms 76 ms 75 ms xe-1-2-0.mpr1.fra4.de.above.net [ip]
14 170 ms 169 ms 164 ms ae27.cs1.fra9.de.eth.zayo.com [ip]
15 169 ms 170 ms 167 ms ae0.cs1.fra6.de.eth.zayo.com [ip]
16 172 ms 171 ms 164 ms ae2.cs1.ams17.nl.eth.zayo.com [ip]
17 165 ms 165 ms 174 ms ae0.cs1.ams10.nl.eth.zayo.com [ip]
18 165 ms 200 ms 169 ms ae6.cs1.lhr11.uk.eth.zayo.com [ip]
19 167 ms 195 ms 169 ms ae5.cs1.lhr11.uk.eth.zayo.com [ip]
20 166 ms 172 ms 187 ms ae3.cs1.ord2.us.eth.zayo.com [ip]
21 168 ms 163 ms 163 ms ae27.cr1.ord2.us.zip.zayo.com [ip]
22 174 ms 168 ms 168 ms ae0.mpr1.ord6.us.zip.zayo.com [ip]
23 162 ms 165 ms 167 ms ip
24 162 ms 164 ms 162 ms ggw2.c09c10.r15.s101.chi03.singlehop.net [ip]
25 164 ms 164 ms 165 ms ip
Trace complete.
where i write ip its an ip like 55.543.54.33
That means we just halved the possible number of issues.
Where were these numbers taken from? Is it what your ISP says you pay for, are they taken from your router or are they taken using a network speed test (like speedtest.net)? In the first 2 cases they might not show your actuall speeds. In the third case it means your ping should be ok. Your down;oad speed is really high, but the upload speed seems a bit low compared to download.
About that tracert:
You have a "request timed out" error on one of the nodes. Try running tracert again and see if it is still there. If it is, try running tracert, but instead of server adress use google.com. There might be something wrong with one of the routers between you and the server. Unfortunatelly there is nothing you can do about it.
from speedtest.net
What did the IP do to make you mad? lol You mean censored, not censured
Nothing in there looks particularly bad. The one timeout isn't really a problem. Timeouts during a trace aren't an issue unless they keep going. Traceroute packets target the control plane and these packets are very low priority, so having a router drop one due to being busy or being configured to do so isn't too surprising.