Internet acting very odd!!!

Blt1684

Honorable
Jul 10, 2013
37
0
10,530
Okay, so first of all i have 100Mbps speed internet and I run hard wired. I have never really had any issue with it expect during the regular maintenance or something like that, overall very reliable. For the past week i have been noticing very erratic ping spikes just general lag when playing Blade and Soul, which i normally have no issue with and get about 35-45 ping. So today I decided to do a speed test with speedtest.net. All results were same: bouncing between 4-16Mbps. So i called and set up an appointment for a tech to come out, now i have to wait 5 days. But, i thought I might just try switching to another modem. So i unplugged my modem and then realized i no longer have another modem to switch out. So after reinstalling the modem i just uninstalled, i decided to look at speedtest.net again only to find out that the speed was back to 100Mbps on the dot. Whats odd is I unplugged my modems power cable for 30-45 sec several times with no avail, until just now when i had the coaxial cable unplugged as well. So i went back to playing Blade and Soul, and checked again a couple minutes later and it was still fine. Then again i noticed lag and ping spikes, so i checked again a few minutes after the last check to find that it was back to 4Mbps. I'm hoping this is an issue with my modem and i can just replace it but im not sure. I'm pretty sure its not with my ISP because when i call and put in my number, it will tell me if there is an outage or maintenance in my area and since i did get my speed back to normal for a few minutes. I know this is a large explanation but I hope someone can help me understand this better.
 
Solution
Basically I wanted to see if packets were being dropped between your computer and modem/router or from your network to the outside. I'm assuming you already know the IP Address to your modem since you got posted the information, but if not, to find out the IP address of your modem if you are directly connected to it, just do "ipconfig /all" in command prompt and it will be after Default Gateway. Try pinging that using my original post, along with pinging 8.8.8.8 (Google DNS server). Make sure to us "ping 8.8.8.8 -t" because the -t means it won't end until you cancel it yourself using CTRL+C.

Once you start getting lag, look at the ping windows and see if anything is irregular. Usually it will be high time values or Unresponsive...
Do the following, open up 2 command prompt windows. In one, type the following without quotes "ping 8.8.8.8 -t" and in the other type "ping 192.168.1.1 -t" assuming that 192.168.1.1 is your router. After a few minutes of using the internet and if you noticed the lag come up, press CTRL+C. Report back the statistics.
 
Status Code: Operational
Software Version: STAC.02.50
Software Model: a81a
Bootloader: 2.3.1

Cable Signal Details
Forward Path:
Channel Frequency Power SNR BER Modulation
1 165.0 MHz 4.4 dBmV 41.3 dB 0.225 % 256 QAM
2 111.0 MHz 4.1 dBmV 41.3 dB 0.982 % 256 QAM
3 117.0 MHz 4.5 dBmV 41.9 dB 0.409 % 256 QAM
4 123.0 MHz 4.5 dBmV 41.3 dB 0.367 % 256 QAM
5 129.0 MHz 4.4 dBmV 41.8 dB 0.274 % 256 QAM
6 147.0 MHz 3.8 dBmV 40.3 dB 0.265 % 256 QAM
7 153.0 MHz 4.7 dBmV 41.5 dB 0.024 % 256 QAM
8 159.0 MHz 3.6 dBmV 40.7 dB 0.035 % 256 QAM
Return Path:
Channel ID Frequency Power Modulation
4 34.5 MHz 53.0 dBmV 16 QAM
5 28.0 MHz 52.0 dBmV 16 QAM
0 0.0 MHz 0.0 dBmV QPSK
0 0.0 MHz 0.0 dBmV QPSK
Data Service Details
Provisioned Address: Yes
Provisioned Time: Yes
Provisioned Configuration: Yes
Registered: Yes
BPI: Disabled


Event Log:
Time Priority Description
Sun Apr 03 08:14:35 2016 Warning (5) MDD message timeout;CM-MAC=c4:27:95:0a:99:7b;CMTS-MAC=68:ef:b...
Sun Apr 03 08:12:35 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Apr 03 08:05:06 2016 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Sun Apr 03 07:42:07 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Apr 03 07:35:06 2016 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Sun Apr 03 07:28:53 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Apr 03 07:05:06 2016 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Sun Apr 03 06:59:44 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Apr 03 06:35:06 2016 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Sun Apr 03 06:26:39 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Apr 03 06:05:06 2016 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Sun Apr 03 06:02:48 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Apr 03 05:35:06 2016 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Sun Apr 03 05:31:40 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Apr 03 05:05:06 2016 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Sun Apr 03 04:34:43 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Apr 03 04:05:06 2016 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Sun Apr 03 04:03:37 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Apr 03 03:35:06 2016 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Sun Apr 03 03:17:15 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Apr 03 03:05:06 2016 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Sun Apr 03 03:02:41 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Apr 03 02:35:06 2016 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Sun Apr 03 02:31:33 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Apr 03 02:05:06 2016 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Sun Apr 03 01:53:09 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Apr 03 01:35:06 2016 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Sun Apr 03 00:47:36 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Apr 03 00:39:05 2016 Warning (5) MDD message timeout;CM-MAC=c4:27:95:0a:99:7b;CMTS-MAC=68:ef:b...
Sun Apr 03 00:37:40 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Apr 03 00:35:06 2016 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Sun Apr 03 00:29:04 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received
 
Basically I wanted to see if packets were being dropped between your computer and modem/router or from your network to the outside. I'm assuming you already know the IP Address to your modem since you got posted the information, but if not, to find out the IP address of your modem if you are directly connected to it, just do "ipconfig /all" in command prompt and it will be after Default Gateway. Try pinging that using my original post, along with pinging 8.8.8.8 (Google DNS server). Make sure to us "ping 8.8.8.8 -t" because the -t means it won't end until you cancel it yourself using CTRL+C.

Once you start getting lag, look at the ping windows and see if anything is irregular. Usually it will be high time values or Unresponsive requests. After a minute, just press CTRL+C in both windows and look for the Packet loss. If you see packet loss to 8.8.8.8 but not to your modem's IP, that means there most likely is something wrong with the connection between your modem and the outside. It could mean something is wrong with your modem, but more often than not, it's the outside connection. If you are getting the exact same packet loss between both IP addresses, then there is something wrong with the connection between your computer and the modem or something wrong with your modem.

All the values at the top of your last post look healthy with the possible exception of the BER. The BER should be as close to 0% as possible, and one of your values is almost 1%.
 
Solution

TRENDING THREADS