dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1413
share rss forum feed


UKD

@teksavvy.com

[Internet] Weekday Evening DSL High Ping

Hi.

I'd like to hear from Bell customers on DSL in the North Bay, ON area.

Do you experience a changed internet experience Monday to Friday, approximately 7pm to 11pm? Specifically, a 10-fold to 30-fold increase in your latency/ping response times, slow page load times, or large online gaming lag.

I'm specifically looking for people on Bell's own ISP packages, not a 3rd party i.e Teksavvy.

Also, I am specifically looking for issues like this which occur on weekday evenings, but NOT at weekends. It is also important that during daytime hours, your experience is one of low latency, usable, connections.

Thanks.


Powassan

@bell.ca
I'm from Powassan (20 minutes south of North Bay) and have that issue, it started as far back as 6 months ago, I'd say between 5-11pm...

My ping is between 15-50ms at all other hours of the day, 5 o'clock rolls around and my ping has spiked as high as 1400ms.

I've contacted Bell numerous times, one guy said it was my computer (it's brand new, so clearly not) another told me there was nothing wrong (again, clearly there is)...

I'm not sure if it's okay on the weekends, I'll do a speedtest tommorrow and see.


fvd

@primus.ca
I'm not in your area but I do see the same issue at those times for the past month or so. It seems like its a congestion problem since that's peak times.


Glen1
These Are The Good Ol' Days.
Premium,MVM
join:2002-05-24
GTA Canada
kudos:8
Reviews:
·Bell Fibe

1 edit
reply to UKD
You are probably right about the latency issue...not being in North Bay I cannot help but if you do a tracert to a specific IP address or domain during the two periods of time and then post them here to show where the slow down occurs that might help. Sometimes the network guys come here to look for issues, they work at a department that used to be called "Inoc" and they may help. I believe it is the "internet network operations center" but that is only a guess. Historically others have done the same on this site and it has had a positive effect...give it a try.

Example: tracert www.dslreports.com

Tracing route to www.dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 2 ms 3 ms 2 ms RT-0026f2cb27d0 [192.168.1.1]
2 200 ms 214 ms 229 ms 206.248.154.104
3 278 ms 175 ms 2120.ae0.bdr01.tor.packetflow.ca [69.196.136.66]
4 82 ms 195 ms 268 ms peer1.bdr02.tor.packetflow.ca [64.34.236.121]
5 227 ms 238 ms 248 ms 10ge.xe-0-3-0.nyc-telx-dis-1.peer1.net [216.187.114.194]
6 214 ms 223 ms nyiix.e-1-4.tbr2.tl9.nac.net [198.32.160.20]
7 216 ms 239 ms 191 ms 0.e3-2.tbr2.tl9.nac.net [209.123.11.145]
8 174 ms 234 ms 149 ms 0.e1-4.tbr2.mmu.nac.net [209.123.10.77]
9 115 ms 189 ms 266 ms 0.e1-1.tbr2.oct.nac.net [209.123.10.21]
10 197 ms 237 ms vlan808.esd1.oct.nac.net [209.123.10.42]
11 183 ms 211 ms 247 ms www.dslreports.com [209.123.109.175]

Trace complete
--
My Canada includes Quebec.
Disclaimer: If I express an opinion, it is my own opinion, not that of Bell or its related companies.


Powassan

@bell.ca
reply to UKD
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms homeportal [192.168.2.1]
2 801 ms 811 ms 858 ms 64.230.197.160
3 1027 ms 1156 ms 994 ms dis5-sudbury98_Vlan101.net.bell.ca [64.230.226.1
7]
4 935 ms 872 ms 819 ms bx5-chicagodt_xe-0-0-3_0.net.bell.ca [64.230.186
.106]
5 854 ms 854 ms 866 ms xe-1-0-6.ar2.ord1.us.nlayer.net [69.31.111.97]
6 717 ms 797 ms 1010 ms ae4-52.cr1.ord1.us.nlayer.net [69.31.111.145]
7 865 ms 734 ms 908 ms xe-5-3-0.cr1.ewr1.us.nlayer.net [69.22.142.75]
8 1013 ms 1138 ms 945 ms ae1-70g.ar2.ewr1.us.nlayer.net [69.31.94.118]
9 780 ms 617 ms 577 ms as8001.xe-3-0-6.ar2.ewr1.us.nlayer.net [69.31.95
.130]
10 565 ms 620 ms 695 ms 0.e1-4.tbr1.oct.nac.net [209.123.10.122]
11 737 ms 742 ms 663 ms vlan804.esd1.oct.nac.net [209.123.10.2]
12 1131 ms 1176 ms 1217 ms www.dslreports.com [209.123.109.175]

Trace complete.

I'm about to change to Teksavvy, although I doubt that'll do anything as they run off Bell's infrastructure... I'm just tired of getting dicked around by Bell and paying double for half the amount of GB. Shame there isn't more options when it comes to Internet and television, I'd love to get Bell completely out of my life!


Powassan

@bell.ca
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms homeportal [192.168.2.1]
2 1130 ms 1209 ms 1236 ms 64.230.197.160
3 1474 ms 1406 ms 1461 ms dis5-sudbury98_Vlan101.net.bell.ca [64.230.226.1
7]
4 1312 ms 1349 ms 1473 ms bx5-chicagodt_xe-0-0-3_0.net.bell.ca [64.230.186
.106]
5 1641 ms 1376 ms 1682 ms xe-1-0-6.ar2.ord1.us.nlayer.net [69.31.111.97]
6 1633 ms 1586 ms 1437 ms ae4-52.cr1.ord1.us.nlayer.net [69.31.111.145]
7 1661 ms 1678 ms 1382 ms xe-5-3-0.cr1.ewr1.us.nlayer.net [69.22.142.75]
8 1463 ms 1485 ms 1670 ms ae1-70g.ar2.ewr1.us.nlayer.net [69.31.94.118]
9 1003 ms 1049 ms 1134 ms as8001.xe-3-0-6.ar2.ewr1.us.nlayer.net [69.31.95
.130]
10 1221 ms 1171 ms 1264 ms 0.e1-4.tbr1.oct.nac.net [209.123.10.122]
11 1559 ms 1560 ms 1650 ms vlan804.esd1.oct.nac.net [209.123.10.2]
12 1545 ms 1556 ms 1780 ms www.dslreports.com [209.123.109.175]

Trace complete.

Here's another at 7pm, around the time I get the worst ping... This is just retarded!


Glen1
These Are The Good Ol' Days.
Premium,MVM
join:2002-05-24
GTA Canada
kudos:8
reply to UKD
Did you get a chance to do a tracert when the network is better?


xsbell

join:2008-12-22
Canada
kudos:8
Reviews:
·Primus Telecommu..
reply to UKD
They are both still on Bell's legacy ATM network. If they used the test@test login and tested latency to Bell's BAS (10.x.x.1), they would get the same high latency.

It's probably their DSLAM uplink(s).. I had the same issue about a year and a half ago.


Powassan

@bell.ca
reply to Glen1
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms homeportal [192.168.2.1]
2 12 ms 13 ms 15 ms 64.230.197.160
3 11 ms 11 ms 11 ms dis5-sudbury98_Vlan101.net.bell.ca [64.230.226.1
7]
4 30 ms 30 ms 60 ms bx5-chicagodt_xe-0-0-3_0.net.bell.ca [64.230.186
.106]
5 32 ms 34 ms 34 ms xe-1-0-6.ar2.ord1.us.nlayer.net [69.31.111.97]
6 31 ms 30 ms 31 ms ae4-52.cr1.ord1.us.nlayer.net [69.31.111.145]
7 39 ms 40 ms 40 ms xe-5-3-0.cr1.ewr1.us.nlayer.net [69.22.142.75]
8 43 ms 46 ms 42 ms ae1-70g.ar2.ewr1.us.nlayer.net [69.31.94.118]
9 40 ms 50 ms 48 ms as8001.xe-3-0-6.ar2.ewr1.us.nlayer.net [69.31.95
.130]
10 39 ms 40 ms 41 ms 0.e1-4.tbr1.oct.nac.net [209.123.10.122]
11 39 ms 40 ms 40 ms vlan804.esd1.oct.nac.net [209.123.10.2]
12 40 ms 40 ms 40 ms www.dslreports.com [209.123.109.175]

Trace complete.

And I was told by Bell tech support theres nothing wrong... HA!

millsy200

join:2012-08-28
Reviews:
·TekSavvy DSL
reply to xsbell
You say you HAD this problem, how did it go about being fixed. I have had this "congestion issue" for over a year now and still no fix in sight...

Tracing route to www.dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 585 ms 594 ms 647 ms 206.248.154.104
3 615 ms 686 ms 579 ms 2110.ae0.bdr01.tor.packetflow.ca [69.196.136.34]

4 571 ms 608 ms 616 ms peer1.bdr02.tor.packetflow.ca [64.34.236.121]
5 685 ms 720 ms 668 ms nyc-telx-dis-1-re0.peer1.net [216.187.115.33]
6 535 ms 598 ms 680 ms 198.32.160.20
7 534 ms 566 ms 681 ms 0.e3-2.tbr1.tl9.nac.net [209.123.11.141]
8 628 ms 448 ms 444 ms 0.e1-4.tbr1.mmu.nac.net [209.123.10.101]
9 598 ms 668 ms 700 ms 0.e1-1.tbr1.oct.nac.net [209.123.10.17]
10 548 ms 544 ms 609 ms vlan804.esd1.oct.nac.net [209.123.10.2]
11 713 ms 595 ms 504 ms www.dslreports.com [209.123.109.175]

Trace complete.

eeeaddict

join:2010-02-14
reply to Powassan
that actually looks pretty standard what is wrong?