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.
1.
Downstream Overview
| 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 |
OFDM Downstream Overview
| 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 |
Upstream Overview
| 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 |
OFDM/OFDMA Overview
| 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.
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.
