cancel
Showing results for 
Search instead for 
Did you mean: 

Rogers Gaming & Streaming Lab

RogersDarrell
Community Manager (Retired)
Community Manager (Retired)

 

  Streaming_Gaming_Lab.png

 

Hi Community, 

 

Welcome to the Rogers Community Forums Gaming & Streaming Lab!

We will use this thread as a central point to discuss upstream issues affecting your online gaming and streaming experience on the Rogers network.  

 

This Lab will work to consolidate all upstream specific issues into one place. By doing so we can work together to hone in on any issues specific to the Rogers network that may be impacting your gaming or streaming experience up to, but not limited to, dropped frames, stutter, increased latency and intermittent voice; all while streaming on Twitch, YouTube Gaming, Steam, etc. 

 

Our own Community Forums Specialist @RogersAndy , is an avid gamer with streaming experience on all major platforms in addition to many years of experience testing and troubleshooting with all technical lines of business. As part of our service resolution tracking, we recommend avoiding contact with alternative lines of support for this issue specifically. 

 

To take part in this lab, you must meet the following requirements. 

  1. All services work fine outside of streaming/gaming.
  2. Your modem’s RF levels are within spec. 
  3. You have had multiple service calls and/or tickets within 6 months regarding your game streaming issues. 
  4. Issues must be present with a wired connection to the modem. NO connected 3rd party equipment.

*If you do not meet the above requirements, your post(s) may be merged to a more accurate thread.

 

What troubleshooting will we need from you? 

  1. A screenshot of your Upstream and Downstream levels found on the status page when you log into your modem. 
  2. A current ping test result from command prompt to google.com 
  3. A current traceroute from command prompt to the streaming/gaming service you’re connecting to. (their support can provide you with that IP if necessary). 

 

*Always remember when posting an image of network testing results to block out/remove your personal IP address.

*Images will show in your post after they have been approved by our Moderator team. Don't worry when they don't show up right away.

 

We also recommend all of our gamers to sign up for the Rogers WiFi Modem Firmware Trial. Feedback from the Community has resulted in great improvements to the overall internet experience, specifically in regards to ping and latency on the Rogers network. For details of this program, please see this thread. 

 

To learn more about Rogers and online gaming, check out our gaming page at www.rogers.com/gaming 

 

Thank you for your continued feedback and support. 

 

 

 

281 REPLIES 281

Re: Rogers Gaming & Streaming Lab

Hey @angral!

 

Welcome to the Lab :). 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
 

Re: Rogers Gaming & Streaming Lab

angral
I Plan to Stick Around

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.

Re: Rogers Gaming & Streaming Lab

RogersAndy
Retired Moderator
Retired Moderator

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

Re: Rogers Gaming & Streaming Lab

Marcoux1
I Plan to Stick Around

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

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

Re: Rogers Gaming & Streaming Lab

angral
I Plan to Stick Around

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.

Re: Rogers Gaming & Streaming Lab

RogersAndy
Retired Moderator
Retired Moderator

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 :). Looking forward to seeing some improvement for you soon.

 

@RogersAndy

Re: Rogers Gaming & Streaming Lab

Marcoux1
I Plan to Stick Around

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


 

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 :). 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

Re: Rogers Gaming & Streaming Lab

Marcoux1
I Plan to Stick Around

I have gathered 4 traceroutes to different Rocket League servers, advised by Rocket League staff. I did a 15 minute traceroute.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                         router.asus.com -    0 |  952 |  952 |    0 |    0 |    6 |    0 |
|xxxxxxxxxxxx.cpe.net.cable.rogers.com -    1 |  940 |  937 |    5 |   16 |  105 |   10 |
|     8080-dgw01.ajax.rmgt.net.rogers.com -    1 |  944 |  942 |    5 |   12 |   86 |    6 |
|                          209.148.236.61 -    1 |  948 |  947 |    6 |   13 |   98 |   19 |
|    9403-cgw01.bloor.rmgt.net.rogers.com -    1 |  944 |  942 |    4 |   14 |  105 |   12 |
|                         209.148.229.226 -    1 |  948 |  947 |   13 |   23 |  210 |   20 |
|                          209.148.231.58 -    1 |  944 |  942 |   22 |   30 |  133 |   25 |
|                      Request timed out. -  100 |  191 |    0 |    0 |    0 |    0 |    0 |
|                      Request timed out. -  100 |  191 |    0 |    0 |    0 |    0 |    0 |
|                      Request timed out. -  100 |  191 |    0 |    0 |    0 |    0 |    0 |
|                      Request timed out. -  100 |  191 |    0 |    0 |    0 |    0 |    0 |
|                   45.63.12.57.vultr.com -    1 |  944 |  942 |   21 |   29 |   64 |   47 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                         router.asus.com -    0 |  912 |  912 |    0 |    0 |    9 |    0 |
|xxxxxxxxxxxx.cpe.net.cable.rogers.com -    0 |  912 |  912 |    6 |   20 |  132 |   13 |
|     8080-dgw02.ajax.rmgt.net.rogers.com -    0 |  912 |  912 |    3 |   16 |  113 |    7 |
|     3000-dgw01.ajax.rmgt.net.rogers.com -    0 |  912 |  912 |    4 |   16 |   91 |   10 |
|                          209.148.236.61 -    0 |  912 |  912 |    7 |   17 |  118 |   13 |
|                         209.148.235.105 -    0 |  912 |  912 |   15 |   29 |  136 |   27 |
|    be812.ccr41.ord03.atlas.cogentco.com -    1 |  908 |  907 |   15 |   28 |  148 |   29 |
|   be2766.ccr42.ord01.atlas.cogentco.com -    1 |  908 |  907 |   17 |   29 |  118 |   27 |
|   be2736.ccr42.atl01.atlas.cogentco.com -    0 |  912 |  912 |   33 |   45 |  145 |   40 |
|te0-3-1-5.rcr51.b009789-2.atl01.atlas.cogentco.com -    0 |  912 |  912 |   33 |   46 |  125 |   47 |
|                            38.140.47.10 -    0 |  912 |  912 |   41 |   54 |  146 |  102 |
|                      Request timed out. -  100 |  182 |    0 |    0 |    0 |    0 |    0 |
|                      Request timed out. -  100 |  182 |    0 |    0 |    0 |    0 |    0 |
|               104.156.255.133.vultr.com -    0 |  911 |  911 |   36 |   48 |  181 |   37 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)

 

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                         router.asus.com -    0 |  911 |  911 |    0 |    0 |    5 |    0 |
|xxxxxxxxxxxxx.cpe.net.cable.rogers.com -    0 |  911 |  911 |    4 |   20 |  175 |   20 |
|     8080-dgw02.ajax.rmgt.net.rogers.com -    0 |  911 |  911 |    7 |   16 |  136 |   22 |
|9001-cgw01.mtnk.asr9k.rmgt.net.rogers.com -    0 |  911 |  911 |    6 |   16 |  111 |   11 |
|                          209.148.233.94 -    0 |  911 |  911 |    6 |   18 |  129 |   12 |
|                           209.148.237.5 -    0 |  911 |  911 |   22 |   33 |  144 |   26 |
|             10ge.eqx-ashburn.misi3d.com -    0 |  911 |  911 |   21 |   35 |  126 |   35 |
|                       hosted-by.i3d.net -    0 |  911 |  911 |   20 |   31 |  132 |   30 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)

 

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                         router.asus.com -    0 |  914 |  914 |    0 |    0 |    5 |    0 |
|xxxxxxxxxxxx.cpe.net.cable.rogers.com -    0 |  914 |  914 |    5 |   17 |  118 |   17 |
|     8080-dgw02.ajax.rmgt.net.rogers.com -    0 |  914 |  914 |    4 |   13 |   98 |   19 |
|     3000-dgw01.ajax.rmgt.net.rogers.com -    0 |  914 |  914 |    4 |   15 |  191 |   26 |
|       9001-cgw01.ym.rmgt.net.rogers.com -    0 |  913 |  913 |    5 |   15 |  163 |   12 |
|                         209.148.230.134 -    0 |  913 |  913 |   29 |   39 |  155 |   36 |
|            equinix-ix.ord1.us.voxel.net -    0 |  913 |  913 |   15 |   26 |  141 |   24 |
|                   bbr2.ae7.chg.pnap.net -    0 |  913 |  913 |   29 |   39 |  175 |   46 |
|bbr1.xe-4-0-0.inapbb-chg-nym-12.nym007.pnap.net -    0 |  913 |  913 |   31 |   43 |  169 |   41 |
|               tsr1.e6-1.nyj004.pnap.net -    0 |  913 |  913 |   32 |   45 |  147 |   42 |
|        v506.po3.cr2.nyj004.us.voxel.net -    0 |  913 |  913 |   33 |   42 |  130 |   43 |
|                         107.150.147.220 -    0 |  913 |  913 |   28 |   41 |  148 |   38 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)


@RogersAndy wrote:

@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 :). 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


 

***Edited -  Removed MAC Address***

 

Re: Rogers Gaming & Streaming Lab

@Marcoux1

 

Appreciate the data provided! To confirm that the results provided via WinMTR are accurate are you able to reproduce the same results using command prompt?

 

Thanks!

 

@RogersAndy

Re: Rogers Gaming & Streaming Lab

Marcoux1
I Plan to Stick Around

Yes the results are accurate. It was just the software that Rocket League support suggested to use.

Re: Rogers Gaming & Streaming Lab

Marcoux1
I Plan to Stick Around

Although I can not have the traceroute repeat with the command prompt so it doesn't necessarily catch ping spikes

  1    <1 ms    <1 ms    <1 ms  router.asus.com [192.168.1.1]
  2    13 ms    11 ms    12 ms  CPE0xxxxxxx -CM00fcxxxxxx.cpe.net.cable.rogers.com [99.xx.xx.x] - Edited - Keep personal info private.  - RogersZia
  3    12 ms    12 ms    14 ms  8080-dgw01.ajax.rmgt.net.rogers.com [67.231.221.233]
  4     8 ms    11 ms    12 ms  209.148.236.61
  5    17 ms    26 ms    16 ms  9403-cgw01.bloor.rmgt.net.rogers.com [209.148.235.229]
  6    24 ms    35 ms    22 ms  209.148.229.226
  7    29 ms    27 ms    21 ms  209.148.231.58
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *

Re: Rogers Gaming & Streaming Lab

Marcoux1
I Plan to Stick Around

What can be done about what is happening?

 

Re: Rogers Gaming & Streaming Lab

Hey @Marcoux1!

 

So what we'll be doing on our end is compiling a list of customer's impacted by issues streaming and or gaming. Within the list we'll be directing focus toward traceroute results that indicate any level of intermittent latency outside of the Rogers network. Assuming all other potential causes of issues within our network have been addressed or ruled out, with this information my hope is that we can determine some level of consistency so that the underlying cause can be targeted for resolution.

 

That said this will take some time, but I assure everyone who's a part of this lab that although progress may be a slow process, it's one I'm dedicated to :).

 

@RogersAndy

Re: Rogers Gaming & Streaming Lab

angral
I Plan to Stick Around

Hi @RogersAndy,

 

Any news? I'm still experiencing lag spike issues. Here's my latest WinMTR if it helps. Looks similar to the ones I took last week:

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                                CODA4582 -  100 | 1046 |    7 |    1 |    1 |    1 |    1 |

|                             xx.xxx.xx.x -    0 | 5195 | 5195 |    2 |   11 |  215 |   11 |

|   8076-dgw01.wlfdle.rmgt.net.rogers.com -    0 | 5195 | 5195 |    2 |    7 |   36 |    8 |

|                         209.148.235.109 -    0 | 5195 | 5195 |    2 |    7 |   48 |    7 |

|                          209.148.230.26 -    0 | 5195 | 5195 |   18 |   23 |  226 |   25 |

|                   eqix-dc2.blizzard.com -    0 | 5195 | 5195 |   18 |   23 |  226 |   23 |

|              ae1-br01-eqdc2.as57976.net -    0 | 5195 | 5195 |   78 |   86 |  305 |   84 |

|         et-0-0-2-br01-eqch2.as57976.net -    1 | 5110 | 5094 |   78 |  101 | 4309 |   82 |

|                          137.221.65.132 -    1 | 5110 | 5095 |   78 |   97 | 4808 |   82 |

|         et-0-0-2-br01-eqla1.as57976.net -    1 | 5049 | 5023 |   87 |  111 | 4564 |  108 |

|              be1-pe02-eqla1.as57976.net -    0 | 5195 | 5195 |   78 |   83 |  293 |   82 |

|        lax-eqla1-ia-bons-03.as57976.net -    0 | 5195 | 5195 |   78 |   83 |  116 |   86 |

|                           24.105.30.129 -    1 | 5140 | 5126 |   78 |   82 |  116 |   84 |

|________________________________________________|______|______|______|______|______|______|

Re: Rogers Gaming & Streaming Lab

RogersAndy
Retired Moderator
Retired Moderator

Hey @angral!

 

Thanks so much for providing an update! I've noted the information and added it to your file. I'll be running some tests this evening to replicate this from your modem. Looking forward to getting to the bottom of this for you. 

 

@RogersAndy

Re: Rogers Gaming & Streaming Lab

angral
I Plan to Stick Around

Here's another WinMTR from an hour ago if it helps:

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                                CODA4582 -  100 |  451 |    4 |    1 |    1 |    2 |    1 |

|                             xx.xxx.xx.x -    0 | 2236 | 2236 |    3 |   10 |  249 |    8 |

|   8076-dgw01.wlfdle.rmgt.net.rogers.com -    0 | 2236 | 2236 |    3 |    7 |  244 |   12 |

|                         209.148.235.109 -    0 | 2236 | 2236 |    2 |    7 |  242 |    8 |

|                          209.148.230.26 -    0 | 2236 | 2236 |   18 |   23 |   67 |   24 |

|                   eqix-dc2.blizzard.com -    0 | 2236 | 2236 |   18 |   23 |  262 |   24 |

|              ae1-br01-eqdc2.as57976.net -    0 | 2236 | 2236 |   78 |   85 |  326 |   85 |

|         et-0-0-2-br01-eqch2.as57976.net -    1 | 2181 | 2171 |   78 |  102 | 4144 |   87 |

|                          137.221.65.132 -    1 | 2202 | 2197 |   78 |  104 | 4634 |   85 |

|         et-0-0-2-br01-eqla1.as57976.net -    1 | 2167 | 2157 |   88 |  121 | 4179 |   93 |

|              be1-pe02-eqla1.as57976.net -    0 | 2236 | 2236 |   78 |   82 |   98 |   85 |

|        lax-eqla1-ia-bons-03.as57976.net -    0 | 2236 | 2236 |   79 |   83 |   98 |   83 |

|                           24.105.30.129 -    1 | 2213 | 2207 |   78 |   83 |   99 |   83 |

|________________________________________________|______|______|______|______|______|______|

Re: Rogers Gaming & Streaming Lab

Marcoux1
I Plan to Stick Around

@RogersAndy wrote:

Hey @Marcoux1!

 

So what we'll be doing on our end is compiling a list of customer's impacted by issues streaming and or gaming. Within the list we'll be directing focus toward traceroute results that indicate any level of intermittent latency outside of the Rogers network. Assuming all other potential causes of issues within our network have been addressed or ruled out, with this information my hope is that we can determine some level of consistency so that the underlying cause can be targeted for resolution.

 

That said this will take some time, but I assure everyone who's a part of this lab that although progress may be a slow process, it's one I'm dedicated to :).

 

@RogersAndy

 

I just figured out that the recent fps drops I have been getting are caused by my network, I had bought new ram, new storage new cooling and everything thinking that the stutters I was receiving was caused by my PC. When I was playing with in game settings I noticed that when I turned all my internet settings to low my fps stutters had stopped. Although the network lag remains to keep the game unplayable. How slow of a process will this be? The lag I am getting has been driving me crazy for almost a year now and has only gotten worse from the beginning. 


 

Re: Rogers Gaming & Streaming Lab

Like..

 

I appreciate all the effort you've put in Andy and it's ultimately not your fault, but "a slow process" and no ETA isn't really acceptable when my main source of income is being impacted at random on a daily basis.

 

I'm gonna have to switch providers. Thanks for all your work so far.

Re: Rogers Gaming & Streaming Lab

Hey @Marcoux1!

 

Though I don't have an ETR at this time as this is an ongoing process, the more traceroute information we have pinpointing the issue the better. There's some additional tests I'd like to run on your network, can you send us a PM @CommunityHelps? For information on our PM system you can check out our Blog. 🙂

 

@aeroteq!

My pleasure, we'll be sad to see you go :(. If there's anything else you need please let me know.

 

 

@RogersAndy

We Want Your Opinion
Would you be interested in becoming a Community Testing Lab member?