03-12-2020 12:16 PM
03-12-2020 12:28 PM - edited 03-12-2020 12:30 PM
You're no further ahead, as you would still be using Rogers cable system enroute to and from Teksavvy's data center. So you would still suffer from the same issues. Fwiw, Teksavvy customers have clearly stated that they are also experiencing the same issues:
https://www.dslreports.com/forum/r32668413-Cable-rCable-GTA
Teksavvy submitted a master ticket to Rogers, most likely a collection of customer locations and problems observed, Rogers refused to accept the ticket. Teksavvy hasn't indicated if they've been successful in addressing the situation at a higher level or not.
You're best bet for lower latency is DSL service with Bell or a TPIA, or fibre thru Bell if that is available to you. DSL will give you lower latency, at much less of a data rate, fibre would give you faster download and upload, with much lower latency. Main complaint seems to be with Bell's routing, which appears to go thru Chicago.
03-12-2020 08:16 PM
I have the pike spike issue. I have spoken with many Rogers agents including people from the office of the president. They refuse to acknowledge this is a widespread issue. After 2 of their technicians not able to solve my problem they told me they need to send another. It's been since early February. Every time I ask them if the technician cannot fix the issue what are the next steps. They never can give me an answer. I'm assuming they will keep sending endless technicians with the hopes I will eventually give up. They told me they cannot issue me credit because in their terms of service it says there is no guarantee in the quality of service. I don't really understand this because I'm not getting what I'm paying for.
03-13-2020 10:02 PM
03-14-2020 03:07 PM
Been playing World of Tanks mostly in the evenings after work and today as well, and can confirm that since all the upgrades in my area, including a new line from the pole into my house...gaming still sucks. From as low as 23 all the way up to 999+ ms, seems to me that ignite cannot handle TV, internet and home phone through a single router. Going to see what Bell now offers in my area. FYI, I'm in St. John's Nl and have been experiencing problems for almost 3 weeks with regards to any online gaming.
03-14-2020 04:33 PM
Been having similar problems here. I have the IGNITE Gigabite Internet Package and I've been doing Livestreaming and It can't go more than 10 seconds without dropping MASSIVE frames (And I'm talking literally losing the connection) I did a tracert to google.com and I'm getting response times of up to 1631ms past the Rogers CMTS...
In Guelph, Ontario here.
03-23-2020 04:41 PM
Hello,
I have been having issues for a very long time (Months). i have had techs coming to the house many times. its very frustrating since i pay for the top package at rogers - Ignite home phone, TV and Internet. 1000 download/ 30 upload. its very noticeable during any form of online gaming and streaming/watching videos. high pings/ lag spikes. also download and upload speeds are way lower then 1000download - 30 upload sometimes. While PC gaming and Xbox gaming same noticeable issue. pretty much you cant play any online game and sometimes watch videos online or stream such as twitch or youtube. here are what stats i have gotten, if there is anything missing please let me know. Thank you for your help!
IndexLock StatusFrequencySNRPower LevelModulation
Downstream | Channel Bonding Value | ||||||||||||||||||||||||||||||||
17 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 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 |
657 MHz | 279 MHz | 849 MHz | 855 MHz | 861 MHz | 579 MHz | 585 MHz | 591 MHz | 597 MHz | 603 MHz | 609 MHz | 615 MHz | 621 MHz | 633 MHz | 639 MHz | 645 MHz | 651 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 |
39.9 dB | 38.4 dB | 39.9 dB | 39.6 dB | 39.4 dB | 39.9 dB | 39.9 dB | 39.9 dB | 40.0 dB | 39.9 dB | 39.8 dB | 39.8 dB | 39.8 dB | 39.8 dB | 39.9 dB | 39.9 dB | 39.9 dB | 40.0 dB | 40.1 dB | 39.5 dB | 39.9 dB | 40.4 dB | 40.3 dB | 40.3 dB | 40.4 dB | 40.2 dB | 40.1 dB | 40.0 dB | 40.3 dB | 40.5 dB | 40.3 dB | 40.3 dB | 38.3 dB | NA |
3.3 dBmV | 1.9 dBmV | 3.6 dBmV | 2.8 dBmV | 2.2 dBmV | 3.1 dBmV | 2.7 dBmV | 3.2 dBmV | 3.5 dBmV | 2.8 dBmV | 2.5 dBmV | 3.2 dBmV | 2.8 dBmV | 2.2 dBmV | 3.2 dBmV | 3.2 dBmV | 3.2 dBmV | 4.1 dBmV | 4.2 dBmV | 3.5 dBmV | 4.4 dBmV | 5.8 dBmV | 5.3 dBmV | 4.8 dBmV | 5.4 dBmV | 5.1 dBmV | 4.3 dBmV | 3.9 dBmV | 5.2 dBmV | 5.2 dBmV | 4.7 dBmV | 4.4 dBmV | 2.3 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 |
IndexLock StatusFrequencySymbol RatePower LevelModulationChannel Type
Upstream | Channel Bonding Value | ||
1 | 2 | 3 | 4 |
Locked | Locked | Locked | Locked |
22 MHz | 25 MHz | 30 MHz | 36 MHz |
2560 | 2560 | 5120 | 5120 |
41.3 dBmV | 42.5 dBmV | 43.3 dBmV | 42.5 dBmV |
QAM | QAM | QAM | QAM |
TDMA_AND_ATDMA | TDMA_AND_ATDMA | ATDMA | ATDMA |
Pinging google.com [2607:f8b0:400b:809::200e] with 32 bytes of data:
Reply from 2607:f8b0:400b:809::200e: time=41ms
Reply from 2607:f8b0:400b:809::200e: time=26ms
Reply from 2607:f8b0:400b:809::200e: time=31ms
Reply from 2607:f8b0:400b:809::200e: time=57ms
Reply from 2607:f8b0:400b:809::200e: time=23ms
Reply from 2607:f8b0:400b:809::200e: time=18ms
Reply from 2607:f8b0:400b:809::200e: time=36ms
Reply from 2607:f8b0:400b:809::200e: time=33ms
Reply from 2607:f8b0:400b:809::200e: time=24ms
Reply from 2607:f8b0:400b:809::200e: time=33ms
Reply from 2607:f8b0:400b:809::200e: time=57ms
Reply from 2607:f8b0:400b:809::200e: time=21ms
Reply from 2607:f8b0:400b:809::200e: time=42ms
Reply from 2607:f8b0:400b:809::200e: time=98ms
Reply from 2607:f8b0:400b:809::200e: time=179ms
Reply from 2607:f8b0:400b:809::200e: time=23ms
Reply from 2607:f8b0:400b:809::200e: time=26ms
Reply from 2607:f8b0:400b:809::200e: time=24ms
Reply from 2607:f8b0:400b:809::200e: time=23ms
Reply from 2607:f8b0:400b:809::200e: time=125ms
Reply from 2607:f8b0:400b:809::200e: time=22ms
Reply from 2607:f8b0:400b:809::200e: time=58ms
Reply from 2607:f8b0:400b:809::200e: time=25ms
Reply from 2607:f8b0:400b:809::200e: time=30ms
Reply from 2607:f8b0:400b:809::200e: time=30ms
Reply from 2607:f8b0:400b:809::200e: time=25ms
Reply from 2607:f8b0:400b:809::200e: time=37ms
Reply from 2607:f8b0:400b:809::200e: time=43ms
Reply from 2607:f8b0:400b:809::200e: time=29ms
Reply from 2607:f8b0:400b:809::200e: time=45ms
Reply from 2607:f8b0:400b:809::200e: time=24ms
Ping statistics for 2607:f8b0:400b:809::200e:
Packets: Sent = 31, Received = 31, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 179ms, Average = 42ms
*Game - counter strike- global offensive. 1 of the CS GO server i was connected to.
Tracing route to 162.254.193.98 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 10.0.0.1
2 87 ms 18 ms 21 ms 99.247.166.1
3 86 ms 56 ms 69 ms rogers.com []
4 16 ms 34 ms 13 ms rogers.com []
5 26 ms 28 ms 16 ms 209.148.237.141
6 25 ms 88 ms 33 ms rogers.com []
7 154 ms 121 ms 88 ms 209.148.235.105
8 109 ms 43 ms 32 ms 162.254.193.222
9 60 ms 82 ms 55 ms 162.254.193.98
Trace complete.
04-02-2020 04:07 PM
1.
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 633000000 | 256QAM | 0.100 | 13 | 38.983 |
2 | 849000000 | 256QAM | -1.800 | 2 | 38.983 |
3 | 855000000 | 256QAM | -1.200 | 3 | 38.983 |
4 | 861000000 | 256QAM | -1.900 | 4 | 38.605 |
5 | 579000000 | 256QAM | 0.200 | 5 | 38.605 |
6 | 585000000 | 256QAM | -0.400 | 6 | 38.983 |
7 | 591000000 | 256QAM | 0.400 | 7 | 38.983 |
8 | 597000000 | 256QAM | 0.100 | 8 | 38.605 |
9 | 603000000 | 256QAM | -1.200 | 9 | 38.983 |
10 | 609000000 | 256QAM | -0.900 | 10 | 38.605 |
11 | 615000000 | 256QAM | -0.700 | 11 | 38.605 |
12 | 621000000 | 256QAM | -1.500 | 12 | 38.983 |
13 | 279000000 | 256QAM | 3.600 | 1 | 38.983 |
14 | 639000000 | 256QAM | -0.500 | 14 | 38.605 |
15 | 645000000 | 256QAM | -0.500 | 15 | 38.983 |
16 | 651000000 | 256QAM | 0.600 | 16 | 38.983 |
17 | 657000000 | 256QAM | 0.300 | 17 | 38.605 |
18 | 663000000 | 256QAM | 0.300 | 18 | 38.605 |
19 | 669000000 | 256QAM | 1.400 | 19 | 40.366 |
20 | 675000000 | 256QAM | -0.100 | 20 | 38.983 |
21 | 681000000 | 256QAM | -0.100 | 21 | 38.605 |
22 | 687000000 | 256QAM | 0.500 | 22 | 38.983 |
23 | 693000000 | 256QAM | -0.100 | 23 | 38.605 |
24 | 699000000 | 256QAM | -0.700 | 24 | 38.605 |
25 | 705000000 | 256QAM | 0.300 | 25 | 38.605 |
26 | 711000000 | 256QAM | -0.600 | 26 | 38.605 |
27 | 717000000 | 256QAM | -1.800 | 27 | 38.605 |
28 | 723000000 | 256QAM | -0.800 | 28 | 38.983 |
29 | 825000000 | 256QAM | -1.400 | 29 | 38.983 |
30 | 831000000 | 256QAM | -1.500 | 30 | 38.983 |
31 | 837000000 | 256QAM | -0.200 | 31 | 38.983 |
32 | 843000000 | 256QAM | -0.500 | 32 | 38.983 |
Receiver | FFT type | Subcarr 0 Frequency(MHz) | PLC locked | NCP locked | MDC1 locked | PLC power(dBmv) |
0 | NA | NA | NO | NO | NO | NA |
1 | 4K | 275600000 | YES | YES | YES | 2.200001 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 25300000 | ATDMA - 64QAM | 32.750 | 6 | 3200000 |
2 | 36996000 | ATDMA - 64QAM | 34.000 | 8 | 6400000 |
3 | 30596000 | ATDMA - 64QAM | 34.000 | 7 | 6400000 |
4 | 22100000 | ATDMA - 64QAM | 34.000 | 5 | 3200000 |
Channel Index | State | lin Digital Att | Digital Att | BW (sc's*fft) | Report Power | Report Power1_6 | FFT Size |
0 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
1 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
2.
Pinging google.ca [2607:f8b0:400b:809::2003] with 32 bytes of data:
Reply from 2607:f8b0:400b:809::2003: time=71ms
Reply from 2607:f8b0:400b:809::2003: time=84ms
Reply from 2607:f8b0:400b:809::2003: time=128ms
Reply from 2607:f8b0:400b:809::2003: time=204ms
Ping statistics for 2607:f8b0:400b:809::2003:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 71ms, Maximum = 204ms, Average = 121ms
3.
04-02-2020 04:25 PM
04-03-2020 04:11 PM
Hey @Ikam!
Welcome to the community!
Latency is certainly at the core of many issues that can plague the gaming experience and we'd be happy to assist in seeing to it's resolution. Thank you for providing the traceroute as well as it does indicate latency within the Rogers network. Have you reached out to support yet to have this investigated? If you need to please reach out to us @CommunityHelps. We would be happy to look into this for you. For more information on our PM system you can check out our blog.