Rogers Gaming & Streaming Lab

Need Help?

That's what we're here for! The goal of the Rogers Community is to help you find answers on everything Rogers. Can't find what you're looking for? Just ask!
cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
I Plan to Stick Around
Posts: 8

Re: Rogers Gaming & Streaming Lab

Hi, I switched from 150u ignite to gigabit and have started experiencing lag spikes and rubber banding in video games. Please help!

 

Games: World of Warcraft, Heroes of the Storm

Area: Mississauga, Ontario

Modem: CODA-4582

 

1. Upstream/Downstream

Downstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB)
1 597000000 256QAM 0.000 8 37.636
2 849000000 256QAM -3.100 2 35.084
3 855000000 256QAM -3.300 3 35.780
4 861000000 256QAM -3.400 4 35.084
5 579000000 256QAM 0.400 5 37.636
6 585000000 256QAM 0.200 6 37.636
7 591000000 256QAM 0.100 7 37.356
8 279000000 256QAM 0.600 1 37.636
9 603000000 256QAM -0.100 9 37.636
10 609000000 256QAM 0.100 10 37.356
11 615000000 256QAM 0.300 11 37.356
12 621000000 256QAM 0.500 12 37.636
13 633000000 256QAM 0.500 13 37.356
14 639000000 256QAM 0.400 14 37.636
15 645000000 256QAM 0.100 15 37.356
16 651000000 256QAM -0.100 16 37.356
17 657000000 256QAM 0.400 17 37.356
18 663000000 256QAM 0.500 18 37.356
19 669000000 256QAM 0.500 19 37.636
20 675000000 256QAM 0.600 20 37.356
21 681000000 256QAM 0.500 21 37.636
22 687000000 256QAM 0.100 22 37.356
23 693000000 256QAM -0.200 23 37.356
24 699000000 256QAM -0.300 24 37.356
25 705000000 256QAM -0.400 25 37.356
26 711000000 256QAM -0.800 26 36.610
27 717000000 256QAM -0.700 27 36.610
28 723000000 256QAM -1.300 28 36.610
29 825000000 256QAM -1.600 29 36.387
30 831000000 256QAM -2.100 30 36.387
31 837000000 256QAM -2.400 31 35.780
32 843000000 256QAM -2.800 32 35.595
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 0.900002
Upstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth
1 13696000 ATDMA - 64QAM 19.500 1 6400000
2 36996000 ATDMA - 64QAM 21.750 4 6400000
3 30596000 ATDMA - 64QAM 21.250 3 6400000
4 23700000 ATDMA - 64QAM 20.750 2 6400000
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. Ping Test to google.com

Pinging google.com [2607:f8b0:400b:802::200e] with 32 bytes of data:
Reply from 2607:f8b0:400b:802::200e: time=10ms
Reply from 2607:f8b0:400b:802::200e: time=8ms
Reply from 2607:f8b0:400b:802::200e: time=7ms
Reply from 2607:f8b0:400b:802::200e: time=8ms
Reply from 2607:f8b0:400b:802::200e: time=7ms
Reply from 2607:f8b0:400b:802::200e: time=7ms
Reply from 2607:f8b0:400b:802::200e: time=9ms
Request timed out.
Reply from 2607:f8b0:400b:802::200e: time=10ms
Reply from 2607:f8b0:400b:802::200e: time=9ms
Reply from 2607:f8b0:400b:802::200e: time=8ms
Reply from 2607:f8b0:400b:802::200e: time=8ms
Reply from 2607:f8b0:400b:802::200e: time=8ms
Reply from 2607:f8b0:400b:802::200e: time=7ms
Reply from 2607:f8b0:400b:802::200e: time=7ms
Reply from 2607:f8b0:400b:802::200e: time=9ms
Request timed out.
Reply from 2607:f8b0:400b:802::200e: time=10ms
Reply from 2607:f8b0:400b:802::200e: time=10ms
Reply from 2607:f8b0:400b:802::200e: time=11ms
Reply from 2607:f8b0:400b:802::200e: time=11ms
Reply from 2607:f8b0:400b:802::200e: time=10ms
Reply from 2607:f8b0:400b:802::200e: time=9ms
Reply from 2607:f8b0:400b:802::200e: time=8ms
Reply from 2607:f8b0:400b:802::200e: time=10ms
Reply from 2607:f8b0:400b:802::200e: time=9ms
Reply from 2607:f8b0:400b:802::200e: time=8ms
Reply from 2607:f8b0:400b:802::200e: time=10ms
Request timed out.
Reply from 2607:f8b0:400b:802::200e: time=12ms

Ping statistics for 2607:f8b0:400b:802::200e:
Packets: Sent = 30, Received = 27, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 12ms, Average = 8ms

3. Traceroute to Heroes of the Storm IP 24.105.30.129 using WinMTR:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| CODA4582 - 
| xx.xxx.xx.x - 0 | 1254 | 1254 | 3 | 10 | 165 | 6 |
| 8076-dgw01.wlfdle.rmgt.net.rogers.com - 0 | 1254 | 1254 | 2 | 7 | 162 | 8 |
| 209.148.235.109 - 0 | 1254 | 1254 | 2 | 7 | 144 | 9 |
| 209.148.230.26 - 0 | 1254 | 1254 | 18 | 23 | 187 | 21 |
| eqix-dc2.blizzard.com - 0 | 1254 | 1254 | 18 | 23 | 65 | 28 |
| ae1-br01-eqdc2.as57976.net - 0 | 1254 | 1254 | 78 | 84 | 261 | 81 |
| et-0-0-2-br01-eqch2.as57976.net - 3 | 1110 | 1081 | 78 | 145 | 4001 | 84 |
| 137.221.65.132 - 2 | 1170 | 1156 | 78 | 132 | 4852 | 82 |
| et-0-0-2-br01-eqla1.as57976.net - 3 | 1124 | 1101 | 88 | 160 | 4700 | 96 |
| be1-pe02-eqla1.as57976.net - 0 | 1254 | 1254 | 78 | 83 | 95 | 83 |
| lax-eqla1-ia-bons-03.as57976.net - 0 | 1254 | 1254 | 79 | 84 | 224 | 84 |
| 24.105.30.129 - 2 | 1203 | 1190 | 78 | 82 | 96 | 84 |
|________________________________________________|______|______|______|______|______|______|

Moderator
Moderator
Posts: 178

Re: Rogers Gaming & Streaming Lab

Hey @angral!

 

Welcome to the Lab Smiley Happy. Heroes of the Storm is a good time, love how teamwork oriented it is. Getting latency issues though can make it rough going.

Ping wise everything looks ok but are you able to provide us with a Ping test and Traceroute result to the Blizzard server you're connecting to? We'll see if there's any visible latency for that server specifically.

 

@Marcoux1

You can log into the modem with http://192.168.0.1
Username: cusadmin
Password: Will be your WiFi password.
Are you able to provide me with a ping test and traceroute to the server you're connecting to?

Thanks everyone!

 

@RogersAndy
 

I Plan to Stick Around
Posts: 8

Re: Rogers Gaming & Streaming Lab

Pinging 24.105.30.129 with 32 bytes of data:
Reply from 24.105.30.129: bytes=32 time=83ms TTL=244
Reply from 24.105.30.129: bytes=32 time=82ms TTL=244
Reply from 24.105.30.129: bytes=32 time=86ms TTL=244
Reply from 24.105.30.129: bytes=32 time=82ms TTL=244
Reply from 24.105.30.129: bytes=32 time=84ms TTL=244
Reply from 24.105.30.129: bytes=32 time=83ms TTL=244
Reply from 24.105.30.129: bytes=32 time=83ms TTL=244
Request timed out.
Reply from 24.105.30.129: bytes=32 time=87ms TTL=244
Reply from 24.105.30.129: bytes=32 time=83ms TTL=244
Reply from 24.105.30.129: bytes=32 time=83ms TTL=244
Reply from 24.105.30.129: bytes=32 time=83ms TTL=244
Reply from 24.105.30.129: bytes=32 time=83ms TTL=244
Reply from 24.105.30.129: bytes=32 time=83ms TTL=244
Reply from 24.105.30.129: bytes=32 time=84ms TTL=244
Reply from 24.105.30.129: bytes=32 time=83ms TTL=244
Reply from 24.105.30.129: bytes=32 time=82ms TTL=244
Reply from 24.105.30.129: bytes=32 time=82ms TTL=244
Reply from 24.105.30.129: bytes=32 time=83ms TTL=244
Reply from 24.105.30.129: bytes=32 time=83ms TTL=244
Reply from 24.105.30.129: bytes=32 time=82ms TTL=244
Reply from 24.105.30.129: bytes=32 time=83ms TTL=244
Reply from 24.105.30.129: bytes=32 time=83ms TTL=244
Request timed out.
Reply from 24.105.30.129: bytes=32 time=85ms TTL=244
Reply from 24.105.30.129: bytes=32 time=84ms TTL=244
Reply from 24.105.30.129: bytes=32 time=85ms TTL=244
Reply from 24.105.30.129: bytes=32 time=85ms TTL=244
Request timed out.
Reply from 24.105.30.129: bytes=32 time=84ms TTL=244

Ping statistics for 24.105.30.129:
Packets: Sent = 30, Received = 27, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 82ms, Maximum = 87ms, Average = 83ms

 

 

 

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 1 ms <1 ms 1 ms CODA4582 [xxx]
2 10 ms 7 ms 9 ms xxx
3 6 ms 9 ms 8 ms 8076-dgw01.wlfdle.rmgt.net.rogers.com [69.63.255.189]
4 7 ms 7 ms 7 ms 209.148.235.109
5 24 ms 23 ms 23 ms 209.148.230.26
6 23 ms 25 ms 23 ms eqix-dc2.blizzard.com [206.126.237.174]
7 89 ms 84 ms 98 ms ae1-br01-eqdc2.as57976.net [137.221.72.33]
8 82 ms 84 ms 84 ms et-0-0-2-br01-eqch2.as57976.net [137.221.65.13]
9 115 ms 84 ms 84 ms 137.221.65.132
10 106 ms 118 ms 93 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
11 83 ms 83 ms 83 ms be1-pe02-eqla1.as57976.net [137.221.68.69]
12 84 ms 84 ms 83 ms lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
13 83 ms 83 ms 82 ms 24.105.30.129

Trace complete.

Moderator
Moderator
Posts: 178

Re: Rogers Gaming & Streaming Lab

Thanks @angral!

 

There is some significant latency occurring on route to that server... I would definitely recommend reaching out to Blizzard support to provide them with those results. As there's no visible latency within the Rogers network and no issue with the route itself. Definitely keep us posted with what they advise though!

 

@RogersAndy

I Plan to Stick Around
Posts: 10

Re: Rogers Gaming & Streaming Lab

https://imgur.com/a/p8zx5pK

It does not let me access that page

I also can not find a public ip address for me to ping or traceroute in Rocket League, but I will connect to google as a placeholder.

I have noticed that I dont have many drops and my download speed is high. I do get much more internet lag at night but still have a high download speed. When I do experience internet lag in games I also start having fps drops in such games. My input buffer is high though ( BUt sometimes drops to 0) and I have some I buf miss. My out bytes arw also sometimes high. Although I was experiencing ping spikes up to 300 last night. I connect to the US-East servers (Which acts as north america)

Tracing route to google.com [2607:f8b0:400b:800::200e]
over a maximum of 30 hops:
  1    21 ms    19 ms    10 ms  2607:f798:804:9::1
  2    11 ms    10 ms    10 ms  2607:f798:10:1455:0:672:3122:1233
  3    10 ms    16 ms     9 ms  2607:f798:10:54:0:690:6324:8217
  4    16 ms     9 ms    13 ms  2607:f798:10:308::1
  5    28 ms    14 ms    42 ms  2001:4860:1:1:0:32c:0:8
  6    16 ms    12 ms    14 ms  2001:4860:0:16::1
  7    14 ms    13 ms    13 ms  2001:4860:0:1::1fb9
  8    11 ms    12 ms    12 ms  yyz12s04-in-x0e.1e100.net [2607:f8b0:400b:800::200e]
Trace complete.
Reply from 2607:f8b0:400b:800::200e: time=96ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=9ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=14ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=14ms
Reply from 2607:f8b0:400b:800::200e: time=17ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=18ms
Reply from 2607:f8b0:400b:800::200e: time=26ms
Reply from 2607:f8b0:400b:800::200e: time=23ms
Reply from 2607:f8b0:400b:800::200e: time=20ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=19ms
Reply from 2607:f8b0:400b:800::200e: time=20ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=10ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=18ms
Reply from 2607:f8b0:400b:800::200e: time=14ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=14ms
Reply from 2607:f8b0:400b:800::200e: time=10ms
Reply from 2607:f8b0:400b:800::200e: time=14ms
Reply from 2607:f8b0:400b:800::200e: time=14ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=10ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=16ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=15ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=18ms
Reply from 2607:f8b0:400b:800::200e: time=15ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=10ms
Reply from 2607:f8b0:400b:800::200e: time=23ms
Reply from 2607:f8b0:400b:800::200e: time=15ms
Reply from 2607:f8b0:400b:800::200e: time=19ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=18ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=9ms
Reply from 2607:f8b0:400b:800::200e: time=31ms
Reply from 2607:f8b0:400b:800::200e: time=8ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=10ms
Reply from 2607:f8b0:400b:800::200e: time=20ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=18ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=16ms
Reply from 2607:f8b0:400b:800::200e: time=16ms
Reply from 2607:f8b0:400b:800::200e: time=14ms
Reply from 2607:f8b0:400b:800::200e: time=14ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=10ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=19ms
Reply from 2607:f8b0:400b:800::200e: time=17ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=10ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=16ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=17ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=19ms
Reply from 2607:f8b0:400b:800::200e: time=18ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=17ms
Reply from 2607:f8b0:400b:800::200e: time=15ms
Reply from 2607:f8b0:400b:800::200e: time=18ms
Reply from 2607:f8b0:400b:800::200e: time=15ms
Reply from 2607:f8b0:400b:800::200e: time=15ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=10ms
Reply from 2607:f8b0:400b:800::200e: time=18ms
Reply from 2607:f8b0:400b:800::200e: time=15ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=78ms
Reply from 2607:f8b0:400b:800::200e: time=18ms
Reply from 2607:f8b0:400b:800::200e: time=24ms
Reply from 2607:f8b0:400b:800::200e: time=10ms
Reply from 2607:f8b0:400b:800::200e: time=28ms
Reply from 2607:f8b0:400b:800::200e: time=9ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=17ms
Reply from 2607:f8b0:400b:800::200e: time=14ms
Reply from 2607:f8b0:400b:800::200e: time=8ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=10ms
Reply from 2607:f8b0:400b:800::200e: time=15ms
Reply from 2607:f8b0:400b:800::200e: time=24ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=17ms
Reply from 2607:f8b0:400b:800::200e: time=10ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=17ms
Reply from 2607:f8b0:400b:800::200e: time=15ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=21ms
Reply from 2607:f8b0:400b:800::200e: time=23ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=26ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=18ms
Reply from 2607:f8b0:400b:800::200e: time=30ms
Reply from 2607:f8b0:400b:800::200e: time=27ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=20ms
Reply from 2607:f8b0:400b:800::200e: time=14ms
Reply from 2607:f8b0:400b:800::200e: time=10ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=32ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=17ms
Reply from 2607:f8b0:400b:800::200e: time=13ms
Reply from 2607:f8b0:400b:800::200e: time=19ms
Reply from 2607:f8b0:400b:800::200e: time=20ms
Reply from 2607:f8b0:400b:800::200e: time=19ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=41ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=11ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Reply from 2607:f8b0:400b:800::200e: time=12ms
Ping statistics for 2607:f8b0:400b:800::200e:
    Packets: Sent = 300, Received = 300, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 8ms, Maximum = 96ms, Average = 14ms
Control-C
Moderator
Moderator
Posts: 178

Re: Rogers Gaming & Streaming Lab

@Marcoux1

 

Thanks so much, there doesn't appear to be any general latency occurring so it's likely specific to the game server you're connecting to. I'd recommend reaching out to their support for assistance in running a traceroute to their closest server to you. Once I have those results though I can assist in identifying where the issue may be.

 

@RogersAndy

I Plan to Stick Around
Posts: 8

Re: Rogers Gaming & Streaming Lab

Hi @RogersAndy ,

 

I reached out to Blizzard, giving them the ping, traceroute, and MTR results I posted. Here's their reply:

 

I was able to look over the MTR test you ran and would agree with Andy from Rogers in the thread you linked. There's some data loss and latency outside of their network. If you look at hop 8 in the test we see 3% data loss and a latency spike up to 4000ms at that point. It seems to affect the points after it as well.

The only hop in this test that Blizzard has access to is the last IP, your destination. And that hop is affected by all the hops before it so we need to look for the first point where an issue appears. Remember that Blizzard is not an ISP so we don't have control over your connection path toward our servers.

These hops in the middle are peering partners that your ISP is using in order to reach our server. I would recommend reaching back out to your ISP and asking them to forward this information to their peering partners. They should be able to have hop 8 investigated as it appears that's where the latency spikes are starting.

Moderator
Moderator
Posts: 178

Re: Rogers Gaming & Streaming Lab

Thanks so much @angral!

 

What I'll do is reach out to some contacts and see what options are available, I'll be able to use the information provided Smiley Happy. Looking forward to seeing some improvement for you soon.

 

@RogersAndy

I Plan to Stick Around
Posts: 10

Re: Rogers Gaming & Streaming Lab

The lag that I do get is not specific to the game. I have latency issues on every game that I play. Even with how excellent google servers I still spiked to over  90 ping at a time of day I lag less. I get many insane spikes at night. Nobody else I play with has spikes in the same lobbies. I will attempt to perform a trace route but it is not a problem with the game servers. I have been dealing with these issues for almost a year now with no help from Rogers but only denial of the issue.


@RogersAndy wrote:

@Marcoux1

 

Thanks so much, there doesn't appear to be any general latency occurring so it's likely specific to the game server you're connecting to. I'd recommend reaching out to their support for assistance in running a traceroute to their closest server to you. Once I have those results though I can assist in identifying where the issue may be.

 

@RogersAndy


 

Moderator
Moderator
Posts: 178

Re: Rogers Gaming & Streaming Lab

@Marcoux1

 

Though I appreciate the level of frustration you've experienced not yet seeing an end to your issues, the creation of this lab was done so that I could address issues with gaming/streaming for anyone much like yourself, in that same boat. I'm definitely not denying an issue, I'm hoping to identify a consistency wherever possible so it can be resolved for as many people as possible Smiley Happy. I'll do everything I can to see an end to it.


This isn't likely an issue with any one particular gaming server no, especially if it's occurring with multiple games, but if there's an issue anywhere along that route, knowledge of that would be paramount to seeing it addressed, if possible. Looking forward to seeing the results of the traceroute, the more information we have the better in this regard. If you're able to provide any additional traceroute information for other games you're seeing issues with that information would be helpful as well!

 

@RogersAndy