Helpmee
@bell.ca
|  [Internet] Bad connection at night suddenly
Ok well i factory reinstalled my computer one day due to a non relevant issue. So i hook up my internet as usual and it is working perfectly fine.
BUT at night my ping for like condition zero will jump to 300-400 which is reallllyy high and my xbox live will go down to 1 bar.
Please help. |
|
line stats
@videotron.ca
| said by Helpmee :
Please help.
Change to cable.
If you don't/can't change to cable, then post the make/model of your modem and include a tracert when the problem happens, and when it doesn't. |
|
helpmee
@bell.ca
| reply to Helpmee
I have cable and so does my xbox
Tracing route to google.ca [64.233.169.104]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms mymodem [192.168.2.1]
2 19 ms 19 ms 19 ms bas1-cooksville01_lo0_SYMP.net.bell.ca [64.230.1
97.2]
3 277 ms 279 ms 277 ms core1-toronto63_13-1-0_143.net.bell.ca [64.230.1
39.9]
4 272 ms 270 ms 267 ms core3-toronto63_POS6-0.net.bell.ca [64.230.242.1
01]
5 272 ms 279 ms 277 ms bx4-toronto63_so-0-0-0.net.bell.ca [64.230.160.1
22]
6 283 ms 281 ms 270 ms 74.125.48.89
7 271 ms 272 ms 265 ms 216.239.47.114
8 297 ms 305 ms 297 ms 216.239.43.147
9 291 ms 289 ms 293 ms 209.85.249.11
10 280 ms 281 ms 287 ms 64.233.175.111
11 294 ms 297 ms 301 ms 72.14.232.21
12 302 ms 305 ms 287 ms yo-in-f104.1e100.net [64.233.169.104]
Trace complete. |
|
kossmikman
join:2006-09-29
Montreal, QC | I'm having the same issue and judging by the title of the threads in Bell Direct forum, there seems to be quite a few folks having the same problem. |
|
Helpmee
@bell.ca | reply to Helpmee
Hopefully someone will give an answer because i cant do anything at night |
|
did u
@videotron.ca
| reply to helpmee
Just out of curiosity, you did double check for the following right:
1. Disable all start-up items
2. Disable/exit all apps that started and may be sitting in the "tray" (ie. if you see an icon in the tray, exit it).
3. Disabled wireless on your router/modem
4. Turned off any other machines connected to your network.
Then run your tracert while nothing at all is running or open.
Not saying Bell doesn't have a problem (of course they do, its Bhell), but just saying you need to eliminate everything on your end as listed above to make sure it is Bhell. |
|
STN
join:2004-12-29
Canada | reply to Helpmee
His first hop to the BAS is 19ms then it spikes. Doubtful any processes on his PC are contributing or all hops would show high latency. |
|
Bicephale
join:2005-09-24 | reply to Helpmee
Depending on the brand/model you can try to force your
DSL device to negociate lower BitRates until it connects.
You can also try a Linux LiveCD if you have reasons not
to trust your Windows station... |
|
Helpmee
@bell.ca
| reply to Helpmee
This is my tracert during the day
Tracing route to google.ca [64.233.169.104]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms mymodem [192.168.2.1]
2 24 ms 23 ms 33 ms bas1-cooksville01_lo0_SYMP.net.bell.ca [64.230.1
97.2]
3 20 ms 19 ms 17 ms core1-toronto63_13-1-0_143.net.bell.ca [64.230.1
39.9]
4 19 ms 19 ms 19 ms core3-toronto63_POS6-0.net.bell.ca [64.230.242.1
01]
5 19 ms 19 ms 17 ms bx4-toronto63_so-0-0-0.net.bell.ca [64.230.160.1
22]
6 18 ms 19 ms 19 ms 74.125.48.89
7 18 ms 19 ms 19 ms 216.239.47.114
8 37 ms 33 ms 33 ms 72.14.233.112
9 43 ms 43 ms 37 ms 209.85.248.216
10 42 ms 39 ms 43 ms 64.233.175.109
11 52 ms 44 ms 37 ms 72.14.232.21
12 38 ms 39 ms 43 ms yo-in-f104.1e100.net [64.233.169.104]
Trace complete. |
|
sbrook
Premium,Mod
join:2001-12-14
H0H 0H0
 ·Rogers Hi-Speed
Host:
Rogers
Bell Canada
| reply to Bicephale
Somebody else was reporting exactly the same problem in another thread very recently ... night time pings jump and on the hop between the bas and the next router. Only difference was it was in Montreal.
Register with the site and post your problem in the Bell Canada Direct forum. |
|
Same Problem
@bell.ca
| reply to Helpmee
Bad Connection with Internet, same spot is causing delay
I'm having bad latency when I try to connect to WoW. I did a search for core1-toronto63_13-1-0_143.net.bell.ca and found this thread.
This is how my tracert looks like during nighttime playsession (6-11pm).
Tracing route to us.logon.worldofwarcraft.com [12.129.232.109]
over a maximum of 30 hops:
1 1812 ms 1 ms 1 ms WRT54G [192.168.128.1]
2 42 ms 41 ms 45 ms bas1-cooksville01_lo0_SYMP.net.bell.ca [64.230.197.2]
3 255 ms 255 ms 256 ms core1-toronto63_13-1-0_143.net.bell.ca [64.230.139.9]
4 261 ms 268 ms 270 ms core4-toronto63_POS6-0.net.bell.ca [64.230.242.105]
5 266 ms 266 ms 265 ms bx4-toronto63_S0-6-0-0.net.bell.ca [64.230.152.190]
6 262 ms 433 ms 318 ms peer_level3_bx4-toronto63.net.bell.ca [67.69.246.190]
7 276 ms 272 ms 271 ms ae-8-8.ebr1.Chicago1.Level3.net [4.69.140.245]
8 289 ms 290 ms 292 ms ae-14-53.car4.Chicago1.Level3.net [4.68.101.72]
9 288 ms 287 ms 282 ms 192.205.33.185
10 334 ms 344 ms 333 ms cr1.cgcil.ip.att.net [12.122.133.142]
11 333 ms 331 ms 331 ms cr2.dvmco.ip.att.net [12.122.31.85]
12 335 ms 340 ms 342 ms cr1.slkut.ip.att.net [12.122.30.25]
13 346 ms 347 ms 349 ms cr2.la2ca.ip.att.net [12.122.30.30]
14 341 ms 342 ms 344 ms gar4.la2ca.ip.att.net [12.122.129.169]
15 446 ms 397 ms 399 ms 12.122.255.70
16 343 ms 349 ms 348 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254].
Then it drops off back to normal during daytimes, which is when I do not play.
Tracing route to us.logon.worldofwarcraft.com [12.129.224.115]
over a maximum of 30 hops:
1 1721 ms 2 ms 1 ms WRT54G [192.168.128.1]
2 44 ms 43 ms 41 ms bas1-cooksville01_lo0_SYMP.net.bell.ca [64.230.197.2]
3 44 ms 40 ms 48 ms core1-toronto63_13-1-0_143.net.bell.ca [64.230.139.9]
4 43 ms 42 ms 45 ms core3-toronto63_POS6-0.net.bell.ca [64.230.242.101]
5 46 ms 46 ms 46 ms bx4-toronto63_S0-5-0-0.net.bell.ca [64.230.152.186]
6 40 ms 41 ms 43 ms peer_level3_bx4-toronto63.net.bell.ca [67.69.246.190]
7 64 ms 58 ms 67 ms ae-8-8.ebr1.Chicago1.Level3.net [4.69.140.245]
8 56 ms 56 ms 57 ms ae-14-55.car4.Chicago1.Level3.net [4.68.101.136]
9 55 ms 56 ms 56 ms 192.205.33.185
10 112 ms 112 ms 111 ms cr1.cgcil.ip.att.net [12.122.133.142]
11 112 ms 111 ms 113 ms cr2.dvmco.ip.att.net [12.122.31.85]
12 115 ms 113 ms 111 ms cr1.slkut.ip.att.net [12.122.30.25]
13 111 ms 111 ms 114 ms cr2.la2ca.ip.att.net [12.122.30.30]
14 110 ms 110 ms 111 ms gar4.la2ca.ip.att.net [12.122.129.169]
15 111 ms 112 ms 111 ms 12.122.255.70
16 112 ms 111 ms 113 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254] |
|
ajatt
join:2009-11-01 | reply to Helpmee
Re: [Internet] Bad connection at night suddenly
Its the bell many people are having the same problem now for a month including me I've been told its the server we are connected to and they are working on it with no idea of how long it will take... very frustrating |
|
ragnarok3
join:2007-11-19
Mississauga, ON
| reply to Helpmee
The results from your tracert are pretty bad. You should definitely post in bell direct forum to see what they could do.
I am experiencing very high latencies during peak hours, 7-11pm in my case. It's weird though, my tracert results are good but I still get relatively high pings, so it's practically unplayable at night.
It's good to hear they said it was a server-side problem, hope it is and they get it fixed soon. |
|
nyquist
join:2009-11-05
| reply to Helpmee
from the other thread
From the other thread...
1 1 ms 1 ms 1 ms mymodem [192.168.2.1]
2 16 ms 17 ms 15 ms bas1-cooksville01_lo0_SYMP.net.bell.ca [64.230.1
97.2]
3 148 ms 155 ms 155 ms core1-toronto63_13-1-0_143.net.bell.ca [64.230.1
39.9]
4 145 ms 144 ms 151 ms core3-toronto63_POS6-0.net.bell.ca [64.230.242.1
01]
5 157 ms 154 ms 153 ms core1-chicago23_pos12-0-0.net.bell.ca [64.230.14
7.14]
6 165 ms 158 ms 165 ms bx3-chicagodt_so-0-0-0-0.net.bell.ca [64.230.203
.46]
7 169 ms 163 ms 164 ms rtp629497rts [64.230.186.134]
8 174 ms 178 ms 194 ms nyk-bb2-link.telia.net [80.91.249.111]
9 186 ms 186 ms 190 ms nyk-b3-link.telia.net [80.91.248.178]
10 195 ms 176 ms 181 ms netaccess-tic-133837-nyk-b3.c.telia.net [213.248
.99.90]
11 177 ms 174 ms 184 ms 0.e1-4.tbr1.mmu.nac.net [209.123.10.101]
12 172 ms 170 ms 172 ms 0.e1-1.tbr1.oct.nac.net [209.123.10.17]
13 184 ms 179 ms 176 ms vlan804.esd1.oct.nac.net [209.123.10.2]
14 178 ms 170 ms 173 ms www.dslreports.com [209.123.109.175]
The problem is the core1-toronto63_13-1-0_143.net.bell.ca. Something's up with that server. |
|
Helpmee
@bell.ca | reply to Helpmee
Re: [Internet] Bad connection at night suddenly
Bump come on people someone has to know a fix! |
|
sbrook
Premium,Mod
join:2001-12-14
H0H 0H0
·Rogers Hi-Speed
Host:
Rogers
Bell Canada
| This is not a problem at your end that you can fix.
This is a Bell Problem and needs Bell to fix it.
Bumping the thread will NOT get you a better answer.
You were recommended to become a registered user on the site and post your problem in the Bell Direct forum ... see the top of this forum's index page. A Bell Canada senior tech helps people who post in that forum. It is considered by Bell to be an official support channel |
|
Bicephale
join:2005-09-24
 ·TekSavvy Solutions..
| SB> This is not a problem at your end that you can fix.
I differ of opinion, maybe he can't fix it definitively but that
customer can certainly try to regain his connection during a
crisis (on a temporarily basis) while he's waiting for the final
solution... I had disconnections which lasted for hours every
single evening last year, not only did i manage with it as i've
described above but this gave me enough time to pin-point,
identify and cure the problem without ever calling Bell...
I reported my case here, read starting from August 17, 2008:
»From the ground up!
It turns out that i know today i got multiple problems but i'm
glad i could handle this by myself because one of the other
problems i have seems to be caused by a "Bridge Tap" and i
know Bell will be reluctant to fix that: their usual course of
action is to reduce the profile and that's exactly the risk this
guy takes if he doesn't clean up his own house before calling
Bell to the rescue! |
|
I differ 2
@videotron.ca
| There is a confirmed problem in some area's causing what we are seeing above. Something about roken/defective equipment causing a material defect in service.
So unless these people confirm the area they are in and if they are affected, it's not use ATM. |
|
sbrook
Premium,Mod
join:2001-12-14
H0H 0H0 | reply to Bicephale
Bicephale ... this is not a problem on his line as evidenced by his tracerts. It's between the BAS and first router. |
|
Bicephale
join:2005-09-24 | If you say so but i've seen some strange things happen lately
that make me say it's better have more evidence than less so
why not clear that matter anyway and make sure there's no
problem compound onvolved!?... |
|
