@RyzenFX wrote:
OP was mistaken and thought it was FTTC, but instead they replaced the existing coax with new coax. They also relieved any sort of congestion experienced by adding 4-5 new nodes, as well as another 4-5 new nodes in the other end of OP's neighbourhood.
I agree with you that internet prices are too expensive, and we do need competition to lower prices but with so little competition there's not really much we can do than bargain for better deals like the $35 500u going around right now.
Have you ever talked to customer support about congestion in your neighborhood? Maybe they could give you some insight if your neighbourhood is slated to be upgraded like the one above.
Thx.....I was being factious.
I have spoken with CS but led to nothing..... will also look into OP's comments. Pricing and Performance are just but a few things. My other point was about clarity....Rogers should clarify their Ultimate Fibre/Hybrid Fibre vs Ignite Internet offerings. It's unclear to me.....Where an Ultimate Fibre 350Dwn/350Up and Hybrid Fibre 250, 150, 60 fit in their Ignite Internet line of 1Gb/500Mb/150Mb. If you add pricing...it really gets confusing and weird (without even considering performance). Add Ignite IPTV....and it gets blurry, when bandwidth, latency and consistency are paramount.
Has anyone dealt with the OoP (office of the president) and received favorable results? 
@ffdhfhf there is a good chance that you have a cable or connector issue on the go. That problem can be temporarily resolved by a modem reboot, but, the reboot doesn't solve the underlying problem. No doubt there is the possibility that there might be a modem bug which takes a considerable amount of time to manifest itself, but, a cable and/or connector issues comes to mind when I see a packet loss indication such as yours.
To determine if there is a packet loss problem with the external cabling or connectors:
1. Run a trace to anywhere: tracert www.google.com
2. Take the second IP address in that trace which should be the Cable Modem Termination System address, and ping that address: ping -t xxx.xxx.xxx.xxx
3. Let that ping test run for a considerable amount of time. I'm assuming that you have an unlimited account. If so let that run overnight.
4. Check the final results when you terminate the test. Use Crtl + C to terminate the test. If you have a packet loss situation still on the go, you should see that in the results of the ping test. If you watch the test while its running, you might see the lost packets as they occur.
5. If you do confirm that there is a packet loss situation on the go, call tech support and advise the Customer Service Rep that your seeing packet loss between the modem and the CMTS. Ask him or her to run a signal check on the modem. That may or may not indicate a problem with the signal levels. Its a one shot check, running only when requested by the CSR. So, it may or may not catch a signal issue. The ongoing ping test will pick up on packet loss issues. The CSR can also run a ping test, either by pinging the modem, or by pinging the CMTS from the modem.
@ASimkins , can you let me know:
1. what your ping target is; and
2. what type of ping your're using, ICMP, TCP/IP, or UDP? and
3. What you're using to run the ping test, Command line ping with text data, Command line ping using Wireshark to plot the data, or Pingplotter to run and plot the test?
-
944581 views
-
669 Likes
-
-
