KardinalDei Gratia ReginaPremium,ModReviews:
N of 49th
|reply to BliZZardX |
Re: [Internet] Service outage downtown toronto?
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
KardinalDei Gratia ReginaPremium,Mod
N of 49th
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.
North York, ON
Any and all Google sites are excruciatingly slow. Could that be caused by this routing issue?
PING google.ca (220.127.116.11): 56 data bytes
64 bytes from 18.104.22.168: icmp_seq=0 ttl=49 time=315.245 ms
64 bytes from 22.214.171.124: icmp_seq=1 ttl=49 time=315.038 ms
64 bytes from 126.96.36.199: icmp_seq=2 ttl=49 time=315.065 ms
64 bytes from 188.8.131.52: icmp_seq=3 ttl=49 time=315.879 ms
Nope everything fixed itself about 2 hours ago here
@MikroTik] > tool traceroute 184.108.40.206
# ADDRESS RT1 RT2 RT3 STATUS
1 220.127.116.11 5ms 5ms 4ms
2 18.104.22.168 5ms 4ms 4ms
3 0.0.0.0 0ms 0ms 0ms
4 22.214.171.124 16ms 15ms 15ms
5 126.96.36.199 18ms 19ms 17ms <MPLS:L=17229,E=1,T=255>
6 188.8.131.52 15ms 22ms 15ms
7 184.108.40.206 31ms 31ms 31ms
8 220.127.116.11 31ms 30ms 31ms
9 18.104.22.168 31ms 31ms 30ms <MPLS:L=501885,E=4>
10 22.214.171.124 38ms 38ms 38ms
11 126.96.36.199 39ms 38ms 38ms
12 188.8.131.52 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.