Congestion issue in south Etobicoke

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
Highlighted
I've Been Around
Posts: 1

Congestion issue in south Etobicoke

Does anyone know when/(if?) the congestion will be resolved in south Etobicoke(Royal York/Lakeshore area). My download speed is down to less than 1Mbit in the evenings(I'm paying for extreme Plus).This has been going on for over a week now....Hopefully Rogers will give me some sort of a break on my bill...

 

 

***edited labels***

Highlighted
I've Been Here Awhile
Posts: 3

Re: Congestion issue in south Etobicoke

I'm a block away and my speed is blazing fast. Sorry...

Highlighted
Resident Expert
Resident Expert
Posts: 14,190

Re: Congestion issue in south Etobicoke

The original poster posted almost a year and a half ago... May not be an issue anymore 🙂


Highlighted
I Plan to Stick Around
Posts: 20

Re: Congestion issue in south Etobicoke

For the past few days now, internet speed has been very erratic.  Sites like SpeedTest and such report everything's fine, but real world tests are quite different.

 

Runninging traces, I've found a couple hops within the Rogers network that seem to be the culprit

 

7.11.163.21 (7.11.163.21) 103.574 ms 44.841 ms 157.061 ms

 

and

 

van58-9-230-26.dynamic.rogerstelecom.net (209.148.230.26) 154.108 ms 39.457 ms 148.874 ms

 

Both these hops regularly have reponse times over 100ms.  The 7.11.163.21 is always the second hop, while the van58 point is usually the 5th hop.

 

I've opened a ticket, but wanted to see if anyone else has been having trouble.

 

Here are some more traces.

 

traceroute to facebook.com (173.252.120.6), 64 hops max, 52 byte packets
1 router.asus.com (192.168.1.240) 2.272 ms 2.278 ms 2.377 ms
2 7.11.163.21 (7.11.163.21) 81.079 ms 124.210 ms 22.213 ms
3 209.148.245.229 (209.148.245.229) 23.800 ms 135.290 ms 113.074 ms
4 69.63.248.185 (69.63.248.185) 66.520 ms 81.819 ms 60.340 ms
5 * 24.156.144.178 (24.156.144.178) 58.067 ms 36.101 ms
6 ae6.pr02.ord1.tfbnw.net (103.4.96.134) 62.943 ms * *
7 be20.bb02.ord1.tfbnw.net (74.119.77.138) 179.204 ms 188.214 ms
be20.bb01.ord1.tfbnw.net (74.119.77.134) 67.788 ms
8 be38.bb01.frc3.tfbnw.net (31.13.25.106) 295.243 ms 89.676 ms 155.764 ms
9 ae29.dr06.frc3.tfbnw.net (31.13.27.163) 92.107 ms
ae61.dr01.frc3.tfbnw.net (173.252.64.55) 459.434 ms
ae60.dr03.frc3.tfbnw.net (74.119.79.11) 141.596 ms
10 * * *
11 * * *
12 edge-star-shv-12-frc3.facebook.com (173.252.120.6) 67.654 ms 120.148 ms 125.794 ms

 

traceroute to googlemail.l.google.com (74.125.226.117), 64 hops max, 52 byte packets
1 router.asus.com (192.168.1.240) 2.369 ms 2.220 ms 2.193 ms
2 7.11.163.21 (7.11.163.21) 38.944 ms 113.690 ms 86.506 ms
3 209.148.245.225 (209.148.245.225) 33.223 ms 157.876 ms 144.365 ms
4 69.63.248.181 (69.63.248.181) 42.411 ms 138.719 ms 124.113 ms
5 209.148.224.246 (209.148.224.246) 148.445 ms 112.003 ms 160.960 ms
6 72.14.222.87 (72.14.222.87) 227.948 ms 124.202 ms 41.988 ms
7 216.239.47.114 (216.239.47.114) 117.099 ms 28.253 ms 45.589 ms
8 209.85.250.207 (209.85.250.207) 78.318 ms 82.752 ms 200.520 ms
9 yyz08s13-in-f21.1e100.net (74.125.226.117) 63.185 ms 33.173 ms 80.478 ms

 

There obviously shouldn't be such high latency so early in the route.

 

***Edited Labels***

Highlighted
I Plan to Stick Around
Posts: 20

Re: Congestion issue in south Etobicoke

The node just keeps getting worse.

 

traceroute to youtube.com (24.156.153.55), 64 hops max, 52 byte packets
1 router.asus.com (192.168.1.240) 2.502 ms 0.640 ms 4.309 ms
2 7.11.163.21 (7.11.163.21) 197.142 ms * *
3 209.148.245.229 (209.148.245.229) 63.883 ms 27.387 ms 18.790 ms
4 69.63.248.185 (69.63.248.185) 24.363 ms * 687.762 ms
5 * 69.63.252.249 (69.63.252.249) 39.763 ms 615.367 ms
6 * * *

 

Now it's timing out the majority of the time.  I really hope this gets fixed soon.  

 

EDIT (2:18AM):

 

As of about 15min ago, my speed situation has changed.  The second hop has changed in my route and appears to be blocking ICMP.  Regardless, my response times are much better.

 

traceroute to youtube.com (66.185.85.45), 64 hops max, 52 byte packets
1 router.asus.com (192.168.1.240) 2.492 ms 2.280 ms 2.396 ms
2 * * *
3 209.148.245.237 (209.148.245.237) 26.956 ms 21.686 ms 20.601 ms
4 69.63.248.185 (69.63.248.185) 18.619 ms 16.825 ms 20.073 ms
5 69.63.249.78 (69.63.249.78) 76.271 ms 17.509 ms 19.977 ms

 

We'll see if this keeps up or if it's just a fluke.