cancel
Showing results for 
Search instead for 
Did you mean: 

High Latency + TV Micro Blocking

FedUp5000
I plan to stick around

Long time Roger's customer since the 1980's with ongoing issues that has been ongoing for years intermittently...

Background:
Just north of Markham in Stouffville.
On the 1gig "Legacy" plan.
Ethernet connected gaming on ps network and multiple wifi devices.

Between the hours of about 7:30/8:00pm to about 11:00/11:30pm I have high ping with packet loss spikes while gaming as well as "micro blocking" on my TV.

Outside these hours I get a 20-40ms latency on the ps servers and have zero issues with my tv. But during those "peak hours" it jumps to 120-200ms latency with occasional spikes to 800-900ms and random packet burst/loss.

The issue started happening again about 2 weeks ago and normally I would call in and get it resolved. This time I have called multiple times and they keep telling me there are no issues...

Instead of trying to help the reps just forcefully try to sell me on the new "Ignite" hardware when my current hardware works perfectly fine outside peak hours.

Very Frustrating.

Help!

 

**Labels Added**

24 REPLIES 24

Re: High Latency + TV Micro Blocking

FedUp5000
I plan to stick around

Tracing route to www.google.com [2607:f8b0:400b:80c::2004]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 2607:fea8:7658:e250:c294:35ff:fec8:9394
2 19 ms 18 ms 22 ms 2607:f798:804:1ef::1
3 21 ms 15 ms 35 ms 2607:f798:10:cf9:0:690:6324:3097
4 15 ms 16 ms 18 ms 2607:f798:10:10b0:0:2091:4823:2053
5 15 ms 16 ms 22 ms 2607:f798:10:35a:0:2091:4823:5214
6 15 ms 15 ms 16 ms 2607:f798:14:83::2
7 3143 ms 145 ms 101 ms 2001:4860:0:11d6::1
8 27 ms 23 ms 31 ms 2001:4860:0:1::31e1
9 45 ms 45 ms 37 ms yyz10s05-in-x04.1e100.net [2607:f8b0:400b:80c::2004]

Trace complete.

Re: High Latency + TV Micro Blocking

FedUp5000
I plan to stick around

now my night time numbers....

 

Tracing route to www.google.com [2607:f8b0:400b:80c::2004]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 2607:fea8:765c:b850:c294:35ff:fec8:9394
2 89 ms 91 ms 84 ms 2607:f798:804:1ef::1
3 93 ms 84 ms 85 ms 2607:f798:10:cf8:0:690:6324:3093
4 90 ms 92 ms 94 ms 2607:f798:10:c9e:0:2091:4823:2049
5 99 ms 99 ms 106 ms 2607:f798:10:35c:0:2091:4823:5222
6 85 ms 104 ms 101 ms 2607:f798:14:83::2
7 97 ms 98 ms 90 ms 2001:4860::1c:4000:e8cb
8 74 ms 83 ms 96 ms 2001:4860:0:1::31cd
9 81 ms 86 ms 90 ms yyz10s05-in-x04.1e100.net [2607:f8b0:400b:80c::2004]

Trace complete.

Pinging www.google.com [2607:f8b0:400b:80c::2004] with 32 bytes of data:
Reply from 2607:f8b0:400b:80c::2004: time=79ms
Reply from 2607:f8b0:400b:80c::2004: time=77ms
Reply from 2607:f8b0:400b:80c::2004: time=75ms
Reply from 2607:f8b0:400b:80c::2004: time=87ms
Reply from 2607:f8b0:400b:80c::2004: time=70ms
Reply from 2607:f8b0:400b:80c::2004: time=83ms
Reply from 2607:f8b0:400b:80c::2004: time=74ms
Reply from 2607:f8b0:400b:80c::2004: time=75ms
Reply from 2607:f8b0:400b:80c::2004: time=85ms
Reply from 2607:f8b0:400b:80c::2004: time=96ms
Reply from 2607:f8b0:400b:80c::2004: time=76ms
Reply from 2607:f8b0:400b:80c::2004: time=64ms
Reply from 2607:f8b0:400b:80c::2004: time=80ms
Reply from 2607:f8b0:400b:80c::2004: time=76ms
Reply from 2607:f8b0:400b:80c::2004: time=75ms
Reply from 2607:f8b0:400b:80c::2004: time=66ms
Reply from 2607:f8b0:400b:80c::2004: time=86ms
Reply from 2607:f8b0:400b:80c::2004: time=79ms
Reply from 2607:f8b0:400b:80c::2004: time=75ms
Reply from 2607:f8b0:400b:80c::2004: time=79ms
Reply from 2607:f8b0:400b:80c::2004: time=97ms
Reply from 2607:f8b0:400b:80c::2004: time=74ms
Reply from 2607:f8b0:400b:80c::2004: time=83ms
Reply from 2607:f8b0:400b:80c::2004: time=78ms
Reply from 2607:f8b0:400b:80c::2004: time=75ms
Reply from 2607:f8b0:400b:80c::2004: time=77ms
Reply from 2607:f8b0:400b:80c::2004: time=78ms
Reply from 2607:f8b0:400b:80c::2004: time=55ms
Reply from 2607:f8b0:400b:80c::2004: time=65ms
Reply from 2607:f8b0:400b:80c::2004: time=58ms
Reply from 2607:f8b0:400b:80c::2004: time=72ms
Reply from 2607:f8b0:400b:80c::2004: time=74ms
Reply from 2607:f8b0:400b:80c::2004: time=75ms
Reply from 2607:f8b0:400b:80c::2004: time=89ms
Reply from 2607:f8b0:400b:80c::2004: time=83ms
Reply from 2607:f8b0:400b:80c::2004: time=79ms
Reply from 2607:f8b0:400b:80c::2004: time=83ms
Reply from 2607:f8b0:400b:80c::2004: time=75ms
Reply from 2607:f8b0:400b:80c::2004: time=75ms
Reply from 2607:f8b0:400b:80c::2004: time=64ms
Reply from 2607:f8b0:400b:80c::2004: time=58ms
Reply from 2607:f8b0:400b:80c::2004: time=72ms
Reply from 2607:f8b0:400b:80c::2004: time=70ms
Reply from 2607:f8b0:400b:80c::2004: time=67ms
Reply from 2607:f8b0:400b:80c::2004: time=63ms
Reply from 2607:f8b0:400b:80c::2004: time=74ms
Reply from 2607:f8b0:400b:80c::2004: time=74ms
Reply from 2607:f8b0:400b:80c::2004: time=73ms
Reply from 2607:f8b0:400b:80c::2004: time=67ms
Reply from 2607:f8b0:400b:80c::2004: time=80ms

Ping statistics for 2607:f8b0:400b:80c::2004:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 97ms, Average = 75ms

Re: High Latency + TV Micro Blocking

FedUp5000
I plan to stick around

have values over 3000ms in both my ping and traceroute tests from earlier today as well as a service that cuts out every 15 mins, but everyone still claims there are no issues....

 

when is bell available in my neighbourhood???

rogers, you are about to lose a customer since 1988

Re: High Latency + TV Micro Blocking

FedUp5000
I plan to stick around

Glad I switched to Ignite, made everything WORSE!

Was able to catch some of the spikes on cam tonight. New all time record!

While other players in my lobby (also local) have no issues.....

When I am not losing connectivity every 15 mins I now have 6000+ lag spikes and/or 40% packet loss.

Somehow no tech, network team, maintenance or anyone on this forum can find any issues?

Using the gaming console numbers to show the issues, but its happens across all devices especially at night...

 

6000ping.jpgpacket loss2.jpg

Topic Stats
  • 24 replies
  • 2256 views
  • 6 Likes
  • 4 in conversation