dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
11

yyzlhr
@rogers.com

yyzlhr to Torontonian

Anon

to Torontonian

Re: [Internet] Service outage downtown toronto?

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 Member
join:2000-12-28
Toronto, ON

HiVolt

Premium Member

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.

ajhaji
Premium Member
join:2002-03-02
Etobicoke, ON

ajhaji

Premium Member

My Bell connection is doing the exact same thing. It seems to be stabilizing now...

Anonu
@wind.ca

Anonu to HiVolt

Anon

to HiVolt
Same thing just happened where I am. Markham. Rebooted the POS sagemcom modem, synced have an ip but very few sites work.
Kraftyy
join:2010-06-19
Burlington, ON

Kraftyy to ajhaji

Member

to ajhaji
My bell inet just went down 30 minutes ago same thing as you guys except I'm east hamilton rosedale area

Nagilum
@bell.ca

Nagilum to ajhaji

Anon

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