Weird packet loss or bad lag on my phone
Weird packet loss or bad lag on my phone
I'm doing this now, I have pinged the first four hops, and one is just sending Request timed out messages. The hop that goes straight to my router is working at 100%. The other two hops are on either side of the completely down server and they're answering normally about 90% to 95% of the time without timing out.
I've been testing ping across different hops between me and Google's 8.8.8.8 lately. It looks like the server at 96.34.84.224 is completely offline, but my router still replies to pings perfectly fine. I also checked two other servers: one that comes before this broken one on the list and another that follows it; both of those are working well with about a 98% success rate. Based on where things are located, that unresponsive server is in Ashford, Connecticut. So maybe I'm missing something or should just ask Spectrum for help?
When I don't play that game, those old servers work fine, but if I do start playing, both servers suddenly slow down by ten to twenty percent on every ping.
This happens because pingplotter doesn't work well when you do it on your own without knowing exactly what's happening. Imagine these lights as the roadblocks between you and your job, and there is an app on your phone that shows how long each block takes to cross. Suppose the app says the third light is broken so no cars can pass through it. You drive by and make it to work in time because the traffic isn't actually stuck at the third stop; only the signal system is failing. Now imagine a five-minute delay appears at the third stop, making your total travel time that much longer and causing you to arrive 5 minutes late even though you never really stopped for anything real. Routers sometimes get set up to not answer or to limit how much they reply just in case someone tries to flood them with too many pings to crash their system. This means a hacker could try to ping those routers millions of times every second, and if the router starts answering it would use all its computer power just to say yes instead of letting traffic through. So what you really want to find is a problem that stops one specific point in your route and stops stopping at every single step after that including the very last stop which matters most for your trip. If you see that 1% of packets get lost at the third stop, you will also see at least 1% missing at all those steps after that including the final destination node itself. You might notice some small differences when testing each point because random issues can come and go so you have to keep running these tests for a while until you start spotting a clear pattern. However, it is very important to ignore any data that only shows problems in an intermediate stop but does not actually block your real traffic from going all the way to where you want to end up.