Packet Loss in Application

[1_3_3_7]

I've been experiencing packet loss on an application and no matter which device I use, the packet loss is there... I've tried on my desktop, my laptop and even a family's laptop and desktop... the packet loss is STILL there. I've also tried on wired and wi-fi connection, I've tried downgrading/updating OS and playing around with network settings... a Rogers tech even came to check the cables and even upgrading the modem to the latest version (gen3) I even tried splitting the wi-fi bands and trying them individually... 2.4ghz 5ghz 6ghz... same issue!

Please escalate my issue to Rogers so they can FIX IT!

PING TEST - 

Ping statistics for 34.86.179.61:
Packets: Sent = 50, Received = 49, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 80ms, Average = 39ms

TRACEROUTE TEST - 

tracert 34.86.179.61

Tracing route to 61.179.86.34.bc.googleusercontent.com [34.86.179.61]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.1
2 16 ms 15 ms 29 ms pool-99-246-142-1.cpe.net.cable.rogers.com [99.246.142.1]
3 15 ms 21 ms 10 ms 24.156.150.233
4 12 ms 17 ms 9 ms 3032-cgw01.wlfdle.rmgt.net.rogers.com [209.148.232.37]
5 13 ms 8 ms 6 ms 209.148.235.214
6 14 ms 18 ms 20 ms 72.14.216.54
7 33 ms 34 ms 33 ms 61.179.86.34.bc.googleusercontent.com [34.86.179.61]

Trace complete.

***Edited Labels***

[RogersJermaine]

Thank you for posting your concern in the Rogers Community Forums!

We definitely understand how frustrating this experience has been for you. We have received your PM and will be happy to continue assisting you there.

RogersJermaine

[1_3_3_7]

Traceroute Result:
1, 10.0.0.1, *, *

*, 3.940/6.415/9.629/2.137 ms
2, 99.246.142.1, AS812, *
Canada Ontario Mississauga rogers.com
pool-99-246-142-1.cpe.net.cable.rogers.com., 18.623/20.916/23.467/1.832 ms
3, 24.156.150.233, AS812, *
Canada Ontario Mississauga rogers.com
*, *

5, *, ,

,
6, *, ,

,
7, *, ,

,
8, *, ,

,
9, *, ,

,
10, *, ,

,
11, *, ,

,
12, *, ,

,
13, *, ,

,
14, *, ,

,
15, *, ,

,
16, *, ,

,
17, *, ,

,
18, *, ,

,
19, *, ,

,
20, *, ,

,
21, *, ,

,
22, *, ,

,
23, *, ,

,

25, *, ,

,
26, *, ,

,
27, *, ,

,
28, *, ,

,

30, *, ,

,

[1_3_3_7]

Rogers has already sent 2 technicians to our establishment to check hardware and wiring and do "speed tests" even after I told them that NONE OF THOSE THINGS ARE THE PROBLEM. They are wasting my time and their own time and need to escalate the issue to the Rogers network team! This is RIDICULOUS that this simple issue still has not been resolved yet.

[RogersCorey]

Good morning @1_3_3_7!

I sent you some of my diagnostic results yesterday in private. If you could return to our private chat and post a fresh ping test and tracert to the problematic server for me, that would be helpful.

Thank you!

Regards,

RogersCorey