Consistently dealing with jitter on my ping, online games unplayable

[rwestlake]

Hi,

I am on gigabit ignite rogers internet and am consistently dealing with ping spikes throughout the day ranging from 100 ms to multiple seconds.  There is no packet loss. 

I have followed up with many Rogers techs and had multiple investigations but they have stated at this point my service is acceptable and nothing further will be done, per their explanation since there is no packet loss the level of service being met is adequate.  Have swapped out modems, cables, changed cable boxes, connected directly to the modem with different ethernet cables (ruling out my router) and nothing seems to be resolving the root cause.  I am not optimistic anything can be done at this point and given my lack of alternatives in the area (only other plan avail is 50 mb down from Bell due to lack of competition for internet providers).  

I have looked at a couple other message threads dealing with approximately the same issue and have pre-included data requested on those threads for my case.  Any suggestions are appreciated!  Happy to include more details if requested.

Ping test through router

ping www.google.com -n 50

Pinging www.google.com [2607:f8b0:400b:802::2004] with 32 bytes of data:
Reply from 2607:f8b0:400b:802::2004: time=301ms
Reply from 2607:f8b0:400b:802::2004: time=17ms
Reply from 2607:f8b0:400b:802::2004: time=499ms
Reply from 2607:f8b0:400b:802::2004: time=128ms
Reply from 2607:f8b0:400b:802::2004: time=481ms
Reply from 2607:f8b0:400b:802::2004: time=30ms
Reply from 2607:f8b0:400b:802::2004: time=138ms
Reply from 2607:f8b0:400b:802::2004: time=1106ms
Reply from 2607:f8b0:400b:802::2004: time=18ms
Reply from 2607:f8b0:400b:802::2004: time=224ms
Reply from 2607:f8b0:400b:802::2004: time=62ms
Reply from 2607:f8b0:400b:802::2004: time=260ms
Reply from 2607:f8b0:400b:802::2004: time=203ms
Reply from 2607:f8b0:400b:802::2004: time=36ms
Reply from 2607:f8b0:400b:802::2004: time=284ms
Reply from 2607:f8b0:400b:802::2004: time=143ms
Reply from 2607:f8b0:400b:802::2004: time=263ms
Reply from 2607:f8b0:400b:802::2004: time=59ms
Reply from 2607:f8b0:400b:802::2004: time=128ms
Reply from 2607:f8b0:400b:802::2004: time=34ms
Reply from 2607:f8b0:400b:802::2004: time=79ms
Reply from 2607:f8b0:400b:802::2004: time=135ms
Reply from 2607:f8b0:400b:802::2004: time=146ms
Reply from 2607:f8b0:400b:802::2004: time=168ms
Reply from 2607:f8b0:400b:802::2004: time=70ms
Reply from 2607:f8b0:400b:802::2004: time=75ms
Reply from 2607:f8b0:400b:802::2004: time=134ms
Reply from 2607:f8b0:400b:802::2004: time=194ms
Reply from 2607:f8b0:400b:802::2004: time=166ms
Reply from 2607:f8b0:400b:802::2004: time=72ms
Reply from 2607:f8b0:400b:802::2004: time=343ms
Reply from 2607:f8b0:400b:802::2004: time=322ms
Reply from 2607:f8b0:400b:802::2004: time=301ms
Reply from 2607:f8b0:400b:802::2004: time=282ms
Reply from 2607:f8b0:400b:802::2004: time=58ms
Reply from 2607:f8b0:400b:802::2004: time=16ms
Reply from 2607:f8b0:400b:802::2004: time=48ms
Reply from 2607:f8b0:400b:802::2004: time=26ms
Reply from 2607:f8b0:400b:802::2004: time=123ms
Reply from 2607:f8b0:400b:802::2004: time=25ms
Reply from 2607:f8b0:400b:802::2004: time=18ms
Reply from 2607:f8b0:400b:802::2004: time=330ms
Reply from 2607:f8b0:400b:802::2004: time=51ms
Reply from 2607:f8b0:400b:802::2004: time=23ms
Reply from 2607:f8b0:400b:802::2004: time=19ms
Reply from 2607:f8b0:400b:802::2004: time=116ms
Reply from 2607:f8b0:400b:802::2004: time=127ms
Reply from 2607:f8b0:400b:802::2004: time=23ms
Reply from 2607:f8b0:400b:802::2004: time=101ms
Reply from 2607:f8b0:400b:802::2004: time=27ms

Ping statistics for 2607:f8b0:400b:802::2004:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 1106ms, Average = 160ms

Ping test directly connected to modem

ping www.google.com -n 50

Pinging www.google.com [2607:f8b0:400b:807::2004] with 32 bytes of data:
Reply from 2607:f8b0:400b:807::2004: time=122ms
Reply from 2607:f8b0:400b:807::2004: time=102ms
Reply from 2607:f8b0:400b:807::2004: time=29ms
Reply from 2607:f8b0:400b:807::2004: time=34ms
Reply from 2607:f8b0:400b:807::2004: time=27ms
Reply from 2607:f8b0:400b:807::2004: time=290ms
Reply from 2607:f8b0:400b:807::2004: time=63ms
Reply from 2607:f8b0:400b:807::2004: time=203ms
Reply from 2607:f8b0:400b:807::2004: time=182ms
Reply from 2607:f8b0:400b:807::2004: time=841ms
Reply from 2607:f8b0:400b:807::2004: time=2238ms
Reply from 2607:f8b0:400b:807::2004: time=20ms
Reply from 2607:f8b0:400b:807::2004: time=959ms
Reply from 2607:f8b0:400b:807::2004: time=23ms
Reply from 2607:f8b0:400b:807::2004: time=27ms
Reply from 2607:f8b0:400b:807::2004: time=24ms
Reply from 2607:f8b0:400b:807::2004: time=17ms
Reply from 2607:f8b0:400b:807::2004: time=23ms
Reply from 2607:f8b0:400b:807::2004: time=715ms
Reply from 2607:f8b0:400b:807::2004: time=23ms
Reply from 2607:f8b0:400b:807::2004: time=81ms
Reply from 2607:f8b0:400b:807::2004: time=15ms
Reply from 2607:f8b0:400b:807::2004: time=1373ms
Reply from 2607:f8b0:400b:807::2004: time=1524ms
Reply from 2607:f8b0:400b:807::2004: time=88ms
Reply from 2607:f8b0:400b:807::2004: time=24ms
Reply from 2607:f8b0:400b:807::2004: time=13ms
Reply from 2607:f8b0:400b:807::2004: time=21ms
Reply from 2607:f8b0:400b:807::2004: time=18ms
Reply from 2607:f8b0:400b:807::2004: time=29ms
Reply from 2607:f8b0:400b:807::2004: time=20ms
Reply from 2607:f8b0:400b:807::2004: time=52ms
Reply from 2607:f8b0:400b:807::2004: time=17ms
Reply from 2607:f8b0:400b:807::2004: time=21ms
Reply from 2607:f8b0:400b:807::2004: time=100ms
Reply from 2607:f8b0:400b:807::2004: time=17ms
Reply from 2607:f8b0:400b:807::2004: time=152ms
Reply from 2607:f8b0:400b:807::2004: time=74ms
Reply from 2607:f8b0:400b:807::2004: time=25ms
Reply from 2607:f8b0:400b:807::2004: time=117ms
Reply from 2607:f8b0:400b:807::2004: time=202ms
Reply from 2607:f8b0:400b:807::2004: time=265ms
Reply from 2607:f8b0:400b:807::2004: time=15ms
Reply from 2607:f8b0:400b:807::2004: time=12ms
Reply from 2607:f8b0:400b:807::2004: time=213ms
Reply from 2607:f8b0:400b:807::2004: time=276ms
Reply from 2607:f8b0:400b:807::2004: time=60ms
Reply from 2607:f8b0:400b:807::2004: time=100ms
Reply from 2607:f8b0:400b:807::2004: time=91ms
Reply from 2607:f8b0:400b:807::2004: time=33ms

Ping statistics for 2607:f8b0:400b:807::2004:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 2238ms, Average = 220ms

Tracert (multiple)

tracert www.google.com

Tracing route to www.google.com [2607:f8b0:400b:803::2004]
over a maximum of 30 hops:

1 23 ms 48 ms 24 ms 2607:f798:804:8d::1
2 * 38 ms 410 ms 2607:f798:10:10e5:0:241:5614:3205
3 414 ms 33 ms 31 ms 2607:f798:10:31f:0:2091:4823:3185
4 36 ms 78 ms 67 ms 2607:f798:10:359:0:2091:4823:5210
5 744 ms 39 ms 52 ms 2607:f798:14:83::2
6 1120 ms 19 ms 20 ms 2001:4860:0:17::1
7 26 ms 203 ms 923 ms 2001:4860:0:1::1fb9
8 21 ms 23 ms 290 ms yyz12s08-in-x04.1e100.net [2607:f8b0:400b:803::2004]

Trace complete.

tracert www.google.com

Tracing route to www.google.com [2607:f8b0:400b:803::2004]
over a maximum of 30 hops:

1 373 ms 50 ms 17 ms 2607:f798:804:8d::1
2 * 328 ms * 2607:f798:10:10e5:0:241:5614:3205
3 19 ms 13 ms 210 ms 2607:f798:10:31f:0:2091:4823:3185
4 396 ms 44 ms 16 ms 2607:f798:10:359:0:2091:4823:5210
5 15 ms 24 ms 50 ms 2607:f798:14:83::2
6 442 ms 15 ms 110 ms 2001:4860:0:17::1
7 83 ms 61 ms 22 ms 2001:4860:0:1::1fb9
8 93 ms 24 ms 59 ms yyz12s08-in-x04.1e100.net [2607:f8b0:400b:803::2004]

Trace complete.

tracert www.google.com

Tracing route to www.google.com [2607:f8b0:400b:803::2004]
over a maximum of 30 hops:

1 34 ms 72 ms 31 ms 2607:f798:804:8d::1
2 * 341 ms 21 ms 2607:f798:10:10e5:0:241:5614:3205
3 24 ms 20 ms 19 ms 2607:f798:10:31f:0:2091:4823:3185
4 161 ms 23 ms 18 ms 2607:f798:10:359:0:2091:4823:5210
5 54 ms 50 ms 984 ms 2607:f798:14:83::2
6 55 ms 25 ms 14 ms 2001:4860:0:17::1
7 24 ms 30 ms 45 ms 2001:4860:0:1::1fb9
8 17 ms 44 ms 20 ms yyz12s08-in-x04.1e100.net [2607:f8b0:400b:803::2004]

TraceRT when internet is behaving properly

tracert www.google.com

Tracing route to www.google.com [2607:f8b0:400b:804::2004]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 2607:fea8:4b63:2b4b::1
2 18 ms 13 ms 16 ms 2607:f798:804:8d::1
3 15 ms 11 ms 13 ms 2607:f798:10:10e4:0:241:5614:3201
4 12 ms 14 ms 13 ms 2607:f798:10:ea29:0:2091:4823:8206
5 13 ms 29 ms 12 ms 2607:f798:10:35a:0:2091:4823:5214
6 13 ms 12 ms 13 ms 2607:f798:14:83::2
7 19 ms 20 ms 21 ms 2001:4860:0:11d6::1
8 14 ms 17 ms 12 ms 2001:4860:0:1::5c83
9 13 ms 15 ms 14 ms yyz10s20-in-x04.1e100.net [2607:f8b0:400b:804::2004]

Ping test when internet is behaving more normally (still has some ping spikes)

Pinging www.google.com [2607:f8b0:400b:804::2004] with 32 bytes of data:
Reply from 2607:f8b0:400b:804::2004: time=14ms
Reply from 2607:f8b0:400b:804::2004: time=19ms
Reply from 2607:f8b0:400b:804::2004: time=17ms
Reply from 2607:f8b0:400b:804::2004: time=22ms
Reply from 2607:f8b0:400b:804::2004: time=21ms
Reply from 2607:f8b0:400b:804::2004: time=18ms
Reply from 2607:f8b0:400b:804::2004: time=55ms
Reply from 2607:f8b0:400b:804::2004: time=19ms
Reply from 2607:f8b0:400b:804::2004: time=14ms
Reply from 2607:f8b0:400b:804::2004: time=15ms
Reply from 2607:f8b0:400b:804::2004: time=14ms
Reply from 2607:f8b0:400b:804::2004: time=14ms
Reply from 2607:f8b0:400b:804::2004: time=15ms
Reply from 2607:f8b0:400b:804::2004: time=15ms
Reply from 2607:f8b0:400b:804::2004: time=15ms
Reply from 2607:f8b0:400b:804::2004: time=21ms
Reply from 2607:f8b0:400b:804::2004: time=12ms
Reply from 2607:f8b0:400b:804::2004: time=12ms
Reply from 2607:f8b0:400b:804::2004: time=28ms
Reply from 2607:f8b0:400b:804::2004: time=29ms
Reply from 2607:f8b0:400b:804::2004: time=22ms
Reply from 2607:f8b0:400b:804::2004: time=14ms
Reply from 2607:f8b0:400b:804::2004: time=20ms
Reply from 2607:f8b0:400b:804::2004: time=16ms
Reply from 2607:f8b0:400b:804::2004: time=42ms
Reply from 2607:f8b0:400b:804::2004: time=21ms
Reply from 2607:f8b0:400b:804::2004: time=45ms
Reply from 2607:f8b0:400b:804::2004: time=31ms
Reply from 2607:f8b0:400b:804::2004: time=71ms
Reply from 2607:f8b0:400b:804::2004: time=63ms
Reply from 2607:f8b0:400b:804::2004: time=21ms
Reply from 2607:f8b0:400b:804::2004: time=55ms
Reply from 2607:f8b0:400b:804::2004: time=14ms
Reply from 2607:f8b0:400b:804::2004: time=83ms
Reply from 2607:f8b0:400b:804::2004: time=24ms
Reply from 2607:f8b0:400b:804::2004: time=118ms
Reply from 2607:f8b0:400b:804::2004: time=64ms
Reply from 2607:f8b0:400b:804::2004: time=93ms
Reply from 2607:f8b0:400b:804::2004: time=17ms
Reply from 2607:f8b0:400b:804::2004: time=32ms
Reply from 2607:f8b0:400b:804::2004: time=13ms
Reply from 2607:f8b0:400b:804::2004: time=73ms
Reply from 2607:f8b0:400b:804::2004: time=72ms
Reply from 2607:f8b0:400b:804::2004: time=13ms
Reply from 2607:f8b0:400b:804::2004: time=110ms
Reply from 2607:f8b0:400b:804::2004: time=22ms
Reply from 2607:f8b0:400b:804::2004: time=30ms
Reply from 2607:f8b0:400b:804::2004: time=25ms
Reply from 2607:f8b0:400b:804::2004: time=15ms
Reply from 2607:f8b0:400b:804::2004: time=36ms

Ping statistics for 2607:f8b0:400b:804::2004:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 118ms, Average = 33ms

Modem info

Model:CGM4331COM

Vendor:Technicolor

Hardware Revision:2.0

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

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

350000000

44.3 dB

42.0 dB

43.4 dB

43.5 dB

43.8 dB

44.1 dB

44.0 dB

44.1 dB

43.9 dB

43.6 dB

43.4 dB

43.3 dB

44.4 dB

44.3 dB

44.1 dB

44.3 dB

44.4 dB

44.4 dB

44.1 dB

42.7 dB

44.2 dB

44.2 dB

44.3 dB

44.2 dB

44.2 dB

44.2 dB

44.6 dB

44.6 dB

44.1 dB

43.8 dB

44.2 dB

43.7 dB

42.5 dB

5.5 dBmV

0.6 dBmV

5.2 dBmV

4.9 dBmV

5.0 dBmV

4.8 dBmV

4.7 dBmV

4.9 dBmV

4.7 dBmV

4.3 dBmV

4.1 dBmV

5.7 dBmV

5.5 dBmV

5.4 dBmV

5.2 dBmV

5.6 dBmV

5.9 dBmV

5.7 dBmV

5.4 dBmV

5.6 dBmV

5.6 dBmV

5.8 dBmV

6.0 dBmV

5.7 dBmV

5.9 dBmV

6.2 dBmV

6.6 dBmV

6.8 dBmV

6.8 dBmV

6.0 dBmV

6.5 dBmV

5.6 dBmV

1.1 dBmV

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

IndexLock StatusFrequencySymbol RatePower LevelModulationChannel Type

Upstream	Channel Bonding Value
1	2	3	4
Locked	Locked	Locked	Locked
21 MHz	25 MHz	32 MHz	38 MHz
2560	5120	5120	5120
37.8 dBmV	40.8 dBmV	40.5 dBmV	39.0 dBmV
QAM	QAM	QAM	QAM
TDMA_AND_ATDMA	ATDMA	ATDMA	ATDMA

IndexUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords

CM Error Codewords
1	2	3	4	5	6	7	8	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
2739690819	1908434154	1906207207	1899166031	1907537089	1911333974	1911358426	1911568713	1910169046	1909388512	1910289303	1910316671	1925769145	1923129759	1910330774	1931550076	1914086747	1931019499	1915697681	1933252212	1915775189	1912030603	1912028735	1912012938	1912024738	1905217364	1916734728	1915247539	1913351573	1913304657	1913407791	1913315878	2739690819
3628844802	1369	997	884	1038	1548	1699	1442	1207	1111	1217	2072	2792023	3268412	1137	2547	2905	11427	27622	10805	18056	3285	3228	3347	3157	1214	199617	1726702	3064	1970	1713	5922	3628844802
1887765	4507	3611	3120	3993	5022	5377	4834	4591	4084	4552	8370	2993658	3682597	4645	9530	7146	26697	69111	29129	55243	6825	7459	7089	6301	4604	86170	2004516	10638	6441	7455	12716	1887765

[rwestlake]

results from today:

tracert www.google.com

Tracing route to www.google.com [2607:f8b0:400b:803::2004]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 2607:fea8:4b63:2b4b::1
2 1174 ms 31 ms 26 ms 2607:f798:804:8d::1
3 1007 ms 13 ms 22 ms 2607:f798:10:10e5:0:241:5614:3205
4 17 ms 17 ms 14 ms 2607:f798:10:ea2a:0:2091:4823:8210
5 499 ms 392 ms 48 ms 2607:f798:10:359:0:2091:4823:5210
6 1717 ms 37 ms 584 ms 2607:f798:14:83::2
7 56 ms 16 ms 144 ms 2001:4860:0:17::1
8 334 ms 68 ms 22 ms 2001:4860:0:1::1fb9
9 2065 ms 27 ms 86 ms yyz12s08-in-x04.1e100.net [2607:f8b0:400b:803::2004]

C:\Users\ryanw>ping www.google.com -n 20

Pinging www.google.com [2607:f8b0:400b:803::2004] with 32 bytes of data:
Reply from 2607:f8b0:400b:803::2004: time=184ms
Reply from 2607:f8b0:400b:803::2004: time=36ms
Reply from 2607:f8b0:400b:803::2004: time=27ms
Reply from 2607:f8b0:400b:803::2004: time=295ms
Reply from 2607:f8b0:400b:803::2004: time=82ms
Reply from 2607:f8b0:400b:803::2004: time=9ms
Reply from 2607:f8b0:400b:803::2004: time=186ms
Reply from 2607:f8b0:400b:803::2004: time=20ms
Reply from 2607:f8b0:400b:803::2004: time=18ms
Reply from 2607:f8b0:400b:803::2004: time=19ms
Reply from 2607:f8b0:400b:803::2004: time=17ms
Reply from 2607:f8b0:400b:803::2004: time=233ms
Reply from 2607:f8b0:400b:803::2004: time=24ms
Reply from 2607:f8b0:400b:803::2004: time=736ms
Reply from 2607:f8b0:400b:803::2004: time=249ms
Reply from 2607:f8b0:400b:803::2004: time=21ms
Reply from 2607:f8b0:400b:803::2004: time=923ms
Reply from 2607:f8b0:400b:803::2004: time=49ms
Reply from 2607:f8b0:400b:803::2004: time=1215ms
Reply from 2607:f8b0:400b:803::2004: time=422ms

Ping statistics for 2607:f8b0:400b:803::2004:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 1215ms, Average = 238ms

[RogersCorey]

Greetings @rwestlake!

My name is Corey.

Looking at these test results, even if you're not getting any packet loss, your average ping times are exceeding 100ms which is well above an acceptable threshold for any real time applications where ping times are relevant. Gaming would absolutely be noticeably impacted by these kinds of ping times.

I'm not seeing any real difference between a direct connection or otherwise, so it's safe to say the issue here isn't WiFi related.

We'd be happy to take a closer look to see what is going on! I'd like to run some additional tests from my end. Feel free to send a private message to @CommunityHelps so we can assist you further. For more information on how our Private Messaging system works, you can find out more here.  

[rwestlake]

HI Corey! Sounds good, I'll message you.

[rwestlake]

Just to follow up for those impacted similarly by something like this, this is a confirmed known issue for Rogers on their parent node, that they have given an indefinite ETA for resolving and per the feedback I've received is within their T&C of acceptable service, so no prioritization will be taken to resolve it.  Keep this in mind when deciding between your options.  This service above, is considered acceptable and not a priority to resolve.

[rwestlake]

Since I wrote the above post, my internet has gone entirely down and not come back up.

[rwestlake]

Still dealing with the same issues had pings as high as 2200 ms tonight:

Ping
#1 33.7 ms
#2 20.7 ms
#3 547.6 ms
#4 190.5 ms
#5 179 ms
#6 18.6 ms
#7 37.3 ms
#8 23.4 ms
#9 22.3 ms
#10 22.7 ms
#11 144 ms
#12 22.5 ms
#13 43.5 ms
#14 2277.1 ms
#15 54.8 ms
#16 21.1 ms
#17 1012.6 ms
#18 17.7 ms
#19 16.5 ms
#20 26.3 ms

[-G-]

---

@rwestlake wrote:

Still dealing with the same issues had pings as high as 2200 ms tonight:

---

FYI, I ran an IPv4 and IPv6 ping test earlier this evening, shortly after your post:

--- 8.8.8.8 ping statistics ---
1000 packets transmitted, 999 packets received, 0.1% packet loss
round-trip min/avg/max/stddev = 13.148/21.582/42.544/2.438 ms

--- 2607:f8b0:400b:803::2004 ping6 statistics ---
1000 packets transmitted, 1000 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 18.445/30.096/48.555/3.181 ms

I've seen better ping RTTs, but my results are great compared to yours.

My neighbourhood got migrated to a new node just over a month ago, so my routing path may be different than yours.  Your latency issues could also be caused by something local to you on the network path.

[rwestlake]

Just in case anyone is looking at this, Rogers has stopped replying to my feedback about the issue still being present and is ignoring following up on the issue at this point.  Here's my connection 05/26/23 (Friday night) at 8 pm: 

ping -n 50 www.google.com

Pinging www.google.com [2607:f8b0:400b:803::2004] with 32 bytes of data:
Reply from 2607:f8b0:400b:803::2004: time=43ms
Reply from 2607:f8b0:400b:803::2004: time=125ms
Reply from 2607:f8b0:400b:803::2004: time=415ms
Reply from 2607:f8b0:400b:803::2004: time=217ms
Reply from 2607:f8b0:400b:803::2004: time=25ms
Reply from 2607:f8b0:400b:803::2004: time=148ms
Reply from 2607:f8b0:400b:803::2004: time=144ms
Reply from 2607:f8b0:400b:803::2004: time=405ms
Reply from 2607:f8b0:400b:803::2004: time=290ms
Reply from 2607:f8b0:400b:803::2004: time=581ms
Reply from 2607:f8b0:400b:803::2004: time=29ms
Reply from 2607:f8b0:400b:803::2004: time=227ms
Reply from 2607:f8b0:400b:803::2004: time=515ms
Reply from 2607:f8b0:400b:803::2004: time=19ms
Reply from 2607:f8b0:400b:803::2004: time=22ms
Reply from 2607:f8b0:400b:803::2004: time=75ms
Reply from 2607:f8b0:400b:803::2004: time=27ms
Reply from 2607:f8b0:400b:803::2004: time=20ms
Reply from 2607:f8b0:400b:803::2004: time=31ms
Reply from 2607:f8b0:400b:803::2004: time=20ms
Reply from 2607:f8b0:400b:803::2004: time=34ms
Reply from 2607:f8b0:400b:803::2004: time=67ms
Reply from 2607:f8b0:400b:803::2004: time=112ms
Reply from 2607:f8b0:400b:803::2004: time=32ms
Reply from 2607:f8b0:400b:803::2004: time=91ms
Reply from 2607:f8b0:400b:803::2004: time=121ms
Reply from 2607:f8b0:400b:803::2004: time=70ms
Reply from 2607:f8b0:400b:803::2004: time=73ms
Reply from 2607:f8b0:400b:803::2004: time=279ms
Reply from 2607:f8b0:400b:803::2004: time=170ms
Reply from 2607:f8b0:400b:803::2004: time=122ms
Reply from 2607:f8b0:400b:803::2004: time=97ms
Reply from 2607:f8b0:400b:803::2004: time=89ms
Reply from 2607:f8b0:400b:803::2004: time=85ms
Reply from 2607:f8b0:400b:803::2004: time=634ms
Reply from 2607:f8b0:400b:803::2004: time=17ms
Reply from 2607:f8b0:400b:803::2004: time=25ms
Reply from 2607:f8b0:400b:803::2004: time=12ms
Reply from 2607:f8b0:400b:803::2004: time=26ms
Reply from 2607:f8b0:400b:803::2004: time=22ms
Reply from 2607:f8b0:400b:803::2004: time=17ms
Reply from 2607:f8b0:400b:803::2004: time=21ms
Reply from 2607:f8b0:400b:803::2004: time=36ms
Reply from 2607:f8b0:400b:803::2004: time=21ms
Reply from 2607:f8b0:400b:803::2004: time=17ms
Reply from 2607:f8b0:400b:803::2004: time=26ms
Reply from 2607:f8b0:400b:803::2004: time=16ms
Reply from 2607:f8b0:400b:803::2004: time=33ms
Reply from 2607:f8b0:400b:803::2004: time=13ms
Reply from 2607:f8b0:400b:803::2004: time=69ms

Ping statistics for 2607:f8b0:400b:803::2004:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 634ms, Average = 116ms

[rwestlake]

I have been given feedback previously to this that the node in my area is known to be congested and there is no ETA on resolution for it.  I believe with population condensing in the GTA Rogers has deemed this level of service to be acceptable.

[RogersCorey]

Hello @rwestlake!

I am sorry that we do not yet have a firm ETA for you but we absolutely do not consider this kind of situation to be acceptable, thus why we have targeted your node for an uplift.

To provide some further insight, it typically takes 6-8 weeks for this kind of work to be done once we begin.

Regards,

RogersCorey

[rwestlake]

Sorry I assumed that @RogersCorey ,  just to clarify the only reason I did was because all the people who had reached out to me about it had stopped, and when I reached out to them to find out what was going on my voicemails and emails were not returned anymore unfortunately.  I do appreciate you giving me this update, even if it is not unquantifiable as it's a lot better than silence!  Totally understand that when its scheduled it takes time to do the work as well :). I'm mainly concerned about the lack of communication combined with no ETA seeming indefinite, especially considering I raised the issue initially last August.

[RogersCorey]

How long has it been since you last checked with us for an ETA? I could check to see if there's a target date available now for you.

Feel free to send a private message to @CommunityHelps so we can assist you further. For more information on how our Private Messaging system works, you can find out more here.  

Regards,

RogersCorey