So I think about a year ago my internet worked practically fine and nowadays my internet just randomly spikes from normal to 3k out of nowhere then go back/fourth like a game of Ping Pong and it's annoying me to no end when I try to watch a video or play a video game. What recommendations would you give to try and fix this problem, if it can be fixed of course.
What did you ISP say when you contacted them?
What's your network situation like?
Wifi?
Recently new-ish modem/router?
Updated network drivers?
Not torrenting?
Speedtests?
Have you tested the internet on another device, like a smartphone or just another computer in general? Just to rule out that it's not a problem with 1 computer
You can also set up a program like pingplotter to narrow down whether it's a problem with your network or your ISP. You can set up 2 continuous pings, one to your router and one to something public like 8.8.8.8. Then compare spikes, if the spikes are only to the public address, it's an ISP problem. If it's to both the router and public address, it's an internal networking problem.
My memory might be fuzzy, but when I brought it up to my ISP I think they gave us a new modem.
So are you hard-wired from the PC to the Router/Modem? (Are you ON wifi, has that changed since before?)
Speedtests can depend on the area... but I use:
http://www.speedtest.net/ - as a baseline and "best case"
https://fast.com/ - as a more "real world" test
and then I download Linux ISOs via HTTPs from local mirrors for a real real test.
You can also trying pinging a number of IPs that are anycasted and generally on the "best" route no matter what:
ping 1.1.1.1 -t -l 1024
or
ping 8.8.8.8 -t -l 1024
There's also a chance it's the ISPs fault, and that's always an uphill battle.
I would say that I am hard-wired then and as for speed I got 2.9 Mbps from Fast.com. Plus if I were to use PingPlotted could I just use it on my ISP/a public ping or does it have to be both?
It'll have to be both if you want to figure out if it's a problem with your network in your home or a problem with your ISP.
I gotchu.
Would it be a good idea to check how my ping is during the event of it skyrocketing?
using -t just makes it sit there until you ctrl+c to end it, lets you passively monitor it until it starts spiking or dropping.
If you just do that it makes it a lot harder to visualize comparisons for the two imo
So I ran PingPlotter for a while and not much happened other than a few mild ping spikes. Think I should've done it when the worst spikes happened?
So I ran a test with both my IP's ping and the 1.1.1.1 -t -l 1024 anycast's ping when everything was normal and I noticed that the latter was getting more of a bit of higher ping at rare times and even had more packet losses than my latency, which had none at the time. What would that mean?
Sounds like what's happening is you're getting intermittent packet loss and latency spikes, causing those horrible (3k+ pings, if you lose a lot of packets) problems.
I'd recommend running pings down the whole traceroute stack, so then you can isolate where the issues are coming from.
run tracert 1.1.1.1
https://s.gvid.me/s/2018/09/06/h4q871.png
You'll get results that look somewhat like that.
You'll want to run ping commands against key points in the route:
Ping the first hop (192.168.1.1)
Ping the next hop that has the larger jump in latency (so 96.120.96.161 in this case)
And then ping the end point, all in separate CMD windows with -t
Once you start getting lag, watch the CMD windows to see what destinations start getting higher latency.
If it's between you and the first hop, it's a local network issue. If it's between the first hop and the first high latency hop, it's (probably) the last-mile infra. If it's between the first high latency hop, it's probably their peering/backbone.
Pray it's the first or last one, you can do something about the first one, and somebody is probably going to do something about the last one.
I've never done this kind of stuff before so this looks like it'd be difficult to do. Sorry if it sounds like I am trying to back out. Though how do I start up the pings to check them out in CMD?
It's fine, networking sucks, it's the sewer maintenance, of computers.
Just open multiple CMD windows (win+r, CMD) then type the different ping commands, you'll want to append -t -l 1024 to all of them.
-t makes the ping continue until you stop it (using ctrl+c), so you can let them run until the lag starts up and then stop and assess.
-l 1024 sets the ping packet size to 1024 byes, which is a bit more realistic for what would happen to TCP/UDP packets.
Networking is the best part of computers, watch your whore mouth.
Every CCNP+ person I've ever met IRL either has an alcohol problem, or sounds like they want to develop one.
This even includes someone who was a core programmer for IOS, that shit turned him crazy.
Yeah that's a fair assessment.
So just to make sure I'm doing it correctly I open up CMD windows and append both my IP and 1.1.1.1 -t -l 1024?
Just do
ping (IP you want to ping) -t -l 1024
So I ran the test with my local IP and the 1.1.1.1 anycast server and after a while when I came back to it the later had 11 packet losses while mine experienced none.
Sorry, you need to Log In to post a reply to this thread.
