cancel
Showing results for 
Search instead for 
Did you mean: 

Suffering Packet loss

pandemic
I've Been Around

Hello, I have contacted tech support a few times and techs have come out to check my cables. The techs say that the signal strength is good and I do receive the advertised speeds 100/10, but I suffer packet loss. I also get dropped from Skype calls at the same times I am lagging on League.... I am not sure what the issue maybe, any advice?

 

Stats from the modem, it is in gateway mode and I am on a desktop connect through ethernet.
 
Ping statistics for 104.160.131.1:
Packets: Sent = 1000, Received = 870, Lost = 130 (13% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 146ms, Average = 31ms
 
Downstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB)
1 651000000 256QAM -8.700 10 37.356
2 591000000 256QAM -6.100 1 38.605
3 597000000 256QAM -7.000 2 38.605
4 603000000 256QAM -6.400 3 38.983
5 609000000 256QAM -6.800 4 38.605
6 615000000 256QAM -6.900 5 38.983
7 621000000 256QAM -7.400 6 38.605
8 633000000 256QAM -8.200 7 37.636
9 639000000 256QAM -7.600 8 37.636
10 645000000 256QAM -8.900 9 37.636
11 657000000 256QAM -9.300 11 37.356
12 663000000 256QAM -9.400 12 37.356
13 669000000 256QAM -9.400 13 35.084
14 675000000 256QAM -9.400 14 36.387
15 681000000 256QAM -9.600 15 37.356
16 687000000 256QAM -9.800 16 36.610
17 693000000 256QAM -9.800 17 36.610
18 699000000 256QAM -10.900 18 36.387
19 705000000 256QAM -10.200 19 36.610
20 711000000 256QAM -10.600 20 36.610
Upstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID BandWidth
1 23700000 ATDMA - 64QAM 40.250 7 6400000
2 30596000 ATDMA - 64QAM 40.250 6 6400000
3 38596000 ATDMA - 64QAM 40.250 5 3200000
201 REPLIES 201

Re: Suffering Packet loss

c2q
I Plan to Stick Around

1. Pingplotter is being done via Ethernet, over a powerline adapter. However it's just as bad over Wifi. I have a pretty good router (RT-AC66U). Results are the same even directly connected to the modem.

 

I'm not really sure why Pingplotter is showing packetloss to the router, when I ping the router it's not showing anything. Comparison image below

8.png

 

Also the packetloss is happening again this morning. It seems to go away/reduce significantly after around 3-4pm like yesterday and last week. This is basically a regular occurance at this point.

 

This is a 6 hour graph of what it looked like yesterday:

9.png

 

 

And here's a 6 hour graph at the time I'm posting this (Sunday afternoon)

10.png

 

So as you can see, it starts around 11am or later and usually stops around 4pm or later. I don't know if  this happens on weekdays since I'm not home during these times.

 

 

Re: Suffering Packet loss

AHxCode
I Plan to Stick Around

I am really tired of this to start things off

 

So ever since construction was being done very close to me on underground wires I have had terrible Wired/Wireless Connection issues with my internet (could just be a coincidence). I disconnect from any game on any computer i own all the time, and web pages often take ages to load. I have swapped coax cables, extended them, used a asus router along side, factory reset countless times, force update interval on ddns is 1 week, firewall typical, time setting is correct. I dont know what esle to do but to look else where that i have in mind if this isnt resolved real soon.

 

22.PNG

 22.PNG

 

Downstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB)
1 693000000 256QAM 7.800 23 40.366
2 561000000 256QAM 10.700 2 40.946
3 567000000 256QAM 10.800 3 40.946
4 573000000 256QAM 11.300 4 40.946
5 579000000 256QAM 10.900 5 40.946
6 585000000 256QAM 11.100 6 40.946
7 591000000 256QAM 11.000 7 40.946
8 597000000 256QAM 10.400 8 40.946
9 603000000 256QAM 10.200 9 40.946
10 609000000 256QAM 10.400 10 40.946
11 615000000 256QAM 10.800 11 40.946
12 621000000 256QAM 10.700 12 40.946
13 633000000 256QAM 10.200 13 40.366
14 639000000 256QAM 9.600 14 40.366
15 645000000 256QAM 10.000 15 40.946
16 651000000 256QAM 11.300 16 40.366
17 657000000 256QAM 11.100 17 40.366
18 663000000 256QAM 11.000 18 40.946
19 669000000 256QAM 11.500 19 40.946
20 675000000 256QAM 10.900 20 40.366
21 681000000 256QAM 9.900 21 40.366
22 687000000 256QAM 8.400 22 40.946
23 555000000 256QAM 10.600 1 40.366
24 699000000 256QAM 7.800 24 40.946
Upstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID BandWidth
1 23700235 ATDMA - 64QAM 34.250 2 6400000
2 38595961 ATDMA - 64QAM 38.250 3 3200000
3 30595844 ATDMA - 64QAM 36.500 1 6400000

 

 

Re: Suffering Packet loss

khorton
I Plan to Stick Around

Interpreting PingPlotter Packet Loss Data?

 

We're having frequent episodes of very slow network response - i.e. web pages take much longer than normal to load, if they load at all. I've called Rogers numerous times - they sent out a tech to checkout things the first time, but he found nothing wrong with the local network, and the situation was not resolved. On subsequent calls, the tech has connected to the modem, but nothing was amiss as the problem had resolved itself while I waited on hold.

 

Two days I downloaded PingPlotter and left it running to gather data.

 

Yesterday was a particularly bad day for the network, so I called Rogers again. The tech was trying to point the finger at some possible issue in our local Ethernet cabling, so after the call ended I temporarily connected the modem directly to our main computer (bypassing the switch), and disconnected the rest of the local network. The problem reoccured later in the day, which proves that the local network is not the root cause.

 

This morning I fiddled with the display options in PingPlotter to show packet loss at hops 1, 2 and last, and I think I have evidence that the packet loss is not occurring in our home network, but is occurring between the modem and the next upstream node. Is that the correct way to interpret this plot?  

 

If so, I think that means the problem could be in the coax between the modem and the connection point in the basement, or in the coax between the house and the network line running down our road, or in the connection box at the road.  Comments?

 

20160818-0724-30mn-www.google.com IP removed.png

 

Edit - we've got Ignite 100U service, and a CGN3 modem.

 

Thanks for your comments and advice,

 

Kevin

Re: Suffering Packet loss

@khorton you are correct.  At some point between the modem and the Cable Modem Termination System (line 2), you have packet loss.  That could exist internally as you indicated, between the modem and splitter or connector in the basement, or, between the basement splitter/connector and the neighborhood node, which is the CMTS.  You could rule out the internal network by parking the modem downstairs as a test and run pingplotter when the modem is up and running.  If you see the same packet loss come up, then you would rule out the internal network.  Note that you would have to know that the incoming cable doesn't run anywhere near an electric motor or near any electrical cables that could draw a substantial amount of current.  Furnace motors come to mind.

 

When you see packet loss like that, that is the best time to call tech support and ask the CSR to run a signal check on the modem, looking specifically for packet loss and noise.  Ask the CSR to check the noise history for the last 24 hours to see what comes up.  Presumably, the CSR would detect the same packet loss that you are seeing, and arrange for a tech visit.  Ask the CSR to check for packet loss for your neighbors as well, as you would all be connected to the same local tap.  There is a good chance that this also affects your neighbors as well.  

 

What you can do with pingplotter is copy the line 2 IP address and paste it into the top address bar and let the application run.  Now you're pinging the CMTS, so you don't have to play around with the display to show that connection point.  The target at this point is to identify the packet loss issue with tech support, check for noise, and see if your neighbors are having the same issue.  It might be a noise issue generated by one of your neighbors backfeeding a signal of some type into the network, causing problems for the whole neighborhood.  If so, that will take some time to track down.  

 

Note that you also have high ping times showing in that image.  From that I'm assuming that you're on a Casa Systems CMTS.  To confirm that, log into the modem, navigate to the STATUS .... DOCSIS WAN page and see how many downstream channels you have.  20 channels equates to a Cisco Systems CMTS, 24 equates to a Casa Systems CMTS.  You could have 32 channels if you were running a gigabit CGNM-3552 modem.  The other confirmation is to navigate to the DOCSIS EVENTS page and look for the following sequence in the log:  CMTS-MAC=00:17:10:XX:XX:XX.  That sequence indicates a Casa Systems CMTS.

 

The change over from a Cisco Systems CMTS to a Casa Systems CMTS is recent, brought in to support gigabit rates and other future goodies that we're not aware of as of yet.  An unexpected problem has arisen between the Casa CMTS and the Hitron modem that is causing high ping times to the CMTS.  This also has a side effect of introducing high ping times to anywhere beyond the CMTS as well.  Rogers, Casa Systems and Hitron are working on the problem.  I haven't seen any news recently so I don't know where the investigation or solutions are at.  All this to say that tech support can't help with the high ping times.  Thats an engineering issue that is progressing.  Tech support can however help with the packet loss, so thats the approach to take for now.  

 

Hope this helps 



Re: Suffering Packet loss

@AHxCode, your downstream signal levels are pretty high, and you have one upstream channel which is just under the normal range.  The signal to noise levels are ok.  

 

Typically the signal levels are 0 dBmV for the downstream signals with a signal to noise ratio of 36 to 40 dB.  The upstream are normally in a 36 to 40 dBmV range.  

 

Call tech support and ask the CSR to run a signal check on the modem and check for packet loss as well.  I would think that the high levels will result in a tech visit, but, I suspect that all he or she will do is install a signal attenuator to drop the downstream levels by about 9 dBmV.  That should also push the upstream levels up by 9 dBmV as well.  That would resolve the signal issue, but I don't know if it will take care of any packet loss.  

 

Please read my comments in the above post regarding high ping times to the CMTS, as you are on a Casa systems CMTS.  

 

One suggestion I would have is the following, which will allow you to check for packet loss.  Load pingplotterpro from www.pingplotter.com.  It will run in PRO mode for 14 days before it kicks down to Freebie mode if you don't buy the intermediate or advanced licence.  When you have that loaded, and started, right click on the top title bar to bring up the column menu.  Select MAX and JTTR to display those columns and drag those columns right so that their sitting beside the MIN column.  In the Focus drop down menu on the upper right, select ALL for now so that it holds and displays the extreme values of the MIN, MAX, Jitter and Packet loss data and averages the ping times from the time that its selected.  This will show if at some point you have packet loss problems, even if that comes and goes.  Then start a test session out to something like google.ca. and hit the green "Go" button.  Drag the bottom area up to the bottom of the data area to expand the scaling for that lower data area. Right click on the lower area and set the display time for 5 minutes.  Let that run for five minutes, filling the lower display area.  Then, select Edit .... Copy as Image. Dump the clipboard contents to something like MS paint, wipe out the line 1 address as it will most likely be an IPV6 address for your modem and then save that image.  Run another test but this time change the Focus time in the upper right to 30 seconds.  To start that, hit the down arrow next to the pause button and select "Reset and Restart".  Let that run for a minute or two.  This will show if you have ongoing packet loss problems as the data lookback for the upper data area is only 30 seconds instead of all of the data. Then run the same Edit .... Copy as image routine...... If you see any packet loss shown in the packet loss column at any time, copy that image and save it and post that data. Thats what I'm interested at this point.

 

Insert those images into a post and indicate which Focus time is applicable..

 

 



Re: Suffering Packet loss

khorton
I Plan to Stick Around

@Datalink - thank you very much for the extremely useful info.

 

[quote]When you see packet loss like that, that is the best time to call tech support and ask the CSR to run a signal check on the modem, looking specifically for packet loss and noise.[/quote]

 

At the moment, I've swtiched the modem back to bridged mode, as I need port forwarding to work, and I've never succeeded to get it working on the CGN3.  Can a Rogers CSR access the modem if I have it bridged?

 

Should port forwarding work on a CGN3, with the latest firmware?  If so, I'll dig deeper, and open a different thread if necessary to get some assistance on that issue.

 

[quote]

Note that you also have high ping times showing in that image.  From that I'm assuming that you're on a Casa Systems CMTS.  To confirm that, log into the modem, navigate to the STATUS .... DOCSIS WAN page and see how many downstream channels you have.  20 channels equates to a Cisco Systems CMTS, 24 equates to a Casa Systems CMTS.  You could have 32 channels if you were running a gigabit CGNM-3552 modem.  The other confirmation is to navigate to the DOCSIS EVENTS page and look for the following sequence in the log:  CMTS-MAC=00:17:10:XX:XX:XX.  That sequence indicates a Casa Systems CMTS.

[/quote]

 

Are you refering to the ping times to the modem, or ping times from the modem to the CMTS?

 

I checked for the signatures of a Casa CMTS when I had the modem running in gateway mode.  I only had 20 channels, and I didn't see CMTS-MAC=00:17:10:XX:XX:XX in the logs.  I concluded that I still had a Cisco CMTS.  I'm living in a quasi-rural part of Ottawa - our local network infrastructure appears to be a bit out of date, so I doubt they've pushed us to the Casa CMTS yet.  The best Bell offers in this area is 5 Mbps down, so Rogers isn't being pushed to upgrade.

 

 

Re: Suffering Packet loss

@khorton, yup, the CSR can interrogate the modem regardless of the modem operating mode. 

 

Port forwarding should work, but, the modem only allows 9 port forwarding rules from what I understand, so if you have multiple devices that require port forwarding, you could run short of rule space fairly fast.  The NAT on the modem is also strict, which causes a lot of problems with port forwarding.  So, switching to Bridge mode and using your own router is a much easier and reliable way to carry out any port forwarding that you need to do.  

 

With a Cisco CMTS you would probably see one of the following sequences in your Docsis Events Log:

 

1. CMTS-MAC=00:05:00
2. CMTS-MAC=00:12:43
3. CMTS-MAC=00:14:f1
4. CMTS-MAC=00:1e:be
5. CMTS-MAC=00:1f:ca
6. CMTS-MAC=e0:2f:6d      Note: there may be other Cicso MAC addresses
                                                             as well which are not on this list yet.

 

The ping times that I was referring to are between the modem and the CMTS, but, looking back at your pingplot, I see that you also have a high max time and occasional high ping times just getting to the router or modem, whichever was in operation.  The average time is also a little high. Those times to the modem or router should be 1 ms or less across the board.  Was this taken via ethernet or wifi?  Your average ping time on line 2, to the CMTS is a little high, personal opinion.  I'm comparing that to when we were on a Cisco CMTS, where the average time was 10 ms.  So, my guess at this point is that the packet loss is leading to the higher than normal average and max ping times.  

 

Fwiw, we're in Stittsville.  We've been switched to the Casa CMTS, as has Kanata, and further south I believe.  Can't vouch for anything further east or north.  I would expect your area to change fairly soon to a Casa CMTS, and when that happens, it will make the average and max ping time worse than they already are.  So, that puts a little impetus on solving the packet loss issue before the switch over, so that you have a better idea of what the true ping times are like.  What was the Focus time that you had set in the upper right hand corner of pingplotter, Auto or some other setting?  Just curious at this point.  



Re: Suffering Packet loss

khorton
I Plan to Stick Around

Thanks for the info.

 

I never got a single port forward rule to work with the CGN3.  I gave up pretty quickly when we first got it and just bridged the thing.  I tried again recently, with the now much newer firmware, and I still struck out.  Maybe I had something was dorked up with the NAT.

 

Ping times to modem - those times were with Ethernet.  I installed a pfSense router today, running a PC Engines APU2C4 CPU, and was very happy to see the ping times to the router average 0.3 to 0.4ms.  The ping times to the CMTS now average about 18ms, even without any packet loss.  Getting port forwarding to work on pfSense was "fun", as the docs assume everyone using them is a network guru, and I'm far from that.  Thanks to Google, I figured it out finally.

 

I think the focus time for that plot was Auto, but I'm not 100% sure anymore, as I was experimenting with different values as I figured out the program.

Re: Suffering Packet loss

Very  interesting.  I might bug you for some details on going pfSense.  Thinking of going that route as well.  I'm curious how fast that board might go considering that we're running the gigabit service.



Re: Suffering Packet loss

khorton
I Plan to Stick Around

@Datalink - I'd be happy to share my meagre knowledge about pfSense, but you'd probably be better served asking questions on the pfSense forums, as I'm very much a pfSense noob, and not a networking expert.

 

I just finished moving the modem to basement to connect directly to the coax coming in from outside, bypassing the coax from the basement to the home office.  I'm still getting packet loss, so I'll call Rogers support yet again.  At least this time I've got enough test data to rule out anything in the house.

 

 

2016-08-19-0932-60s-www.google.com.png

 

60s focus, taken after moving the modem to the basement.

 

Edit - I called support, and they also see the packet loss, and similar loss at several neighbours.  He raised a ticket for network maintenance to solve.

 

Re: Suffering Packet loss

I'll ask one of the mods to delete the image as it has your modem's IPV6 address in it.  Try this.  Instead of running the test out to google, use 2607:f798:80c:10e::1 which is the line 2 address.  That is the CMTS.  That will give you a bottom display for the modem to CMTS path.  The object of the exercise is to keep an eye on that path, looking for packet loss, and keeping an eye on it to determine if the maintenance crew manages to resolve the problem.  So, if you get a call one day to indicate that the issue has been resolved and yet you still see packet loss on that path, then, call tech support again when the packet loss is occurring to get the maintenance crew back out for another go.  When the local packet loss issue has been resolved, then any packet loss that you see further downstream when you run a test out to some far flung server should be due to the network path and its servers.  That can be resolved, but thats a network issue that requires the attention of the network engineering staff.  In theory, at that point, there shouldn't be any local packet loss issues clouding the picture.  

 

When you post those images, and you have an IPV6 address, as this one shows, dump the image into something like Microsoft Paint, wipe out that line one IPV6 address, save it and post it.  The remaining data, ie: the ping times can remain on the image, just wipe out the address.

 

If you click on your personal icon at the upper right hand corner of the page when you're logged in, select Profile from the pop up menu, then My Images to bring up your image library.  You can then delete the last image with the IPV6 address in it.  



Re: Suffering Packet loss

khorton
I Plan to Stick Around

@Datalink wrote:

I'll ask one of the mods to delete the image as it has your modem's IPV6 address in it.  Try this.  Instead of running the test out to google, use 2607:f798:80c:10e::1 which is the line 2 address.  That is the CMTS.  

Thanks for catching the embedded IP - I forgot to remove it.  I've deleted the image. And thanks for the advice on just going to the CMTS.

Re: Suffering Packet loss

AHxCode
I Plan to Stick Around

top one is 60 seconds bottom is 30 seconds, its still happening, im looking at WhatTheFast while gaming and i can see my Bytes sent jump from 7-15bytes up to50-70Bytes every couple minutes, 11.jpg22.jpgShould i use arin.net to find something?

Re: Suffering Packet loss

AHxCode
I Plan to Stick Around

Here is also an update on this, I had someone come over a couple weeks ago and "fix" it.

 

 

Downstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDSignal noise ratio (dB)
1639000000256QAM6.7003840.366
2363000000256QAM9.1001040.946
3369000000256QAM9.4001140.946
4375000000256QAM9.3001240.946
5381000000256QAM8.8001340.946
6387000000256QAM8.3001440.946
7393000000256QAM7.4001540.366
8399000000256QAM7.5001640.946
9405000000256QAM7.9001740.946
10411000000256QAM7.1001840.366
11417000000256QAM7.9001940.946
12423000000256QAM8.2002040.946
13429000000256QAM8.7002140.946
14435000000256QAM8.8002240.366
15441000000256QAM8.6002340.946
16447000000256QAM9.0002440.946
17555000000256QAM7.6002540.946
18561000000256QAM7.8002640.366
19567000000256QAM8.0002740.946
20573000000256QAM8.5002840.946
21633000000256QAM7.4003740.946
22357000000256QAM8.400940.946
23645000000256QAM7.0003940.366
24651000000256QAM8.4004040.366
Upstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDBandWidth
138595915ATDMA - 64QAM42.75033200000
230595528ATDMA - 64QAM41.25016400000
323700000ATDMA - 64QAM37.75026400000

I seem to have been connecting to a rogers line quite often while gaming 67.231.223.255 and i have had alot of issues with it, I dont know if thats the entire case though

Re: Suffering Packet loss

AHxCode
I Plan to Stick Around
http://imgur.com/a/AABcs shows what my gaming connection looks like. its very similar across all games

Re: Suffering Packet loss

Hello @AHxCode,

 

If that's what your connection looks like across all games, we would need to do some troubleshooting and check your connection.

 

Please PM us @CommunityHelps for further assistance.

 

RogersCorey

Re: Suffering Packet loss

cailerh
I've Been Here Awhile

Severe Packet Loss For The Last Week or 2.

 

I have been getting severe packet loss the last week or 2 at anytime between 10pm-3am. The way I am seeing the packet loss amounts is through my Teamspeak Connection Info. It spikes up to 60%. And it isn't the teamspeak server because it also disconnects me from my games and stops my Netflix stream. I called tech last night and was told there was an outage in my area and that it would be fixed soon. An hour later my net was fine. But once again tonight it spiked up to 60%. Am currently calling Tech Support again but am at a 36-54 minute wait. I am connected ethernet directly into my PC. It isn't just my PC because my cellphone can't load any websites at the same time that the packet loss is happening.

Re: Suffering Packet loss

 

Hello, @cailerh

 

Welcome to the Rogers Community Forums! Smiley Happy

 

Thank you for joining and posting your concern in the Community. Were you able to reach tech support and resolve the packet loss issue? If the issue is only happening at certain hours it could be related to noise in the signal.  Please send us a private message at @CommunityHelps when the packet loss is occurring so that it can be properly diagnosed. Our private messaging system is explained in this blog.

 

Cheers,

RogersMoin

Re: Suffering Packet loss

nuts
I've Been Around

My connection is suffering from packet loss under 5%, when the tech visited and ran his test he said everything looked fine and packet loss under 5% is considered within normal bounds. The packet loss is making connection sensitive tasks like gaming un-playable. What can I do to get this fixed? I have a cisco DPC3825 which has been replaced twice already, once by me and once by the tech and the issue hasn't resolved itself.

ping.jpg

Re: Suffering Packet loss

larryjhawkins
I Plan to Stick Around

Constant disconnects from Warcraft, mumble server and podcast freezing

 

I just got off a call with the tech support team, they have confirmed my Modem (Hitron Adv Wi-Fi Mdm) is fine and there are no issues with it. I realized from the webcast freezing that I was having problem with packet loss. I am running PathPing to various sites and I see consistent packet loss on the following backbone routers. there seems to be a connection between when There are high levels of packet loss on these routers and when my gaming and mumble server connections are bad Computing statistics for 175 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 3 33ms 0/ 100 = 0% 0/ 100 = 0% 99.254.158.1 45/ 100 = 45% | 4 37ms 45/ 100 = 45% 0/ 100 = 0% 66.185.91.145 55/ 100 = 55% | 3 29ms 0/ 100 = 0% 0/ 100 = 0% 99.254.158.1 0/ 100 = 0% | 4 36ms 50/ 100 = 50% 50/ 100 = 50% 66.185.91.145 0/ 100 = 0% | 3 116ms 0/ 100 = 0% 0/ 100 = 0% 99.254.158.1 55/ 100 = 55% | 4 70ms 55/ 100 = 55% 0/ 100 = 0% 66.185.91.145 45/ 100 = 45% |

Re: Suffering Packet loss

JohnyR
I Plan to Stick Around

Insane Latency and Packet Loss (Avg 150ms+, 2.56% PL in the last hour)

 

Here it goes again.. Had the same issue with my 3rd party ISP around the same time last year. Even after switching to Rogers GIG, it's back. Pretty sure there is something terribly wrong with my node when it gets cold outside.

 

Smokeping to the node:

 

Smokeping to Rogers.com

 

Smokeping to node over last 7 days:

 

Latency to Node (always get crazy latency around the evenings.....):

 

 

Signals:

Downstream Overview
Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Signal noise ratio (dB)
1	669000000	256QAM	0.100	43	37.356
2	363000000	256QAM	1.000	10	38.983
3	369000000	256QAM	1.400	11	38.983
4	375000000	256QAM	1.300	12	38.983
5	381000000	256QAM	1.300	13	38.605
6	387000000	256QAM	1.200	14	38.983
7	393000000	256QAM	1.400	15	38.983
8	399000000	256QAM	1.600	16	38.605
9	405000000	256QAM	1.300	17	38.983
10	411000000	256QAM	1.200	18	38.983
11	417000000	256QAM	1.500	19	38.605
12	423000000	256QAM	1.100	20	38.605
13	555000000	256QAM	0.300	25	37.636
14	561000000	256QAM	0.100	26	37.636
15	567000000	256QAM	0.100	27	38.605
16	573000000	256QAM	0.300	28	37.636
17	579000000	256QAM	-0.200	29	37.636
18	585000000	256QAM	0.100	30	38.605
19	591000000	256QAM	-0.300	31	37.636
20	597000000	256QAM	-0.600	32	37.636
21	603000000	256QAM	-0.100	33	38.605
22	609000000	256QAM	-0.100	34	37.636
23	615000000	256QAM	-0.200	35	37.636
24	621000000	256QAM	0.200	36	37.636
25	633000000	256QAM	-0.200	37	37.900
26	639000000	256QAM	0.000	38	37.900
27	645000000	256QAM	-0.500	39	37.600
28	651000000	256QAM	0.400	40	38.200
29	657000000	256QAM	-0.300	41	37.900
30	663000000	256QAM	-0.500	42	37.600
31	357000000	256QAM	1.000	9	39.500
32	675000000	256QAM	-0.800	44	37.300
Upstream Overview
Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	BandWidth
1	38596000	ATDMA - 64QAM	39.750	3	3200000
2	30596000	ATDMA - 64QAM	38.500	1	6400000
3	23700000	ATDMA - 64QAM	37.250	2	6400000

What's my best course of action here? I've gone through 10 techs last year with my old ISP (using Rogers lines), and they would never EVER recommend maintenance to take a look at the node. I really don't want to go through another 50+ calls with CS.