dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
7867
share rss forum feed

r5a

join:2006-02-05
Toronto, ON
reply to BliZZardX

Re: [Internet] Service outage downtown toronto?

I work in a consulting firm. I can confirm wholesalers and bell clients went down for 10 mintues all over the GTA Aug 8th between 1:50ish till now (2:05pm)

not sure if still having troubles, most of my sites (7 now) are coming back online.

Wonder what happened



techMology

@bell.ca
reply to mediajedi

said by mediajedi:

DSL FIBE 25 Toronto Beaches area, connection has been "flaky" today. Works for a while, slows down and stops. Reboot Modem, nothing happens, wait a while and things start to work again for a little while.

Ditto here. Beaches. Fibe 25. Up and down. Very annoying.


Nagilum

@bell.ca
reply to ajhaji

It looks like Bell's Torix link went down. This is a trace route during the downtime:


Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms cog-1-2-12-12.attalascom.net [12.12.2.1]
2 50 ms 47 ms 48 ms lns1-kitchener06_lo0_SYMP.net.bell.ca [64.230.199.22]
3 45 ms 44 ms 47 ms dis9-kitchener06_GE12-1-0_101.net.bell.ca [64.230.157.53]
4 46 ms 45 ms 47 ms core4-kitchener06_POS10-0-0.net.bell.ca [64.230.158.133]
5 59 ms 60 ms 58 ms core4-toronto21_pos0-0-2-0.net.bell.ca [64.230.48.96]
6 60 ms 60 ms 58 ms Ncore4-montreal02_POS0-12-0-0.net.bell.ca [64.230.147.121]
7 59 ms 56 ms 58 ms core1-quebec14_pos0-15-0-0.net.bell.ca [64.230.32.74]
8 57 ms 58 ms 58 ms dis17-quebec14_5-0-0.net.bell.ca [64.230.87.245]
9 * 68 ms * 69.156.255.222
10 * * 75 ms 172.16.244.120
11 * 76 ms * 216.113.13.33
12 * * * Request timed out.
13 * * * Request timed out.
14 * * 196 ms 72.14.214.126
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * 140 ms * google-public-dns-a.google.com [8.8.8.8]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 172 ms * * google-public-dns-a.google.com [8.8.8.8]
24 * * * Request timed out.
25 191 ms 192 ms * google-public-dns-a.google.com [8.8.8.8]
26 * * * Request timed out.
27 * * 193 ms google-public-dns-a.google.com [8.8.8.8]


Edit: Looks like the Toronto link is back up.


Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 3 ms 1 ms



Anonu

@wind.ca
reply to HiVolt

Same thing just happened where I am. Markham. Rebooted the POS sagemcom modem, synced have an ip but very few sites work.



BliZZardX
Premium
join:2002-08-18
Toronto, ON
Reviews:
·WIND Mobile
reply to BliZZardX

I had the same outage this afternoon too between 1:30 and now, about half hour. Looks like a Toronto core router went down?? All my traffic was being sent through Montreal instead.

»www.as577.net/en/page/lg.html

We'll never know...


Kraftyy

join:2010-06-19
Burlington, ON
Reviews:
·Cogeco Cable

 
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  monreseau.home [192.168.2.1]
  2     5 ms     5 ms     5 ms  bas1-hamilton01_lo0_SYMP.net.bell.ca [64.230.200
.194]
  3     5 ms     5 ms     5 ms  dis15-hamilton14_5-1-0_100.net.bell.ca [64.230.5
9.88]
  4   111 ms    17 ms    17 ms  bx5-chicagodt_xe1-0-0-0.net.bell.ca [64.230.186.
242]
  5    22 ms    24 ms    49 ms  12.249.212.9
  6    19 ms    19 ms    19 ms  cr2.cgcil.ip.att.net [12.122.132.242]
  7    28 ms    18 ms   123 ms  ggr3.cgcil.ip.att.net [12.122.132.9]
  8   285 ms   284 ms   285 ms  12.250.28.6
  9   285 ms   284 ms   284 ms  209.85.254.128
 10   285 ms   285 ms   285 ms  72.14.237.110
 11   297 ms   297 ms   296 ms  72.14.232.141
 12   297 ms   295 ms   295 ms  216.239.43.217
 13     *        *        *     Request timed out.
 14   296 ms   295 ms   295 ms  google-public-dns-a.google.com [8.8.8.8]
 
Trace complete.
 
C:\Users\Danny>
 

Tracert to the same location except I'm in hamilton. Results are weird :S


NoName777

@fibrenoire.ca
reply to BliZZardX

Seems to be from TATA communication



mrxcol

@bell.ca
reply to Kraftyy

At 14:19 it's still slow in Montreal. Some sites are loading , some slow and some don't load at all. By the way the ones that load are loading superfast (like arstechnica)!. At first only bing was responding but now google is ok.

Funny that internet.bell.ca for quebec is not responding either. But the main one (ontario) does.


resa1983
Premium
join:2008-03-10
North York, ON
kudos:10

Had an outage at work for about half an hour - nothing loaded whatsoever, not even Bell's own website.
--
Battle.net Tech Support MVP


ns1225

join:2010-12-30
Montreal, QC
reply to BliZZardX

I removed OpenDNS servers from the router and returned to default Bell servers and it appears to help or its returning to normal again.



HiVolt
Premium
join:2000-12-28
Toronto, ON
kudos:21

Looks like its back, I switched to the bell login. I did try different DNS servers when it was down, but it didnt affect it.



HiVolt
Premium
join:2000-12-28
Toronto, ON
kudos:21
Reviews:
·TekSavvy DSL
·TekSavvy Cable
reply to resa1983

said by resa1983:

Had an outage at work for about half an hour - nothing loaded whatsoever, not even Bell's own website.

I even had trouble loading Bell's website from my other line here, Rogers.

resa1983
Premium
join:2008-03-10
North York, ON
kudos:10

said by HiVolt:

said by resa1983:

Had an outage at work for about half an hour - nothing loaded whatsoever, not even Bell's own website.

I even had trouble loading Bell's website from my other line here, Rogers.

Yeah.. I pulled out my cell (Wind) to find out what the hell was going on. Bell's service status page wouldn't load at all. Finally 40 mins after it started, I was able to load it on my cell.
--
Battle.net Tech Support MVP


Kardinal
Dei Gratia Regina
Premium,Mod
join:2001-02-04
N of 49th
Reviews:
·TekSavvy DSL
·Bell Sympatico
reply to BliZZardX

I've not lost sync nor have I lost a PPPoE session, but I've had a lot of timeouts / non-loading pages and those that do load take a while to do so and then aren't complete. It's been going on since after 12 noon or so. I was wondering if it was a DNS problem, but hadn't got around to changing servers.
--
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



BliZZardX
Premium
join:2002-08-18
Toronto, ON
Reviews:
·WIND Mobile

1 recommendation

Today is a separate issue, routing related. Much bigger too.. I saw people in Miami and Atlanta asking if there are routing issues on the east coast. Bell advertised routes they didn't have to TATA, TATA releaked it to other ISPs like Comcast and took down half the internet for about an hour.

On Monday August 6 5:09 I lost DSL sync and I posted here because technical support told me it effected "my whole area" and to "just ask [my] neighbour". :P



TorontoADSL7

@bell.ca
reply to BliZZardX

What ever happened it seems that something was changed with bell connections, maybe a different route. speedtest.net using teksavvy's server I would average 13-20ping, now I am getting 52,38,37,38.


teedot

join:2008-03-04
reply to BliZZardX

Happened to us today as well... All our customers that are on Bell's network were down for about 20-30 mins. DSL, Fibre, didn't matter. Not 100% sure what happened, but it looks like they might have rerouted traffic



TSI Gabe
Router of Packets
Premium,VIP
join:2007-01-03
Gatineau, QC
kudos:7

What BliZZardX said, someone at Bell must have fat fingered a prefix filter rule and leaked a full routing table to the net. Bad things ensues.



Kardinal
Dei Gratia Regina
Premium,Mod
join:2001-02-04
N of 49th
reply to BliZZardX

It's good to know I didn't call in and get put through the "we need to check a few things" call flow chart as it would have been pointless and frustrating. Thanks for the insight.



ajhaji
Premium
join:2002-03-02
North York, ON
Reviews:
·AEI Internet
·Anveo
·voip.ms

1 edit

Any and all Google sites are excruciatingly slow. Could that be caused by this routing issue?

PING google.ca (74.125.226.88): 56 data bytes
64 bytes from 74.125.226.88: icmp_seq=0 ttl=49 time=315.245 ms
64 bytes from 74.125.226.88: icmp_seq=1 ttl=49 time=315.038 ms
64 bytes from 74.125.226.88: icmp_seq=2 ttl=49 time=315.065 ms
64 bytes from 74.125.226.88: icmp_seq=3 ttl=49 time=315.879 ms
 


BliZZardX
Premium
join:2002-08-18
Toronto, ON
Reviews:
·WIND Mobile

3 edits

Nope everything fixed itself about 2 hours ago here

@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
 

When it was messed up my trace to google exit bells network all over the place in montreal, chicago, seattle. I guess it kept switching as one location got overloaded with all the new incoming traffic. Now I am going through chicago again.


network arch

@bell.ca
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



ajhaji
Premium
join:2002-03-02
North York, ON
reply to BliZZardX

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



BliZZardX
Premium
join:2002-08-18
Toronto, ON
reply to BliZZardX

I'm out again, modem won't sync...



Kardinal
Dei Gratia Regina
Premium,Mod
join:2001-02-04
N of 49th
Reviews:
·TekSavvy DSL
·Bell Sympatico

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



BliZZardX
Premium
join:2002-08-18
Toronto, ON
Reviews:
·WIND Mobile

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.



antirealist

@bell.ca

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.



BliZZardX
Premium
join:2002-08-18
Toronto, ON
Reviews:
·WIND Mobile

4 edits
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.



uptimedown

@bell.ca

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.)


HeadSpinning
MNSi Internet

join:2005-05-29
Windsor, ON
kudos:5

said by uptimedown :

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.)

There was a widespread problem from Wed night until tonight. Apparently, something in Bell's management network was causing HDSLAMs to drop sync on ports.
--
MNSi Internet - »www.mnsi.net