Rogers Gaming & Streaming Lab

[mrbray]

Hmm nope, Microsoft Windows Security and that hasn't changed since before the extra latency bumped up when I changed to the new Ignite Wifi modem.

[liquidneon]

Hi All,

I set up my Rogers Ignite internet yesterday, and so far am very unhappy. All my devices seem to be functioning fine - speed tests almost always show >50 MBPs down, and >10 MBPs up... but I consistently have very significant latency and/or jitter issues when playing my PS4 online (COD Warzone specifically), and occasionally during video calls. I have about 18 devices connected, most of which are idle most of the time (not always).  I can't figure out what to do and need help!!!

I opened up ports for Warzone as per https://www.purevpn.com/port-forwarding/call-of-duty-warzone --> this did not seem to resolve anything. 

I'm running out of options and patience. Any ideas how I can fix this?!?! very unhappy with this connection so far.

Here are my test results:

PING test

Ping statistics for 172.217.0.228:
    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 208ms, Average = 57ms

Ping statistics for 172.217.1.4:
    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 191ms, Average = 65ms

Ping statistics for 172.217.1.164:
    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 14ms, Maximum = 231ms, Average = 59ms

traceroute

Tracing route to www.google.com [172.217.1.164]
over a maximum of 30 hops:

  1    37 ms     9 ms     4 ms  10.0.0.1
  2    39 ms    16 ms    15 ms  99.224.224.1
  3    14 ms    19 ms    25 ms  8081-dgw01.etob.rmgt.net.rogers.com [66.185.91.49]
  4    16 ms   146 ms    15 ms  3009-cgw01.wlfdle.rmgt.net.rogers.com [69.63.248.181]
  5    27 ms    16 ms    13 ms  209.148.235.214
  6     *        *        *     Request timed out.
  7    15 ms    17 ms    15 ms  108.170.250.241
  8    15 ms    17 ms   153 ms  108.170.226.221
  9    23 ms    17 ms    17 ms  yyz10s04-in-f4.1e100.net [172.217.1.164]

Trace complete.

Tracing route to www.google.com [172.217.165.4]
over a maximum of 30 hops:

  1     8 ms     4 ms    23 ms  10.0.0.1
  2    17 ms    18 ms    17 ms  99.224.224.1
  3   435 ms    17 ms    14 ms  8081-dgw01.etob.rmgt.net.rogers.com [66.185.91.49]
  4    91 ms    26 ms    16 ms  3009-cgw01.wlfdle.rmgt.net.rogers.com [69.63.248.181]
  5   153 ms    17 ms   104 ms  209.148.235.214
  6    31 ms    17 ms    22 ms  72.14.216.54
  7    36 ms    15 ms    15 ms  209.85.249.15
  8    34 ms   101 ms    15 ms  216.239.41.175
  9   137 ms    11 ms    17 ms  yyz12s06-in-f4.1e100.net [172.217.165.4]

Trace complete.

Tracing route to www.google.com [172.217.165.4]
over a maximum of 30 hops:

  1    42 ms     9 ms     4 ms  10.0.0.1
  2   146 ms    19 ms    12 ms  99.224.224.1
  3    82 ms    18 ms    24 ms  8081-dgw01.etob.rmgt.net.rogers.com [66.185.91.49]
  4    76 ms    15 ms    22 ms  3009-cgw01.wlfdle.rmgt.net.rogers.com [69.63.248.181]
  5    15 ms    18 ms    26 ms  209.148.235.214
  6   127 ms    16 ms    20 ms  72.14.216.54
  7    22 ms    15 ms    44 ms  209.85.249.15
  8    58 ms    16 ms    22 ms  216.239.41.175
  9    21 ms    75 ms    50 ms  yyz12s06-in-f4.1e100.net [172.217.165.4]

Trace complete.

Tracing route to www.google.com [172.217.165.4]
over a maximum of 30 hops:

  1    25 ms     4 ms     4 ms  10.0.0.1
  2    14 ms    13 ms    12 ms  99.224.224.1
  3    23 ms    15 ms    13 ms  8081-dgw01.etob.rmgt.net.rogers.com [66.185.91.49]
  4    21 ms    17 ms   137 ms  3009-cgw01.wlfdle.rmgt.net.rogers.com [69.63.248.181]
  5    51 ms    18 ms    16 ms  209.148.235.214
  6    23 ms    15 ms    17 ms  72.14.216.54
  7    17 ms    16 ms    13 ms  209.85.249.15
  8   117 ms    15 ms    21 ms  216.239.41.175
  9    31 ms    14 ms    12 ms  yyz12s06-in-f4.1e100.net [172.217.165.4]

Trace complete.

in graphs below, left axis is ping in ms, right axis is loss %. Horrendous results:

[liquidneon]

also tried changing DNS - no luck. 

[liquidneon]

I'm thrilled that Rogers tech support told me to come check out this forum for help since they don't know how to fix my connection.... and no one even monitors it. They also told me they'd be sending a technician yesterday between 6 and 8PM. I rushed home to be there for 6PM... and no one showed up. What a joke. Calling Bell this weekend. 

[RogersAndy]

Hey @liquidneon!

Thank you for sharing your issue here. I'm sorry to hear that your scheduled technician didn't arrive. I can only imagine the distaste that experience must have left. We would love the chance to look into what happened here for you and see to it that any service issues remaining are addressed. Feel free to PM us at your convenience @CommunityHelps.   

You can read more about our PM system here.  

@RogersAndy

[gkvincent]

Yet no idea as to what was done to fix the issue. Great! Another mystery.

[liquidneon]

nothing solved yet. if they fix it, i will post on here. for now they just rescheduled my technician lol