09-08-2019
08:33 PM
- last edited on
09-08-2019
08:48 PM
by
RogersMaude
Hello again, sorry for not responding sooner. I had a senior technician and a supervisor come in and try and fix it on Tuesday evening.
They found a very poor quality connector piece in the lines near my house and told me a maintenance crew would come out in the next few days to fix it.
I was hoping that would be all but unfortunately It's been replaced and I'm still getting the issue.
Here are a bunch of traceroutes. Keep in mind that most of them will probably look normal and that everything is fine. It's a really hard problem to fix and pinpoint the issue for because 90% of the time everything is running quite well. It's just without fail every 5 minutes or so I'll get a 5 second lag spike. This is especially frustrating in a 10+ minute endgame raid fight in Final Fantasy XIV.
I'm not sure what I'm supposed to edit out of these, so hopefully I edited out what I needed to
.
Tracing route to 204.2.229.10 over a maximum of 30 hops
1 <1 ms 1 ms 1 ms hitronhub.home [EDITED]
2 31 ms 24 ms 37 ms XX.XXX.XXX.1
3 18 ms 22 ms 10 ms 24.156.149.49
4 19 ms 12 ms 11 ms 9025-cgw01.ym.rmgt.net.rogers.com [24.156.147.153]
5 19 ms 10 ms 12 ms 9403-cgw01.bloor.rmgt.net.rogers.com [209.148.235.229]
6 25 ms 32 ms 20 ms 209.148.229.226
7 42 ms 30 ms 35 ms 209.148.231.50
8 28 ms 27 ms 50 ms ae-11.r00.nycmny17.us.bb.gin.ntt.net [140.174.28.13]
9 31 ms 30 ms 28 ms ae-7.r24.nycmny01.us.bb.gin.ntt.net [129.250.3.48]
10 95 ms 87 ms 99 ms ae-4.r22.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
11 88 ms 88 ms 86 ms ae-0.r23.sttlwa01.us.bb.gin.ntt.net [129.250.6.30]
12 126 ms 136 ms 109 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
13 127 ms 110 ms 113 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
14 138 ms 129 ms 130 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
15 132 ms 141 ms 116 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
16 108 ms 110 ms 105 ms 204.2.229.234
17 121 ms 112 ms 108 ms 204.2.229.10
Trace complete.
Tracing route to 204.2.229.10 over a maximum of 30 hops
1 1 ms 1 ms <1 ms hitronhub.home [EDITED]
2 13 ms 28 ms 19 ms XX.XXX.XXX.1
3 14 ms 18 ms 44 ms 24.156.149.49
4 12 ms 24 ms 16 ms 9025-cgw01.ym.rmgt.net.rogers.com [24.156.147.153]
5 15 ms 29 ms 34 ms 9403-cgw01.bloor.rmgt.net.rogers.com [209.148.235.229]
6 25 ms 40 ms 31 ms 209.148.229.226
7 42 ms 29 ms 26 ms 209.148.231.50
8 31 ms 32 ms 28 ms ae-11.r00.nycmny17.us.bb.gin.ntt.net [140.174.28.13]
9 26 ms 29 ms 30 ms ae-7.r24.nycmny01.us.bb.gin.ntt.net [129.250.3.48]
10 * 92 ms 85 ms ae-4.r22.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
11 86 ms 123 ms 86 ms ae-0.r23.sttlwa01.us.bb.gin.ntt.net [129.250.6.30]
12 102 ms 106 ms 104 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
13 107 ms 109 ms 109 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
14 125 ms 111 ms 117 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
15 115 ms 132 ms 113 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
16 109 ms 129 ms 114 ms 204.2.229.234
17 113 ms 107 ms 128 ms 204.2.229.10
Trace complete.
Tracing route to 204.2.229.10 over a maximum of 30 hops
1 1 ms 1 ms 1 ms hitronhub.home [EDITED]
2 9 ms 8 ms 26 ms XX.XXX.XXX.1
3 21 ms 64 ms 15 ms 24.156.149.49
4 11 ms 12 ms 12 ms 9025-cgw01.ym.rmgt.net.rogers.com [24.156.147.153]
5 12 ms 11 ms 11 ms 9403-cgw01.bloor.rmgt.net.rogers.com [209.148.235.229]
6 26 ms 38 ms 24 ms 209.148.229.226
7 27 ms 44 ms 39 ms 209.148.231.50
8 27 ms 28 ms 28 ms ae-11.r00.nycmny17.us.bb.gin.ntt.net [140.174.28.13]
9 28 ms 27 ms 27 ms ae-7.r24.nycmny01.us.bb.gin.ntt.net [129.250.3.48]
10 92 ms 85 ms 89 ms ae-4.r22.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
11 * * * Request timed out.
12 132 ms 156 ms 102 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
13 155 ms 123 ms 116 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
14 113 ms 109 ms 113 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
15 * 2481 ms 119 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
16 120 ms 153 ms 113 ms 204.2.229.234
17 113 ms 137 ms 105 ms 204.2.229.10
Trace complete.
C:\Users\micha> tracert 204.2.229.10
Tracing route to 204.2.229.10 over a maximum of 30 hops
1 1 ms 1 ms <1 ms hitronhub.home [EDITED]
2 18 ms 29 ms 29 ms XX.XXX.XXX.1
3 56 ms 27 ms 14 ms 24.156.149.49
4 12 ms 12 ms 14 ms 9025-cgw01.ym.rmgt.net.rogers.com [24.156.147.153]
5 10 ms 16 ms 13 ms 9403-cgw01.bloor.rmgt.net.rogers.com [209.148.235.229]
6 65 ms 23 ms 22 ms 209.148.229.226
7 47 ms 29 ms 42 ms 209.148.231.50
8 30 ms 80 ms 34 ms ae-11.r00.nycmny17.us.bb.gin.ntt.net [140.174.28.13]
9 45 ms 28 ms 45 ms ae-7.r24.nycmny01.us.bb.gin.ntt.net [129.250.3.48]
10 * 107 ms * ae-4.r22.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
11 95 ms 92 ms 86 ms ae-0.r23.sttlwa01.us.bb.gin.ntt.net [129.250.6.30]
12 111 ms 118 ms 102 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
13 113 ms 110 ms 128 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
14 107 ms 109 ms 119 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
15 111 ms 112 ms 111 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
16 113 ms 114 ms * 204.2.229.234
17 109 ms 109 ms 108 ms 204.2.229.10
Trace complete.
Tracing route to 204.2.229.10 over a maximum of 30 hops
1 1 ms 1 ms <1 ms hitronhub.home [EDITED]
2 71 ms 8 ms 11 ms XX.XXX.XXX.1
3 126 ms 181 ms 194 ms 24.156.149.49
4 40 ms 150 ms 76 ms 9025-cgw01.ym.rmgt.net.rogers.com [24.156.147.153]
5 33 ms 47 ms 17 ms 9403-cgw01.bloor.rmgt.net.rogers.com [209.148.235.229]
6 26 ms 38 ms 79 ms 209.148.229.226
7 31 ms 86 ms 27 ms 209.148.231.50
8 49 ms 64 ms 33 ms ae-11.r00.nycmny17.us.bb.gin.ntt.net [140.174.28.13]
9 41 ms 27 ms 31 ms ae-7.r24.nycmny01.us.bb.gin.ntt.net [129.250.3.48]
10 * * * Request timed out.
11 114 ms 91 ms * ae-0.r23.sttlwa01.us.bb.gin.ntt.net [129.250.6.30]
12 105 ms 127 ms 101 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
13 112 ms 112 ms 117 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
14 118 ms 132 ms 110 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
15 118 ms 122 ms 118 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
16 133 ms 106 ms 130 ms 204.2.229.234
17 286 ms 106 ms 203 ms 204.2.229.10
**Edited post to remove Personal IP**
09-17-2019 08:07 PM
Hi,
I'm having similar problems. Playing Overwatch is mostly okay, with the odd lag spike. Once I start streaming though, the lag is relentless and usually leads right to a DC.
This has been going on for years across various modems, games (WoW, CSGO, some emulation stuff, and most recently OW) and no amount of service upgrades or swapping has offered lasting fixes. I'm at the end of my tether here.
Here's the deets. Thanks for anything you can offer.
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 669000000 | 256QAM | 2.900 | 19 | 38.983 |
2 | 849000000 | 256QAM | 1.300 | 2 | 38.605 |
3 | 855000000 | 256QAM | 1.300 | 3 | 38.605 |
4 | 861000000 | 256QAM | 1.400 | 4 | 38.605 |
5 | 579000000 | 256QAM | -1.200 | 5 | 38.983 |
6 | 585000000 | 256QAM | -0.300 | 6 | 38.605 |
7 | 591000000 | 256QAM | -0.300 | 7 | 38.605 |
8 | 597000000 | 256QAM | -0.700 | 8 | 38.983 |
9 | 603000000 | 256QAM | 0.000 | 9 | 38.983 |
10 | 609000000 | 256QAM | 0.200 | 10 | 38.605 |
11 | 615000000 | 256QAM | 0.000 | 11 | 38.605 |
12 | 621000000 | 256QAM | 0.100 | 12 | 38.605 |
13 | 633000000 | 256QAM | 0.500 | 13 | 38.605 |
14 | 639000000 | 256QAM | 1.200 | 14 | 38.983 |
15 | 645000000 | 256QAM | 0.600 | 15 | 38.605 |
16 | 651000000 | 256QAM | 1.400 | 16 | 38.605 |
17 | 657000000 | 256QAM | 1.400 | 17 | 38.983 |
18 | 663000000 | 256QAM | 1.900 | 18 | 38.983 |
19 | 279000000 | 256QAM | -3.200 | 1 | 37.636 |
20 | 675000000 | 256QAM | 3.500 | 20 | 40.366 |
21 | 681000000 | 256QAM | 3.500 | 21 | 38.983 |
22 | 687000000 | 256QAM | 4.000 | 22 | 38.605 |
23 | 693000000 | 256QAM | 3.300 | 23 | 38.983 |
24 | 699000000 | 256QAM | 4.100 | 24 | 38.983 |
25 | 705000000 | 256QAM | 3.500 | 25 | 38.983 |
26 | 711000000 | 256QAM | 3.000 | 26 | 38.983 |
27 | 717000000 | 256QAM | 2.700 | 27 | 38.983 |
28 | 723000000 | 256QAM | 1.800 | 28 | 38.605 |
29 | 825000000 | 256QAM | 1.500 | 29 | 38.983 |
30 | 831000000 | 256QAM | 1.900 | 30 | 38.605 |
31 | 837000000 | 256QAM | 1.600 | 31 | 38.983 |
32 | 843000000 | 256QAM | 1.200 | 32 | 38.605 |
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 | -3.000000 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 22100000 | ATDMA - 64QAM | 42.500 | 1 | 3200000 |
2 | 36996000 | ATDMA - 64QAM | 39.500 | 4 | 6400000 |
3 | 30596000 | ATDMA - 64QAM | 40.250 | 3 | 6400000 |
4 | 25300000 | ATDMA - 64QAM | 42.250 | 2 | 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 |
09-17-2019 08:40 PM
Hmm, this is interesting.
09-18-2019 08:24 PM
Hey @The_Ferd!
Thanks so much for dropping by the Lab!
Drops in connection while you're gaming can be beyond disruptive! We'll do what we can to assist in identifying where these drops are coming from. Based on the first image provided, the traceroute and ping aren't indicating any visible latency. The second image is a bit confusing as it's more indicative of a loss of connection or inability to maintain the traceroute over the 200s.
To validate this, are you able to run the traceroute while the game is being played? I'd love to see a live traces during the period of disconnect.
In addition can you confirm the following for us?
Thanks!
09-18-2019 08:50 PM
Hi, thanks for your reply.
This is a wired connection, the disconnects happen at any hour, all internet connectivity for the whole house dies and a speedtest from speedtest.net reports 52.38 Mbps down (not a typo, that's fifty-two), 21.63 up on an Ignite 500 plan.
I've been fighting versions of this problem for nearly all of the eight years I've lived here, and opened more support requests than I can count over it. Every time it's the same thing: Run a test, send a tech, tell me to spend more, upgrade my plan, here's a discount, new modem, and a week or a month later it's the same thing again. I've had enough (my last day as a Rogers customer is Friday) but hopefully what I've included here can help someone else.
09-22-2019
02:56 PM
- last edited on
09-22-2019
03:10 PM
by
RogersCorey
Hello everyone,
I have the Rogers Gigabit unlimited and CODA-4582U, my iMac connect directly to the router via ethernet (CAT7). Everything is perfect except the ping when I play an online game (League of Legends). Pings are not stable, it's around 30ms (great) but sometimes it increases up to 100 and higher within a few seconds then back to normal. I don't know whether the problem is caused from the inside (Lan) or outside (WAN) and how to solve it.
Below are my downstream and 3 tests on PingPlotter (192.168.0.1, 174.115.206.1 (tracert from www.google.ca); and 64.71.255.204.
Downstream Overview
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 597000000 | 256QAM | -1.800 | 8 | 38.983 |
2 | 849000000 | 256QAM | -0.900 | 2 | 40.366 |
3 | 855000000 | 256QAM | -1.500 | 3 | 38.983 |
4 | 861000000 | 256QAM | -3.000 | 4 | 38.605 |
5 | 579000000 | 256QAM | -1.000 | 5 | 40.366 |
6 | 585000000 | 256QAM | -0.800 | 6 | 40.366 |
7 | 591000000 | 256QAM | -1.500 | 7 | 40.946 |
8 | 279000000 | 256QAM | -1.800 | 1 | 38.983 |
9 | 603000000 | 256QAM | -0.700 | 9 | 40.366 |
10 | 609000000 | 256QAM | 0.100 | 10 | 40.366 |
11 | 615000000 | 256QAM | -0.200 | 11 | 40.366 |
12 | 621000000 | 256QAM | -1.300 | 12 | 40.366 |
13 | 633000000 | 256QAM | -0.700 | 13 | 40.366 |
14 | 639000000 | 256QAM | 0.000 | 14 | 40.366 |
15 | 645000000 | 256QAM | -0.500 | 15 | 40.366 |
16 | 651000000 | 256QAM | -1.200 | 16 | 40.366 |
17 | 657000000 | 256QAM | -1.300 | 17 | 38.983 |
18 | 663000000 | 256QAM | 0.300 | 18 | 40.366 |
19 | 669000000 | 256QAM | -0.100 | 19 | 40.366 |
20 | 675000000 | 256QAM | -0.400 | 20 | 40.366 |
21 | 681000000 | 256QAM | -1.700 | 21 | 38.605 |
22 | 687000000 | 256QAM | -1.200 | 22 | 38.983 |
23 | 693000000 | 256QAM | -0.100 | 23 | 40.366 |
24 | 699000000 | 256QAM | 0.300 | 24 | 40.366 |
25 | 705000000 | 256QAM | -0.700 | 25 | 40.366 |
26 | 711000000 | 256QAM | -0.700 | 26 | 40.946 |
27 | 717000000 | 256QAM | -0.900 | 27 | 40.366 |
28 | 723000000 | 256QAM | -0.200 | 28 | 40.366 |
29 | 825000000 | 256QAM | -3.500 | 29 | 38.983 |
30 | 831000000 | 256QAM | -2.900 | 30 | 38.983 |
31 | 837000000 | 256QAM | -1.500 | 31 | 40.366 |
32 | 843000000 | 256QAM | -1.300 | 32 | 40.366 |
[img]https://i.imgur.com/dRaCUWg.png[/img]
09-23-2019 12:31 PM
09-23-2019 03:41 PM
Greetings @phucnb!
Welcome to our Community. 🙂
Your modem levels appear to be within spec, so I don't suspect this to be a signal related issue at a glance. Were these levels captured while you were experiencing this issue?
If you would be so kind as to run the ping test as suggested by @elmirix that would give us a better idea of what we're working with here.
Regards,
RogersCorey
11-03-2019 01:13 AM
Hi Guys,
Glad I found this thread. I've been struggling with latency issues for quite some time now and I haven't been able to get it resolved with support. The last Senior Tech I had out indicated everything was good on the cabling and in spec. I play a lot of competitive FPS games and latency is a big issue for me. I see latency issues in all games, and can reproduce my latency issues with a simple ping. I get frequent spikes with my ping anytime of the day, but in the evening it's substantially worse.
I have no where to turn to at this point I hope you can help!
Modem Stats
Ping stats to google, this is a typical sample I see daily in the evening.
Below are some smokeping graphs which visually illustrate the issues and clearly show the variance and evening issues.
Below is to RogersDNS2 (64.71.255.198)
Below is to 8.8.8.8
Looking forward to you assistance!
11-04-2019 08:29 AM
Hello and welcome to our Community, @corm1!
I'm here to help, I just have a few clarifying questions first.
You mention that this issue is worse at night... did you perform these tests at night during the worst of the issues or during the day? Were the ping tests performed from a computer connected via Ethernet or WiFi? When did these issues first begin? Did they occur after an event that you can remember such as a bad storm or construction in the area?
If these tests weren't performed during the worst of the issues, could you run another set of tests in the evening for us?
Please let us know.
Regards,
RogersCorey