cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
1,288 Views
Message 281 of 1,014

Re: Recent online gaming ping spikes when streaming Netflix

From a BT connection in SW London I get 12ms mate.
0 Ratings
1,275 Views
Message 282 of 1,014

Re: Recent online gaming ping spikes when streaming Netflix

My pings to your overwatch server dubstepzombie are steady between 28 and 32ms with multiple device streaming hd content at the same time. This was over 40 to 50 pings
0 Ratings
1,271 Views
Message 283 of 1,014

Re: Recent online gaming ping spikes when streaming Netflix

Just ran a tracert to the overwatch server and was spot on, and interestingly, only 8 hops. My bt fibre was 12 hops.
0 Ratings
1,263 Views
Message 284 of 1,014

Re: Recent online gaming ping spikes when streaming Netflix

 

@Mighten82 it does sound like you've got a definite positive result, where I am at the moment is wondering if Sky will provide a better connection seeing as my BT connection is reasonably ok at the moment.

If it shaved a few ms off my ping and gave me even less ping jitter from running other things on my network I'd switch, I'm at the point of thinking if it ain't broke then don't fix it. I guess when my contract ends next year I'll switch, when I rang sky they ended up cheaper than BT which also included a TV package.

Anyone in London will have a better base ping seeing as all the routing is done in London, my ping to the Overwatch server is 17ms

 

Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=17ms TTL=245
Reply from 185.60.112.157: bytes=32 time=17ms TTL=245
Reply from 185.60.112.157: bytes=32 time=17ms TTL=245
Reply from 185.60.112.157: bytes=32 time=17ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=17ms TTL=245

0 Ratings
1,120 Views
Message 285 of 1,014

Re: Recent online gaming ping spikes when streaming Netflix

Just started getting this issue after a couple months with BT.

0 Ratings
1,114 Views
Message 286 of 1,014

Re: Recent online gaming ping spikes when streaming Netflix

Just did some quick testing after noticing something with Twitch (only twitch).

If I watch a stream that HAS low latency turned on (and I have low latency turned on in cog wheel) that the ping doesn't jitter as much at all.

CohhCarnage Stream WITH low latency enabled:
Pinging google.co.uk [216.58.210.35] with 32 bytes of data:
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=22ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=34ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=19ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=21ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=22ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=35ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54

CohhCarnage Stream WITHOUT low latency enabled:
Pinging google.co.uk [216.58.210.227] with 32 bytes of data:
Reply from 216.58.210.227: bytes=32 time=73ms TTL=54 - HIGH
Reply from 216.58.210.227: bytes=32 time=72ms TTL=54 - HIGH
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=73ms TTL=54 - HIGH
Reply from 216.58.210.227: bytes=32 time=17ms TTL=54
Reply from 216.58.210.227: bytes=32 time=17ms TTL=54
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=17ms TTL=54
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=17ms TTL=54
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=73ms TTL=54 - HIGH
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=17ms TTL=54
Reply from 216.58.210.227: bytes=32 time=72ms TTL=54 - HIGH
Reply from 216.58.210.227: bytes=32 time=17ms TTL=54
Reply from 216.58.210.227: bytes=32 time=17ms TTL=54
Reply from 216.58.210.227: bytes=32 time=17ms TTL=54
Reply from 216.58.210.227: bytes=32 time=72ms TTL=54 - HIGH
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54

As you can see from the ping tests to google.co.uk it could be pointing to something other than BT's network... (in my case at least)

Would anyone else mind testing this and sharing the results?
0 Ratings
1,111 Views
Message 287 of 1,014

Re: Recent online gaming ping spikes when streaming Netflix

@h3x1e  sure no problem,  my connection after the BT magic fix - whatever they did ?

 

Steam downloading at 3MB/s

Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=15ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=52ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=47ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=51ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=28ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=40ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54

 

No downloads -

 

Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=18ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54
Reply from 216.58.210.35: bytes=32 time=8ms TTL=54

 

0 Ratings
1,109 Views
Message 288 of 1,014

Re: Recent online gaming ping spikes when streaming Netflix

Hang on - wrong IP 🙂 much the same though

 

Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=8ms TTL=54
Reply from 216.58.210.227: bytes=32 time=8ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=8ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=8ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=8ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=8ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=8ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=8ms TTL=54
Reply from 216.58.210.227: bytes=32 time=8ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=8ms TTL=54
Reply from 216.58.210.227: bytes=32 time=8ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=8ms TTL=54
Reply from 216.58.210.227: bytes=32 time=8ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=8ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=8ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=8ms TTL=54
Reply from 216.58.210.227: bytes=32 time=8ms TTL=54
Reply from 216.58.210.227: bytes=32 time=8ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54
Reply from 216.58.210.227: bytes=32 time=9ms TTL=54

 

0 Ratings
1,018 Views
Message 289 of 1,014

Re: Recent online gaming ping spikes when streaming Netflix

It's been maybe 5 weeks since this started and my landlord is dragging his feet on switching providers even though we're out of contract.

 

Pinging 185.60.112.157 with 32 bytes of data:
Reply from 185.60.112.157: bytes=32 time=17ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=166ms TTL=245
Reply from 185.60.112.157: bytes=32 time=25ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=173ms TTL=245
Reply from 185.60.112.157: bytes=32 time=126ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=17ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245
Reply from 185.60.112.157: bytes=32 time=16ms TTL=245

0 Ratings
983 Views
Message 290 of 1,014

Re: Recent online gaming ping spikes when streaming Netflix

Enter your own contract mate, why is you landlord responsible for broadband? Shared accommodation?
0 Ratings