dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
689

Online game
@209.202.64.x

Online game

Anon

Online gaming lag

So I'm sure anyone in Ontario who plays games online knows there is issues with lag between 7pm and 11pm EST.

Who the heck do I need to complain to to get it straightened out or made more people aware, it's a serious issue when it effects any online games for whole of Ontario.

CRTC, Media outlets?
Anzio
join:2008-11-22

Anzio

Member

No issues here. Have you done basic troubleshooting with your ISP?

Bad lag
@209.202.64.x

Bad lag

Anon

I've already done the basic trouble shooting, they tell me it's out of their hands.

But the fact is there is traffic shaping going on.

Go ahead try any game online between 7pm est and 11pm est, my issues is already with their level 3 and been sent to Rogers already.. but the fact is it just isn't me. You can Google and find TONS of people having the EXACT same problem on any online game.

Calero27
join:2014-01-13
Chatham, ON

Calero27 to Online game

Member

to Online game
Sound like a congestion issue. Everyone being on at the same time.

The only thing to do is wait for them to preform a node split which normally takes a few months.

Guspaz
Guspaz
MVM
join:2001-11-05
Montreal, QC

Guspaz to Online game

MVM

to Online game
It's not normal to experience lag from 7PM to 11PM, and it's definitely not the norm for the entire province.

Calero27
join:2014-01-13
Chatham, ON

Calero27 to Online game

Member

to Online game
I've been playing a lot of DDO the past week and have had no issues.

I guess more information would be helpful.

At the beginning of the year I was on a congested node and online gaming suffered till Cogeco did a node split.

donoreo
Premium Member
join:2002-05-30
North York, ON

donoreo to Online game

Premium Member

to Online game
To address your suggestions, do you think the CRTC or the media will care about your gaming slowing down?
Chosen14u
join:2011-05-14
Scarborough, ON

Chosen14u

Member

sadly no
dallas1
join:2014-04-16
Oshawa

dallas1 to Online game

Member

to Online game
I been fine here in oshawa im with start 150\15
graniterock
Premium Member
join:2003-03-14
London, ON

graniterock to Bad lag

Premium Member

to Bad lag
Of all the traffic to shape, why gaming? Firefall works great during peak at a steady 41 ms. My friends complain about league. There are ways to trouble shoot this. A tool that does multiple trace routes would be my next step. Track down where the lag starts.

Guspaz
Guspaz
MVM
join:2001-11-05
Montreal, QC

Guspaz to donoreo

MVM

to donoreo
said by donoreo:

To address your suggestions, do you think the CRTC or the media will care about your gaming slowing down?

Teresa was able to get the CRTC to slap Rogers on the wrist because their throttling was impacting WoW, so... yes. They do care about such things, but only if there is a legitimate complaint. And "the Internet is slow" isn't a valid complaint to the CRTC if there isn't something like an ITMP violation happening.

MacGyver

join:2001-10-14
Vancouver, BC
·TELUS
Actiontec T3200M
Arcadyan WE410443-TS
Sipura SPA-2102

MacGyver to Online game

to Online game
Get an ISP that can and will fix the problem for you. TSI Gabe See Profile has been very helpful, doing his best to change Teksavvy routing to accomodate customer needs - even for games

I live in Ontario and I have no lag.

Nitra
join:2011-09-15
Montreal

Nitra

Member

You have no basis in fact to claim that traffic shaping is in use whatsoever.

Please stop posting FUD
Chosen14u
join:2011-05-14
Scarborough, ON

Chosen14u

Member

what are you some part of Rogers and don't want this information out?

A simple Google will tell you people are having the exact same issues all over Ontario with online gaming lag.

I am not delusional that at 7pm it goes bad and then 11pm it's back to normal.
I am running line monitors that also show my ping right around 7pm goes horrible and then 11pm it's back to normal. I will continue to monitor and document these.
f1ipmode
join:2014-09-29
Ajax, ON

f1ipmode to MacGyver

Member

to MacGyver
I agree with MacG. I have Teksavvy live in Ontario and rarely experience lag.
Chosen14u
join:2011-05-14
Scarborough, ON

Chosen14u to Online game

Member

to Online game
Everyone please run this line monitoring -

»/monit ··· d/detail

I want to get a class action lawsuit going if we can gather enough data we can prove that our lines from Distributel are being throttle for online gaming.

Thanks

oceros37
join:2013-07-20
St Thomas, ON

oceros37 to Online game

Member

to Online game
-- also having no issues gaming in ontario
mikee
join:2012-12-21
Gloucester, ON

mikee to Online game

Member

to Online game
no lag here what so ever living in ottawa, orleans any hour of the day.

DKS
Damn Kidney Stones

join:2001-03-22
Owen Sound, ON

DKS to Online game

to Online game
I was having major ping issues in the summer, but the folks in the Bell Direct forum said it was related to congestion and that it would be resolved by mid-July, when Bell added fibre capacity. It was, right after the date they promised. Congestion is congestion and it can be local.

BF4 had had rubber banding issues all over the world since the last patch a week ago, but that is related to the patch itself and is provider independent.
Chosen14u
join:2011-05-14
Scarborough, ON

Chosen14u to Online game

Member

to Online game
»imgur.com/xgm1RF6

had bad lag tonight, line monitoring goes back to normal right at 11
graniterock
Premium Member
join:2003-03-14
London, ON

graniterock

Premium Member

You need to run tracerts to figure out where the problem is. Local congestion won't get you a class action suit for gaming throttling.
Mazgazine
join:2010-11-18

Mazgazine to Online game

Member

to Online game
I have the exact same problem here - I ping google and its bad also. When I try to play anything online related I get spikes of 2000ms. Downloading from any service is extremely slow. For some odd reason netflix still works....

On distributel - London ONtario

Issue starts at 7:30pm here. Check it out:

Pinging www.google.com [74.125.225.145] with 32 bytes
Reply from 74.125.225.145: bytes=32 time=32ms TTL=55
Reply from 74.125.225.145: bytes=32 time=31ms TTL=55
Reply from 74.125.225.145: bytes=32 time=187ms TTL=55
Reply from 74.125.225.145: bytes=32 time=67ms TTL=55
Reply from 74.125.225.145: bytes=32 time=29ms TTL=55
Reply from 74.125.225.145: bytes=32 time=28ms TTL=55
Reply from 74.125.225.145: bytes=32 time=53ms TTL=55
Reply from 74.125.225.145: bytes=32 time=34ms TTL=55
Reply from 74.125.225.145: bytes=32 time=82ms TTL=55
Reply from 74.125.225.145: bytes=32 time=45ms TTL=55
Reply from 74.125.225.145: bytes=32 time=72ms TTL=55
Reply from 74.125.225.145: bytes=32 time=40ms TTL=55
Reply from 74.125.225.145: bytes=32 time=38ms TTL=55
Reply from 74.125.225.145: bytes=32 time=34ms TTL=55
Reply from 74.125.225.145: bytes=32 time=192ms TTL=55
Reply from 74.125.225.145: bytes=32 time=60ms TTL=55
Reply from 74.125.225.145: bytes=32 time=81ms TTL=55
Reply from 74.125.225.145: bytes=32 time=38ms TTL=55
Reply from 74.125.225.145: bytes=32 time=36ms TTL=55
Reply from 74.125.225.145: bytes=32 time=31ms TTL=55
Reply from 74.125.225.145: bytes=32 time=31ms TTL=55
Reply from 74.125.225.145: bytes=32 time=37ms TTL=55
Reply from 74.125.225.145: bytes=32 time=67ms TTL=55
Reply from 74.125.225.145: bytes=32 time=123ms TTL=55
Reply from 74.125.225.145: bytes=32 time=38ms TTL=55
Reply from 74.125.225.145: bytes=32 time=61ms TTL=55
Reply from 74.125.225.145: bytes=32 time=60ms TTL=55
Reply from 74.125.225.145: bytes=32 time=45ms TTL=55
Reply from 74.125.225.145: bytes=32 time=42ms TTL=55
Reply from 74.125.225.145: bytes=32 time=79ms TTL=55
Reply from 74.125.225.145: bytes=32 time=150ms TTL=55
Reply from 74.125.225.145: bytes=32 time=112ms TTL=55
Reply from 74.125.225.145: bytes=32 time=117ms TTL=55
Reply from 74.125.225.145: bytes=32 time=111ms TTL=55
Reply from 74.125.225.145: bytes=32 time=84ms TTL=55
Reply from 74.125.225.145: bytes=32 time=114ms TTL=55
Reply from 74.125.225.145: bytes=32 time=89ms TTL=55
Reply from 74.125.225.145: bytes=32 time=31ms TTL=55
Reply from 74.125.225.145: bytes=32 time=34ms TTL=55
Reply from 74.125.225.145: bytes=32 time=49ms TTL=55
Reply from 74.125.225.145: bytes=32 time=32ms TTL=55
Reply from 74.125.225.145: bytes=32 time=32ms TTL=55
Reply from 74.125.225.145: bytes=32 time=30ms TTL=55
Reply from 74.125.225.145: bytes=32 time=29ms TTL=55
Reply from 74.125.225.145: bytes=32 time=58ms TTL=55
Reply from 74.125.225.145: bytes=32 time=43ms TTL=55
Reply from 74.125.225.145: bytes=32 time=62ms TTL=55
Reply from 74.125.225.145: bytes=32 time=33ms TTL=55
Reply from 74.125.225.145: bytes=32 time=98ms TTL=55
Reply from 74.125.225.145: bytes=32 time=54ms TTL=55
Reply from 74.125.225.145: bytes=32 time=31ms TTL=55
Reply from 74.125.225.145: bytes=32 time=42ms TTL=55
Reply from 74.125.225.145: bytes=32 time=41ms TTL=55
Reply from 74.125.225.145: bytes=32 time=47ms TTL=55
Reply from 74.125.225.145: bytes=32 time=30ms TTL=55
Reply from 74.125.225.145: bytes=32 time=29ms TTL=55
Reply from 74.125.225.145: bytes=32 time=30ms TTL=55
Reply from 74.125.225.145: bytes=32 time=30ms TTL=55
Reply from 74.125.225.145: bytes=32 time=31ms TTL=55
Reply from 74.125.225.145: bytes=32 time=30ms TTL=55
Reply from 74.125.225.145: bytes=32 time=36ms TTL=55
Reply from 74.125.225.145: bytes=32 time=41ms TTL=55
Reply from 74.125.225.145: bytes=32 time=72ms TTL=55
Reply from 74.125.225.145: bytes=32 time=79ms TTL=55
Reply from 74.125.225.145: bytes=32 time=89ms TTL=55
Reply from 74.125.225.145: bytes=32 time=40ms TTL=55
Reply from 74.125.225.145: bytes=32 time=81ms TTL=55
Reply from 74.125.225.145: bytes=32 time=103ms TTL=55
Reply from 74.125.225.145: bytes=32 time=65ms TTL=55
Reply from 74.125.225.145: bytes=32 time=30ms TTL=55
Reply from 74.125.225.145: bytes=32 time=30ms TTL=55
Reply from 74.125.225.145: bytes=32 time=52ms TTL=55
Reply from 74.125.225.145: bytes=32 time=29ms TTL=55
Reply from 74.125.225.145: bytes=32 time=31ms TTL=55
Reply from 74.125.225.145: bytes=32 time=85ms TTL=55
Reply from 74.125.225.145: bytes=32 time=39ms TTL=55
Reply from 74.125.225.145: bytes=32 time=91ms TTL=55
Reply from 74.125.225.145: bytes=32 time=28ms TTL=55
Reply from 74.125.225.145: bytes=32 time=53ms TTL=55
Reply from 74.125.225.145: bytes=32 time=122ms TTL=55
Reply from 74.125.225.145: bytes=32 time=71ms TTL=55
Reply from 74.125.225.145: bytes=32 time=29ms TTL=55
Reply from 74.125.225.145: bytes=32 time=34ms TTL=55
Reply from 74.125.225.145: bytes=32 time=39ms TTL=55
Reply from 74.125.225.145: bytes=32 time=31ms TTL=55
Reply from 74.125.225.145: bytes=32 time=94ms TTL=55
Reply from 74.125.225.145: bytes=32 time=42ms TTL=55
Reply from 74.125.225.145: bytes=32 time=30ms TTL=55
Reply from 74.125.225.145: bytes=32 time=71ms TTL=55
Reply from 74.125.225.145: bytes=32 time=30ms TTL=55
Reply from 74.125.225.145: bytes=32 time=29ms TTL=55
Reply from 74.125.225.145: bytes=32 time=31ms TTL=55
Reply from 74.125.225.145: bytes=32 time=42ms TTL=55
Reply from 74.125.225.145: bytes=32 time=170ms TTL=55
Reply from 74.125.225.145: bytes=32 time=121ms TTL=55
Reply from 74.125.225.145: bytes=32 time=110ms TTL=55
Reply from 74.125.225.145: bytes=32 time=153ms TTL=55
Reply from 74.125.225.145: bytes=32 time=155ms TTL=55
Reply from 74.125.225.145: bytes=32 time=201ms TTL=55
Reply from 74.125.225.145: bytes=32 time=161ms TTL=55

Reply from 74.125.225.145: bytes=32 time=95ms TTL=55
Reply from 74.125.225.145: bytes=32 time=84ms TTL=55
Reply from 74.125.225.145: bytes=32 time=64ms TTL=55
Reply from 74.125.225.145: bytes=32 time=31ms TTL=55
Reply from 74.125.225.145: bytes=32 time=182ms TTL=55
Reply from 74.125.225.145: bytes=32 time=90ms TTL=55
Reply from 74.125.225.145: bytes=32 time=211ms TTL=55
Reply from 74.125.225.145: bytes=32 time=323ms TTL=55
Reply from 74.125.225.145: bytes=32 time=239ms TTL=55
Reply from 74.125.225.145: bytes=32 time=188ms TTL=55
Reply from 74.125.225.145: bytes=32 time=160ms TTL=55
Reply from 74.125.225.145: bytes=32 time=243ms TTL=55
Reply from 74.125.225.145: bytes=32 time=200ms TTL=55
Reply from 74.125.225.145: bytes=32 time=232ms TTL=55
Reply from 74.125.225.145: bytes=32 time=196ms TTL=55
Reply from 74.125.225.145: bytes=32 time=150ms TTL=55
Reply from 74.125.225.145: bytes=32 time=228ms TTL=55
Reply from 74.125.225.145: bytes=32 time=214ms TTL=55
Reply from 74.125.225.145: bytes=32 time=174ms TTL=55
Reply from 74.125.225.145: bytes=32 time=230ms TTL=55
Reply from 74.125.225.145: bytes=32 time=134ms TTL=55
Reply from 74.125.225.145: bytes=32 time=250ms TTL=55
Reply from 74.125.225.145: bytes=32 time=194ms TTL=55
Reply from 74.125.225.145: bytes=32 time=185ms TTL=55
Reply from 74.125.225.145: bytes=32 time=150ms TTL=55
Reply from 74.125.225.145: bytes=32 time=255ms TTL=55
Reply from 74.125.225.145: bytes=32 time=352ms TTL=55
Reply from 74.125.225.145: bytes=32 time=154ms TTL=55
Reply from 74.125.225.145: bytes=32 time=365ms TTL=55
Reply from 74.125.225.145: bytes=32 time=249ms TTL=55
Reply from 74.125.225.145: bytes=32 time=404ms TTL=55
Reply from 74.125.225.145: bytes=32 time=308ms TTL=55
Reply from 74.125.225.145: bytes=32 time=303ms TTL=55
Reply from 74.125.225.145: bytes=32 time=257ms TTL=55
Reply from 74.125.225.145: bytes=32 time=361ms TTL=55
Reply from 74.125.225.145: bytes=32 time=265ms TTL=55
Reply from 74.125.225.145: bytes=32 time=96ms TTL=55
Reply from 74.125.225.145: bytes=32 time=132ms TTL=55
Reply from 74.125.225.145: bytes=32 time=181ms TTL=55
Reply from 74.125.225.145: bytes=32 time=54ms TTL=55

Reply from 74.125.225.145: bytes=32 time=69ms TTL=55
Reply from 74.125.225.145: bytes=32 time=85ms TTL=55
Reply from 74.125.225.145: bytes=32 time=83ms TTL=55
Reply from 74.125.225.145: bytes=32 time=65ms TTL=55
Reply from 74.125.225.145: bytes=32 time=80ms TTL=55
Reply from 74.125.225.145: bytes=32 time=90ms TTL=55
Reply from 74.125.225.145: bytes=32 time=86ms TTL=55
Reply from 74.125.225.145: bytes=32 time=29ms TTL=55
Reply from 74.125.225.145: bytes=32 time=66ms TTL=55
Reply from 74.125.225.145: bytes=32 time=96ms TTL=55
Reply from 74.125.225.145: bytes=32 time=61ms TTL=55
Reply from 74.125.225.145: bytes=32 time=104ms TTL=55
Reply from 74.125.225.145: bytes=32 time=71ms TTL=55
Reply from 74.125.225.145: bytes=32 time=32ms TTL=55
Reply from 74.125.225.145: bytes=32 time=71ms TTL=55
Reply from 74.125.225.145: bytes=32 time=29ms TTL=55
Reply from 74.125.225.145: bytes=32 time=69ms TTL=55
Reply from 74.125.225.145: bytes=32 time=31ms TTL=55
Reply from 74.125.225.145: bytes=32 time=66ms TTL=55
Reply from 74.125.225.145: bytes=32 time=33ms TTL=55
Reply from 74.125.225.145: bytes=32 time=30ms TTL=55
Reply from 74.125.225.145: bytes=32 time=31ms TTL=55
Reply from 74.125.225.145: bytes=32 time=29ms TTL=55
Reply from 74.125.225.145: bytes=32 time=33ms TTL=55
Reply from 74.125.225.145: bytes=32 time=80ms TTL=55
Reply from 74.125.225.145: bytes=32 time=85ms TTL=55
Reply from 74.125.225.145: bytes=32 time=47ms TTL=55
Reply from 74.125.225.145: bytes=32 time=30ms TTL=55
Reply from 74.125.225.145: bytes=32 time=30ms TTL=55
Reply from 74.125.225.145: bytes=32 time=64ms TTL=55
Reply from 74.125.225.145: bytes=32 time=56ms TTL=55
graniterock
Premium Member
join:2003-03-14
London, ON

graniterock

Premium Member

Something is definitely wrong. Try using this tracert tool. It will track down exactly where the bad server is. »winmtr.net/ (You can tracert from command prompt too but this will automate doing it over and over again).
Mazgazine
join:2010-11-18

Mazgazine

Member

I will give it a shot. I'll let you know what its like tonight.

jmck
formerly 'shaded'
join:2010-10-02
Ottawa, ON

jmck to Online game

Member

to Online game
you also need to post modem stats when it's having issues, and make sure nobody else is using the internet too, if someone downloads or uploads a photo from their iPhone while you're playing you'll lag quite a bit until it finishes.