CGN3ACSMR League of legends lag after firmware update

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
Vurog
I Plan to Stick Around
Posts: 8

Re: CGN3ACSMR League of legends lag after firmware update

I'm in an apartment building , I guess you could call it a high rise.
Datalink
Resident Expert
Resident Expert
Posts: 7,367

Re: CGN3ACSMR League of legends lag after firmware update

Ok, that means that there is most likely a Multiple Dwelling Unit (MDU) in the utility room providing data distribution to Rogers customers in the building. The MDU can be a challenge with something goes wrong.  If you're seeing online lags, that means that others should be noticing the same thing.  Give me a couple of minutes, I'll pm one of the mods to contact you.  Keep an eye on the envelope icon at the upper right for a private message.  I would still like to see your ping times with updated version, but one of the mods can have a look at the modem and MDU. 



Vurog
I Plan to Stick Around
Posts: 8

Re: CGN3ACSMR League of legends lag after firmware update

Thanks alot, appreciate it.
Datalink
Resident Expert
Resident Expert
Posts: 7,367

Re: CGN3ACSMR League of legends lag after firmware update

PM sent to @RogersMoin.



Robleh
I Plan to Stick Around
Posts: 33

Re: CGN3ACSMR League of legends lag after firmware update

Don't mean to highjack this thread but am also on the 100u and have same problems. Had a tech come over and change calbes etc but that didn't solve anything. Seeem to be getting high pings/packet loss this could be a local node issue no idea. 

 

C:\Users\Robleh>ping -t google.ca

Pinging google.ca [209.148.198.245] with 32 bytes of data:
Reply from 209.148.198.245: bytes=32 time=15ms TTL=58
Reply from 209.148.198.245: bytes=32 time=43ms TTL=58
Reply from 209.148.198.245: bytes=32 time=18ms TTL=58
Reply from 209.148.198.245: bytes=32 time=16ms TTL=58
Reply from 209.148.198.245: bytes=32 time=19ms TTL=58
Reply from 209.148.198.245: bytes=32 time=24ms TTL=58
Reply from 209.148.198.245: bytes=32 time=17ms TTL=58
Reply from 209.148.198.245: bytes=32 time=19ms TTL=58
Reply from 209.148.198.245: bytes=32 time=21ms TTL=58
Reply from 209.148.198.245: bytes=32 time=28ms TTL=58
Reply from 209.148.198.245: bytes=32 time=75ms TTL=58
Reply from 209.148.198.245: bytes=32 time=27ms TTL=58
Reply from 209.148.198.245: bytes=32 time=38ms TTL=58
Reply from 209.148.198.245: bytes=32 time=29ms TTL=58
Reply from 209.148.198.245: bytes=32 time=33ms TTL=58
Reply from 209.148.198.245: bytes=32 time=27ms TTL=58
Reply from 209.148.198.245: bytes=32 time=19ms TTL=58
Request timed out.
Reply from 209.148.198.245: bytes=32 time=19ms TTL=58
Reply from 209.148.198.245: bytes=32 time=43ms TTL=58
Reply from 209.148.198.245: bytes=32 time=25ms TTL=58
Reply from 209.148.198.245: bytes=32 time=32ms TTL=58
Reply from 209.148.198.245: bytes=32 time=16ms TTL=58
Reply from 209.148.198.245: bytes=32 time=32ms TTL=58
Reply from 209.148.198.245: bytes=32 time=12ms TTL=58
Reply from 209.148.198.245: bytes=32 time=17ms TTL=58
Reply from 209.148.198.245: bytes=32 time=84ms TTL=58
Reply from 209.148.198.245: bytes=32 time=49ms TTL=58
Reply from 209.148.198.245: bytes=32 time=184ms TTL=58
Reply from 209.148.198.245: bytes=32 time=40ms TTL=58
Reply from 209.148.198.245: bytes=32 time=31ms TTL=58
Reply from 209.148.198.245: bytes=32 time=15ms TTL=58
Reply from 209.148.198.245: bytes=32 time=34ms TTL=58
Reply from 209.148.198.245: bytes=32 time=13ms TTL=58
Reply from 209.148.198.245: bytes=32 time=32ms TTL=58
Reply from 209.148.198.245: bytes=32 time=12ms TTL=58
Reply from 209.148.198.245: bytes=32 time=16ms TTL=58
Reply from 209.148.198.245: bytes=32 time=19ms TTL=58
Reply from 209.148.198.245: bytes=32 time=36ms TTL=58
Reply from 209.148.198.245: bytes=32 time=96ms TTL=58
Reply from 209.148.198.245: bytes=32 time=24ms TTL=58
Reply from 209.148.198.245: bytes=32 time=18ms TTL=58
Reply from 209.148.198.245: bytes=32 time=51ms TTL=58
Reply from 209.148.198.245: bytes=32 time=42ms TTL=58
Reply from 209.148.198.245: bytes=32 time=21ms TTL=58
Reply from 209.148.198.245: bytes=32 time=21ms TTL=58
Reply from 209.148.198.245: bytes=32 time=27ms TTL=58
Reply from 209.148.198.245: bytes=32 time=12ms TTL=58
Reply from 209.148.198.245: bytes=32 time=21ms TTL=58
Reply from 209.148.198.245: bytes=32 time=29ms TTL=58
Reply from 209.148.198.245: bytes=32 time=14ms TTL=58
Reply from 209.148.198.245: bytes=32 time=19ms TTL=58
Reply from 209.148.198.245: bytes=32 time=23ms TTL=58
Reply from 209.148.198.245: bytes=32 time=52ms TTL=58
Reply from 209.148.198.245: bytes=32 time=16ms TTL=58
Reply from 209.148.198.245: bytes=32 time=17ms TTL=58
Reply from 209.148.198.245: bytes=32 time=23ms TTL=58
Reply from 209.148.198.245: bytes=32 time=32ms TTL=58
Reply from 209.148.198.245: bytes=32 time=57ms TTL=58
Reply from 209.148.198.245: bytes=32 time=153ms TTL=58
Reply from 209.148.198.245: bytes=32 time=166ms TTL=58
Reply from 209.148.198.245: bytes=32 time=21ms TTL=58
Reply from 209.148.198.245: bytes=32 time=140ms TTL=58
Reply from 209.148.198.245: bytes=32 time=23ms TTL=58
Reply from 209.148.198.245: bytes=32 time=18ms TTL=58
Reply from 209.148.198.245: bytes=32 time=27ms TTL=58
Reply from 209.148.198.245: bytes=32 time=34ms TTL=58
Reply from 209.148.198.245: bytes=32 time=190ms TTL=58
Reply from 209.148.198.245: bytes=32 time=30ms TTL=58
Reply from 209.148.198.245: bytes=32 time=98ms TTL=58
Reply from 209.148.198.245: bytes=32 time=48ms TTL=58
Reply from 209.148.198.245: bytes=32 time=83ms TTL=58
Reply from 209.148.198.245: bytes=32 time=26ms TTL=58
Reply from 209.148.198.245: bytes=32 time=67ms TTL=58
Reply from 209.148.198.245: bytes=32 time=100ms TTL=58
Reply from 209.148.198.245: bytes=32 time=38ms TTL=58
Reply from 209.148.198.245: bytes=32 time=25ms TTL=58

Ping statistics for 209.148.198.245:
Packets: Sent = 77, Received = 76, Lost = 1 (1% loss),

RogersMoin
Moderator
Moderator
Posts: 1,996

Re: CGN3ACSMR League of legends lag after firmware update

 

Hello, @Vurog

 

Welcome to the Rogers Community Forums! Smiley Happy

 

Thanks @Datalink for all the help. @Vurog would you please message CommunityHelps with your modem's MAC address and Cable Account Reference Number, I'll be able to run all diagnostics and follow-up with deployment team for the firmware update.

 

Thank you for your patience!

RogersMoin

Vurog
I Plan to Stick Around
Posts: 8

Re: CGN3ACSMR League of legends lag after firmware update

Sent!

Vurog
I Plan to Stick Around
Posts: 8

Re: CGN3ACSMR League of legends lag after firmware update

My modem just restarted and i am now on the latest firmware, However I still have high latency to all the servers I mentioned in my earlier post.

 

Heres google.ca, can post more if requested.

http://pastebin.com/uaqxYyLB

 

 

Datalink
Resident Expert
Resident Expert
Posts: 7,367

Re: CGN3ACSMR League of legends lag after firmware update

Your first hop to the Rogers server is very slow.  Let @RogersMoin have a look at the MDU or node, and see what he can determine.  This probably won't be something that can be fixed in a couple of minutes.  



Vurog
I Plan to Stick Around
Posts: 8

Re: CGN3ACSMR League of legends lag after firmware update

Modem just restarted about 20 minutes ago and I am seeing back to normal latency, Mad props to @datalink and @rogersmoin for getting this sorted :). Thanks alot guys!