dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
7915
share rss forum feed


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

[Internet] Service outage downtown toronto?

I'm by Front St. and my modem lost sync at 5:09 pm. Then about an hour later my phone dropped from lte to hspa. Anybody know what's going on?
--
Fiber Optics are the future of high-speed internet access. Stop by the BBR »Fiber Optic Forum.


Torontonian

@74.198.9.x
TekSavvy dsl down here as of about 4pm(bell fibe lines) Dundas and Sherbourne


StuckInTO

@stsn.com
reply to BliZZardX
Us too at Sherbourn and Richmond. Right now I'm stuck tethering out on Mobilicity. Our modem was already down when I got home around 6 pm. Tried restarting the modem several times, with no luck. Does anybody know what happened...or more importantly, does anyone have an ETA on a resolution?


Thane_Bitter
Inquire within
Premium
join:2005-01-20
Reviews:
·Bell Sympatico
reply to BliZZardX
According to Bell's status page
»internet.bell.ca/index.cfm?metho···cestatus
"Customers in the following areas may be experiencing service interruptions:
•Ajax
•Montreal
•Plaisance
•Richmond Hill
•Verdun
•Stouffville
•Toronto
•Barrie

We apologize for any inconvenience."


BliZZardX
Premium
join:2002-08-18
Toronto, ON
I thought they changed my DSLAM or something, I even plugged my Sagemcom back in but it still wouldn't sync.

I checked Bell's status page and Toronto wasn't listed, they must have updated it hours later.

When I called in someone wrote a note that it should be fixed by 11pm. I dunno if it came back at exactly that time but I just woke up in the middle of the night (now 03:30) and everything is working again ... glad to know it wasn't just me. Wonder what happened.
--
Fiber Optics are the future of high-speed internet access. Stop by the BBR »Fiber Optic Forum.


sys0

@supralink.com
still down here in mississauga.


Torontonian

@74.198.9.x
reply to BliZZardX
Still out here.. WTF.


BliZZardX
Premium
join:2002-08-18
Toronto, ON
You guys might have another issue? are your lines normally stable? I had over 2 months uptime until last night


Thane_Bitter
Inquire within
Premium
join:2005-01-20
Reviews:
·Bell Sympatico
reply to BliZZardX
It's not a very informative page, I believe someone (an employee of Bell or one of its subcontractors) must input the areas which are experiencing issues; it is not automated and probably is filled out based on the number of irate customers calling in seeking help & resolution.

I agree with you, it would be nice if they could convey useful knowledge and information rather than the endless platitude of apologies and regrets.

They might as well dump all front row CSR and have EMILY say “I am sorry, I am not programmed to respond to that inquiry”.


Torontonian

@74.198.9.x
I managed to get some answers from Bell tech support overnight without giving a phone number.. They verified service outages "in the 416" (the guy was in India for sure, the communication level was so bad I had to ask to speak with another rep - who ended up being equally as terrible), then again in another conversation this morning, the woman I was speaking with said some lines were down because of a storm, and that is what was is causing outages around the Provence (sounds like a dismissive excuse to get customers off the phone IMO).

Also, I spoke with TekSavvy around noon today.. Apparently most of their issues had to do with a password reset at one of the connection hubs (or something like that.. I don't know how this stuff works) which resulted in customers DSL light to be on, but no data flow.

I was told that issue was resolved early this morning, requiring customers to simply re-enter their username and password in the modem menu to get back online.

Unfortunately this did not fix my issue, and my service is still down... And considering my DSL light is on, Bell lines being down could not be my issue either.

That being said, the issue is definitely on the Bell end of things.. And the way things work, TekSavvy is at the mercy of Bell in terms of there is nothing TekSavvy can do but wait for Bell to fix the problem.. so anyone hating on TekSavvy right now should pull their head out of the sand and look at what is really going on.

Also, I would like to report that though sometimes it takes a while to get through to TekSavvy support, my conversations have always been at a very high level of communication, with a person who is both informed, and cares about helping customers.

The wait times are just a result of TekSavvy having so many new customers (people like myself who were tired of getting price gauged by Bell or Rogers), and they are having a tough time keeping up..

I advise anyone reading this to really think twice before believing the bad reviews about TekSavvy that have been going up on the web.. Chances are Rogers and Bell are paying someone to write them.


BliZZardX
Premium
join:2002-08-18
Toronto, ON
I got a call back from the Test Centre this afternoon. They asked me if my connection was back up so they can close the ticket, and I said yes it's working fine now. He said weird because its showing down on his end. WTF? Anyway I asked what caused the outage, and he couldn't answer. Totally clueless. There's really bad internal communication at Bell.


yyzlhr

@rogers.com
reply to Torontonian
said by Torontonian :

I advise anyone reading this to really think twice before believing the bad reviews about TekSavvy that have been going up on the web.. Chances are Rogers and Bell are paying someone to write them.

Relax. Bell and Rogers do not pay people to write any sort of reviews.


HiVolt
Premium
join:2000-12-28
Toronto, ON
kudos:21
Bell just died here, just east of downtown...

Still have sync, have an IP, but nothing works. I reconnect and same thing.

Other ISP login works, thank god.
--
GO BLUE JAYS!



ajhaji
Premium
join:2002-03-02
North York, ON
My Bell connection is doing the exact same thing. It seems to be stabilizing now...

Kraftyy

join:2010-06-19
Burlington, ON
My bell inet just went down 30 minutes ago same thing as you guys except I'm east hamilton rosedale area


AMailer
Aaron DM

join:2004-04-03
reply to BliZZardX
I seem to be affected as well. Connection seems to be normal at times and then just dies.

mediajedi

join:2011-12-23
Toronto, ON
reply to BliZZardX
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.

ns1225

join:2010-12-30
Montreal, QC
reply to BliZZardX
Something odd is going on here in downtown Montreal as well. I can load the Globe and Mail but other websites are intermittent. DSL Reports still works though.

smoki

join:2000-10-19
Oakville, ON
reply to BliZZardX
Same with Oakville, some sites work some dont...

Kraftyy

join:2010-06-19
Burlington, ON
Reviews:
·Cogeco Cable
reply to ns1225
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
C:\Users\Danny>tracert 199.107.24.244
 
Tracing route to 199.107.24.244 over a maximum of 30 hops
 
  1    <1 ms    <1 ms    <1 ms  monreseau.home [192.168.2.1]
  2     5 ms     4 ms     5 ms  bas1-hamilton01_lo0_SYMP.net.bell.ca [64.230.200
.194]
  3     5 ms     4 ms     4 ms  dis15-hamilton14_5-1-0_100.net.bell.ca [64.230.5
9.88]
  4    17 ms    17 ms    17 ms  bx5-chicagodt_xe1-0-0-0.net.bell.ca [64.230.186.
242]
  5    18 ms    18 ms    18 ms  12.249.212.9
  6    32 ms    34 ms    33 ms  cr1.cgcil.ip.att.net [12.122.99.22]
  7    34 ms    35 ms    34 ms  cr1.cl2oh.ip.att.net [12.122.2.206]
  8    33 ms    34 ms    31 ms  cr2.cl2oh.ip.att.net [12.122.2.126]
  9    35 ms    33 ms    35 ms  cr2.phlpa.ip.att.net [12.122.2.210]
 10    31 ms    31 ms    31 ms  gar1.pitpa.ip.att.net [12.122.107.85]
 11    38 ms    35 ms    38 ms  12-122-254-242.attens.net [12.122.254.242]
 12    36 ms    38 ms    35 ms  mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.24
0.65.14]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *
 

Hop 5 paused for a long time maybe the cause of the hanging. (Pinged a WoW server)

r5a

join:2006-02-05
Toronto, ON
reply to BliZZardX
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
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.