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

reply to BliZZardX

Re: [Internet] Service outage downtown toronto?

reply to mediajedi

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

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.

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

 
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>
 

reply to BliZZardX
Seems to be from TATA communication

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.

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

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.

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.

reply to resa1983

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

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

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.

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

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.

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.

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