O Canada! > Canadian > Bell Canada > [Internet] Service outage downtown toronto?

reply to ajhaji

Re: [Internet] Service outage downtown toronto?

@MikroTik] > tool traceroute 74.125.226.88
 # ADDRESS                                 RT1   RT2   RT3   STATUS                                                                                              
 1 64.230.200.232                          5ms   5ms   4ms                                                                                                       
 2 64.230.97.228                           5ms   4ms   4ms                                                                                                       
 3 0.0.0.0                                 0ms   0ms   0ms                                                                                                       
 4 12.249.212.9                            16ms  15ms  15ms                                                                                                      
 5 12.122.132.242                          18ms  19ms  17ms  <MPLS:L=17229,E=1,T=255>                                                                            
 6 12.122.132.9                            15ms  22ms  15ms                                                                                                      
 7 12.250.28.6                             31ms  31ms  31ms                                                                                                      
 8 209.85.254.120                          31ms  30ms  31ms                                                                                                      
 9 72.14.237.108                           31ms  31ms  30ms  <MPLS:L=501885,E=4>                                                                                 
10 216.239.46.161                          38ms  38ms  38ms                                                                                                      
11 64.233.175.98                           39ms  38ms  38ms                                                                                                      
12 74.125.226.88                           39ms  38ms  38ms
 

reply to Kraftyy
Everybody relax. I am home sympatico customer. They (Bell) have core issue. Routing loops, dead routes advertizement to peers, etc.
No valid exits from AS577 (bell). Issue begin 2012-08-08 14:xx EST . Conditions change but BGP is still out of order. Shoot those network designers and engineers. Now everybody start laughing about 99.999% network availability article on Cisco web site. Just today brought it down 100 times from 5 nines to 3 nines for us here in GTA, GTA West and some QC.

Anybody with good eyesight can see the same router/interface twice in the traceroute?

[root@localhost ~]# traceroute -A netsuite.com
traceroute to netsuite.com (167.216.129.12), 30 hops max, 60 byte packets
1 bas1-cooksville17_lo0_SYMP.net.bell.ca (64.230.197.56) [AS577] 22.091 ms 22.972 ms 23.117 ms
2 dis7-toronto01_Vlan144.net.bell.ca (64.230.202.17) [AS577] 20.921 ms 21.004 ms 20.601 ms
3 * * bx5-chicagodt_xe6-0-0.net.bell.ca (64.230.186.86) [AS577] 35.986 ms
4 newcore2-chicagocp_xe3-1-1.net.bell.ca (64.230.186.89) [AS577] 34.379 ms newcore2-chicagocp_xe3-1-0.net.bell.ca (64.230.186.85) [AS577] 34.390 ms core2-chicago23_GE5-1-0.net.bell.ca (64.230.186.245) [AS577] 32.344 ms
5 core3-toronto47_POS0-2-0-0.net.bell.ca (64.230.186.125) [AS577] 35.028 ms newcore3-toronto12_POS0-6-0-0.net.bell.ca (64.230.147.165) [AS577] 34.046 ms newcore4-toronto12_POS0-6-0-0.net.bell.ca (64.230.147.173) [AS577] 36.656 ms
6 bx4-toronto12_so-0-0-0.net.bell.ca (64.230.158.22) [AS577] 32.573 ms bx4-toronto12_so-1-1-0-0.net.bell.ca (64.230.138.114) [AS577] 32.746 ms bx4-toronto12_so-2-0-0-0.net.bell.ca (64.230.138.126) [AS577] 31.130 ms
7 core4-toronto12_POS10-0-0.net.bell.ca (64.230.158.25) [AS577] 46.275 ms newcore3-toronto12_POS0-9-1-0.net.bell.ca (64.230.152.233) [AS577] 42.250 ms 89.404 ms
8 newcore2-chicago23_so2-0-0.net.bell.ca (64.230.147.174) [AS577] 45.463 ms 45.574 ms 43.729 ms
9 bx5-chicagodt_xe-0-0-3_0.net.bell.ca (64.230.186.106) [AS577] 43.903 ms * *
10 core2-chicago23_GE5-1-0.net.bell.ca (64.230.186.245) [AS577] 68.840 ms newcore1-chicagocp_xe-4-0-0_0.net.bell.ca (64.230.186.105) [AS577] 45.184 ms core2-chicago23_GE5-1-0.net.bell.ca (64.230.186.245) [AS577] 68.929 ms
11 core4-toronto47_POS0-2-0-0.net.bell.ca (64.230.186.117) [AS577] 47.921 ms newcore4-toronto12_POS0-6-0-0.net.bell.ca (64.230.147.173) [AS577] 47.606 ms core3-toronto47_POS0-2-0-0.net.bell.ca (64.230.186.125) [AS577] 47.700 ms
12 bx4-toronto12_so-2-0-0-0.net.bell.ca (64.230.138.126) [AS577] 45.104 ms bx4-toronto12_so-0-0-0.net.bell.ca (64.230.158.22) [AS577] 40.907 ms bx4-toronto12_so-1-1-0-0.net.bell.ca (64.230.138.114) [AS577] 47.150 ms
13 newcore3-toronto12_POS0-9-1-0.net.bell.ca (64.230.152.233) [AS577] 57.398 ms core4-toronto12_POS10-0-0.net.bell.ca (64.230.158.25) [AS577] 80.450 ms newcore3-toronto12_POS0-9-1-0.net.bell.ca (64.230.152.233) [AS577] 57.138 ms
14 newcore2-chicago23_so2-0-0.net.bell.ca (64.230.147.174) [AS577] 55.089 ms newcore1-chicago23_so2-0-0.net.bell.ca (64.230.147.166) [AS577] 54.903 ms 57.737 ms
15 * bx5-chicagodt_xe6-0-0.net.bell.ca (64.230.186.86) [AS577] 53.109 ms 54.635 ms
16 core1-chicago23_GE8-1-0.net.bell.ca (64.230.186.241) [AS577] 57.180 ms 52.909 ms newcore1-chicagocp_xe3-1-0.net.bell.ca (64.230.186.77) [AS577] 54.966 ms
17 core4-toronto47_POS0-2-0-0.net.bell.ca (64.230.186.117) [AS577] 56.167 ms core3-toronto47_POS0-2-0-0.net.bell.ca (64.230.186.125) [AS577] 58.777 ms newcore4-toronto12_POS0-6-0-0.net.bell.ca (64.230.147.173) [AS577] 58.822 ms
18 bx4-toronto12_so-1-1-0-0.net.bell.ca (64.230.138.114) [AS577] 58.440 ms bx4-toronto12_so-2-0-0-0.net.bell.ca (64.230.138.126) [AS577] 57.638 ms 55.711 ms
19 newcore3-toronto12_POS0-9-1-0.net.bell.ca (64.230.152.233) [AS577] 68.786 ms core4-toronto12_POS10-0-0.net.bell.ca (64.230.158.25) [AS577] 72.675 ms newcore3-toronto12_POS0-9-1-0.net.bell.ca (64.230.152.233) [AS577] 61.698 ms
20 newcore2-chicago23_so2-0-0.net.bell.ca (64.230.147.174) [AS577] 67.651 ms newcore1-chicago23_so2-0-0.net.bell.ca (64.230.147.166) [AS577] 62.683 ms 61.140 ms
21 * * bx5-chicagodt_xe3-1-0-0.net.bell.ca (64.230.186.246) [AS577] 68.873 ms
22 newcore1-chicagocp_xe3-1-0.net.bell.ca (64.230.186.77) [AS577] 97.206 ms newcore2-chicagocp_xe3-1-0.net.bell.ca (64.230.186.85) [AS577] 75.756 ms newcore1-chicagocp_xe3-1-1.net.bell.ca (64.230.186.81) [AS577] 91.669 ms
23 newcore3-toronto12_POS0-6-0-0.net.bell.ca (64.230.147.165) [AS577] 63.376 ms core4-toronto47_POS0-2-0-0.net.bell.ca (64.230.186.117) [AS577] 71.214 ms 68.905 ms
24 bx4-toronto12_so-1-1-0-0.net.bell.ca (64.230.138.114) [AS577] 69.463 ms 70.131 ms bx4-toronto12_so-0-0-0.net.bell.ca (64.230.158.22) [AS577] 61.383 ms
25 newcore3-toronto12_POS0-9-1-0.net.bell.ca (64.230.152.233) [AS577] 75.963 ms core4-toronto12_POS10-0-0.net.bell.ca (64.230.158.25) [AS577] 88.234 ms 86.558 ms
26 newcore1-chicago23_so2-0-0.net.bell.ca (64.230.147.166) [AS577] 79.111 ms 79.737 ms newcore2-chicago23_so2-0-0.net.bell.ca (64.230.147.174) [AS577] 86.221 ms
27 * * *
28 newcore1-chicagocp_xe3-1-1.net.bell.ca (64.230.186.81) [AS577] 81.901 ms newcore1-chicagocp_xe3-1-0.net.bell.ca (64.230.186.77) [AS577] 82.010 ms newcore2-chicagocp_xe-4-0-0_0.net.bell.ca (64.230.186.109) [AS577] 88.821 ms
29 newcore3-toronto12_POS0-6-0-0.net.bell.ca (64.230.147.165) [AS577] 74.955 ms 76.384 ms core3-toronto47_POS0-2-0-0.net.bell.ca (64.230.186.125) [AS577] 82.947 ms
30 bx4-toronto12_so-1-0-0.net.bell.ca (64.230.158.26) [AS577] 85.575 ms bx4-toronto12_so-1-1-0-0.net.bell.ca (64.230.138.114) [AS577] 82.072 ms 79.211 ms

reply to BliZZardX
The problem is resolved for me as of about 5 minutes ago.

reply to BliZZardX
I'm out again, modem won't sync...

I've been having re-syncs or re- log ins since this thread started, when I used to go for literally months and months on the same log in session. It's quite annoying, but I haven't been able to pick out a pattern of when it's happening....it's randomly random.
--
All of us get lost in the darkness, dreamers learn to steer by the stars
All of us do time in the gutter, dreamers turn to look at the cars
- Peart / Lifeson / Lee
Join Team Helix

I checked with a neighbour again and their modem is online. So it must be just me. I went through all the troubleshooting stuff again with the test centre and we didn't solve anything so a tech is coming tomorrow..

I tried 2 modems, no sync. We even went and tried ADSL2+ profiles with no success, it's like there's no signal coming through the wire. I had 2 months+ uptime and the only incidents were August 6 (lost sync/unknown line issue), August 8 (Dery Telecom incident) and today (lost sync/unknown line issue). I didn't touch anything so I have no idea what's going on.
--
Fiber Optics are the future of high-speed internet access. Stop by the BBR »Fiber Optic Forum.

I've been having this problem for over a week now, and today has been particularly bad, with loss of sync every 10 mins or so, sometimes lasting more than 30 mins.

Bell pointlessly sent round a tech on Monday, even though the issue was clearly at the DSLAM, and wasted a couple of hours of his time, and a whole morning of mine. It seems that the port is defective, but they're doing some infrastructure upgrades and can't/won't migrate me to a new port until that work is completed - I believe Project Waikiki was mentioned.

So they expect me to put up with - and pay for - a barely usable service for an indefinite period with the expectation that things may return to the way they were at some future point. My DSL sync actually dropped twice while I was typing this post.

reply to BliZZardX
So it turns out someone physically disconnected my wires in the phone room by accident. Tech came today and reconnected it, but my speed is way worse than before. Loop length DOUBLED and my line stats turned to shit

US Aggregate Power : -11.9 dbm
DS Attainable Data Rate: 38292 kbps
US Attainable Data Rate: 5464 kbps

WTF. Before yesterday that was 90Mbps down and 9Mbps up »pastebin.com/raw.php?i=ndm3hdjf. I'm on the phone with the test centre and the guy won't send another technician because "our tool says 5Mbps is all your line can handle". His supervisor said the same thing. Well your damn tool is wrong. What dicks. I'm going through the business office instead, they seem to be a little more competent.

Today, for the first time in years, I'm having loss of sync problems in Kitchener. Arrrgg! And so far, no message on 310-SURF as to problems in the area.
My DSLAM is in the Kingsway CO (not on a remote) and POTS service is working without problems, so all signs point to a BHell problem...
('been a customer since 1999, I'm a tech myself with extensive experience, etc.)

reply to BliZZardX
Original: Downstream attainable line rate: 92032 kbps
This afternoon: Downstream attainable payload rate: 37856 kbps
This evening: Downstream attainable payload rate: 54284 kbps

Ok, this 2nd tech tried to fix things, although he still didn't restore it to original condition. He says my original port was fried (!). That sounds a bit different than my wires were disconnected doesn't it? Nobody can get this story straight.

Now I can sync at 25/10, but I'm on interleave. I tried to get it turned off, but he claimed he didn't know what I was talking about. Going to eat some dinner then wait on hold for 2 hours, be right back.
--
Fiber Optics are the future of high-speed internet access. Stop by the BBR »Fiber Optic Forum.

Actually got somebody helpful on the first try. Now I can go to sleep peacefully.

Extended Port Status
=================
Bme: 1 Port: 1
Downstream line rate: 29424 kbps
Upstream line rate: 13004 kbps
Bearer0 Downstream payload rate: 0 kbps
Bearer1 Downstream payload rate: 26928 kbps
Bearer0 Upstream payload rate: 0 kbps
Bearer1 Upstream payload rate: 11320 kbps
Downstream attainable payload rate: 57688 kbps
Downstream attainable line rate: 67684 kbps
Downstream Training Margin: 20.1 dB
Downstream Line Protection (Bearer1 Path): 0.0 DMT Symbols
Upstream Line Protection (Bearer1 Path): 0.0 DMT Symbols
Near-end ITU Vendor Id: 0xb500494b4e530200
Far-end ITU Vendor Id: 0xb500494b4e530100
Downstream delay: 0.0 ms
Upstream delay: 0.0 ms
Tx total power -18.8 dbm
FE Tx total power 14.2 dbm
VDSL Estimated Loop Length : 693 ft
G.Hs Estimated Near End Loop Length : 234 ft
G.Hs Estimated Far End Loop Length :592 ft
Current framing mode: 0x10 EFM
Bandplan Type...........: 2
No. of Upstream Bands...: 2
No. of Downstream Bands.: 2
Line Type: 0x01000000 VDSL2 Profile 12A
Downstream FFT Protection (Bearer1 Path): 0.0 DMT Symbols
Upstream FFT Protection (Bearer1 Path): 0.0 DMT Symbols
Upstream Line Attenuation: NA (Only for ADSL1 & T1.413)
Upstream SNR Margin: NA (Only for ADSL1 & T1413)
Upstream Retransmission status: Disabled
Downstream Retransmission status: Disabled
--
Fiber Optics are the future of high-speed internet access. Stop by the BBR »Fiber Optic Forum.

reply to antirealist
Down dozens of times again today, with brief episodes of uptime. Called Bell again, and got a callback from a higher service centre. Why don't they familiarize themselves with the problem before they call you about it? No improvement. In fact the service is much worse than when I originally opened the ticket a week ago.

reply to BliZZardX
well I'm in brockville via Kingston bas I get 1000 ms + ping intermittently. gaming horror lol

been like this for the past week but they were unhappy when I did not pay my bill till they fixed it
--
To be or not to be is just a question its what you do that gives you the answer

reply to antirealist

Yes, it's still happening. As I said, the linecard I'm assigned to is faulty. For some reason of their own, Bell doesn't want to migrate me to another one just yet.

reply to BliZZardX
I found this guide that explains SNR levels for DSL. Higher is better: »Windstream DSL FAQ »Modem DSL Statistics? What do the SNR and ATTN numbers show me about my line?

My SNR:
Original: Downstream Training Margin: 29.9 dB
After the 1st tech half complete his job: Downstream Training Margin: 11.7 dB
After the 2nd tech did a card swap: Downstream Training Margin: 20.5 dB

I don't know how reconnecting my wire aka swapping line cards means I lost almost 9.4 dB but I'm not pleased about it. So far no disconnections.

antirealist the tech here last night claims he installed a new line card so it should be possible. Are you on a VDSL2 with a Stinger too? What's your SNR?
--
Fiber Optics are the future of high-speed internet access. Stop by the BBR »Fiber Optic Forum.

Many previous techs that have been here also mentioned that the phone room in my building is messy, there's lots of labels missing on the distribution block and the Stinger pumps out a lot of heat. The tech last night said the same thing. I'm waiting for the day those guys read my signature and stop replacing $2000 line cards because a chip fried from bad/no climate control.
--
Fiber Optics are the future of high-speed internet access. Stop by the BBR »Fiber Optic Forum.

reply to BliZZardX
I don't even know where the CO is, let alone what kind of multiplexer I'm hooked up to. Reading between the lines, I suspect that my DSLAM is being taken out of service as part of the infrastructure upgrade. They'd rather wait for that to happen than solve my immediate problem. Unfortunately for me, the timing of the changeover keeps getting delayed - it was supposed to happen a week ago.

I'm leaving for a week on Sunday, and I told Bell that if the issue wasn't resolved when I returned, I'd have to change providers.

No sync for >5 hours now, I assume the line card has finally died. Called Bell again. They don't understand why nothing has been done, but they confirmed that there has been no action on this ticket which has been open for 8 days. A supervisor will call me back, but they don't expect that they can get it resolved this weekend...

I'm using up a lot of cellular data today.