10-12-2020 08:10 PM
Hello, @Shleffy
Thanks so much for following up with us regarding this matter.
Based on the traceroute, hop 4 is the last one within the Rogers network. There does not appear to be any latency showing in hops 1 - 4.
It's possible it could be an intermittent issue and may require consecutive traceroutes over a period of 3 - 5 minutes to determine if there is any latency that can be detected within our network.
You could also do the traceroutes to www.google.com as well to determine if there is latency within the Rogers network.
Regards,
CommunityHelps
RogersTony
10-13-2020 09:18 PM
Hi @RogersTony !
I'm starting to wrap my head around this. I thought the tracert was used to identify where the hops were, not that you may be looking for the latency, or flat out "Time-outs". Below are Twitch and Google results, keeping in mind that I did reconnect my network and I'm not directly to the modem in bridge mode anymore:
Twitch
Tracing route to yto.contribute.live-video.net [52.223.243.219]
over a maximum of 30 hops:
1 <1 ms 1 ms 1 ms 192.168.86.1
2 19 ms 19 ms 16 ms XXXXXXXXXXX
3 14 ms 15 ms 16 ms 8080-dgw02.ktgc.rmgt.net.rogers.com [66.185.90.69]
4 18 ms 20 ms 21 ms 209.148.233.229
5 101 ms * 36 ms 209.148.233.102
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Google
Tracing route to google.com [172.217.164.238]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.86.1
2 18 ms 18 ms 15 ms XXXXXXXXXXXXX
3 15 ms 13 ms 14 ms 8080-dgw02.ktgc.rmgt.net.rogers.com [66.185.90.69]
4 16 ms 17 ms 16 ms 209.148.233.233
5 15 ms 19 ms 17 ms 209.148.233.38
6 * * * Request timed out.
7 23 ms 22 ms 17 ms 74.125.244.161
8 16 ms 20 ms 21 ms 216.239.42.61
9 18 ms 24 ms 18 ms yyz12s05-in-f14.1e100.net [172.217.164.238]
Trace complete.
Best,
Chris L
10-14-2020 09:10 PM
Thank you @Shleffy.
There is latency on the fifth hop there that exceeds 100ms. Assuming this connection isn't through a third party device (as this would make the results unusable for us) can you reach out to us via PM @CommunityHelps?
There's some additional tests we would like to run to validate the latency. For more information on our PM system click here.
Thanks!
10-16-2020 08:09 AM
10-16-2020 09:08 PM
Hi @RogersMike
I hope this is what you were looking for.
IndexLock StatusFrequencySNRPower LevelModulation
Downstream | Channel Bonding Value | ||||||||||||||||||||||||||||||||
8 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | |
Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked |
597 MHz | 279 MHz | 849 MHz | 855 MHz | 861 MHz | 579 MHz | 585 MHz | 591 MHz | 603 MHz | 609 MHz | 615 MHz | 621 MHz | 633 MHz | 639 MHz | 645 MHz | 651 MHz | 657 MHz | 663 MHz | 669 MHz | 675 MHz | 681 MHz | 687 MHz | 693 MHz | 699 MHz | 705 MHz | 711 MHz | 717 MHz | 723 MHz | 825 MHz | 831 MHz | 837 MHz | 843 MHz | 350 MHz | 275600000 |
38.6 dB | 38.8 dB | 38.6 dB | 38.9 dB | 38.8 dB | 38.8 dB | 38.6 dB | 38.6 dB | 38.5 dB | 38.8 dB | 38.5 dB | 38.6 dB | 38.6 dB | 38.8 dB | 38.7 dB | 38.4 dB | 38.7 dB | 38.9 dB | 39.0 dB | 38.5 dB | 38.8 dB | 38.8 dB | 38.7 dB | 38.9 dB | 39.0 dB | 38.9 dB | 39.1 dB | 38.8 dB | 39.2 dB | 39.1 dB | 38.7 dB | 38.9 dB | 38.4 dB | NA |
0.7 dBmV | 3.2 dBmV | 0.2 dBmV | 0.4 dBmV | 0.2 dBmV | 1.1 dBmV | 0.3 dBmV | 0.5 dBmV | 0.2 dBmV | 1.1 dBmV | 0.2 dBmV | 0.4 dBmV | 0.5 dBmV | 1.4 dBmV | 0.6 dBmV | 0.3 dBmV | 1.2 dBmV | 0.9 dBmV | 1.8 dBmV | 1.4 dBmV | 0.5 dBmV | 1.0 dBmV | 0.4 dBmV | 0.9 dBmV | 1.4 dBmV | 0.3 dBmV | 1.2 dBmV | 0.4 dBmV | 1.3 dBmV | 1.1 dBmV | 0.2 dBmV | 0.8 dBmV | 3.1 dBmV | NA |
256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | OFDM | OFDM |
10-16-2020
11:38 PM
- last edited on
10-17-2020
09:39 PM
by
RogersTony
Losing Bitrate While Streaming To Twitch. This is my second time back to this forum to get some help. For the past month and a half my internet has been having problems streaming to twitch. I've had 4 different techs come to my house and had countless things replaced with still no fix. The techs keep saying there is nothing wrong but I find that hard to believe. When my internet was working I was able to stream at 1080p 60fps at 8000 bitrate. I currently cannot go 10 seconds without dropping a major amount of frames.
I'm not too sure how to find the upstream and downstream chart on the ignite modem so it wont be attached but i do have the twitch traceroute and the ping to google. Any help with this would be greatly appreciated.
10-17-2020 06:08 PM - edited 10-17-2020 06:10 PM
Hello, @lethalsniper, @mr_wood, @aasar, & @Koma
Welcome to the Rogers Community Forums! - @aasar 🙂
@lethalsniper - All of our modems are capable of online gaming but I would recommend the latest modem which is the XB6 made by Technicolor which has the Broadcom chipset.
@mr_wood - Thanks so much for providing us with the signal levels to the modem. They appear to be within the optimal specification. Please follow the steps outlined in our Troubleshooting Latency knowledge base article. Please provide us with the results of a ping test and a traceroute to google using the command prompt.
@aasar & @Koma - I can understand how frustrating it is trying to stream when you are dropping frames. We'll need to take a look at the signal levels on your modem to determine if there is an RF issue that may be causing poor performance. Please take a look at our Troubleshooting a Slow or Intermittent Connection and provide us with the signal levels for your modem.
@Koma - Thanks so much for providing us with the traceroutes to Google and Twitch. There does not appear to be any latency over 100 ms in the results you've sent. It's possible this could be an intermittent issue, in that case, you may need to run consecutive traceroutes over a period of 3 - 5 minutes to either Google or Twitch. If you are able to detect latency over 100 ms in any of these tests, please provide us with the results of the tests showing latency so we can review it.
We look forward to reviewing your results!
RogersTony
10-17-2020 06:44 PM - edited 10-17-2020 06:46 PM
10-18-2020 12:12 PM
10-18-2020 03:29 PM