Reviews:
 ·WIND Mobile
 ·TekSavvy Cable
 ·TekSavvy DSL
| reply to TSI MartinP
Re: [Cable] Outage in London 2nd Tuesday of next week? Good thing I was planning to only use the web on the 1rst Tuesday of next week.
My friends on facebook have also been telling me that there is a scheduled downtime for facebook from Feb 29 - 31 and to not plan to use facebook during that time. |
|
|
|
1 edit | Good thing, I think you might be safe then!
Is the Facebook outage legit? I haven't heard anything on that. |
|
| reply to graniterock
said by graniterock:2nd Tuesday of next week? Good thing I was planning to only use the web on the 1rst Tuesday of next week.
My friends on facebook have also been telling me that there is a scheduled downtime for facebook from Feb 29 - 31 and to not plan to use facebook during that time.
LAWLZ!!! You do of course realize that February 29 - 31 doesn't exist, right? February only goes as far as February 28... LOL LOL LOL |
|
 iRage
join:2010-06-01
Canada
1 edit | reply to evil_gusgus
Let's all blame an ISP for a truck smashing into a few lines and then cry that "I can't work from home and I'm losing so much money rawwwwwwwwwr! Me want credit so you give me monies for my lost time rabblerabblerabble!".
If having a constant connection is 100% vital in keeping your finances coming in working from home, you need to implement some redundancy and get a dry loop DSL connection as a backup. Or tether your cellphone/hotspot that shit up. If you're not willing to go the extra mile in securing your connection then STFU and eat your loss because it's YOUR fault for not thinking ahead. Not TekSavvy, not Rogers, YOURS.
We're talking about the internet. It WILL go down at some point in your busy little life and this WILL happen again, no matter who the hell your ISP is. So go ahead and cancel TekSavvy, Rogers etc over this and future outages. It won't make a bit of difference to them.
Anyway, I'm back up in London as well. I had kids bitching at me about it. Next time I'll come complain that my kids are bitching so then maybe the internet will come back faster. |
|
| Not to mention I mean really, is it worth THAT much of your time to get your f'n 1 dollars in credit back?!?
Seriously? It is 1 dollar, maybe a buck fifty. |
|
| reply to MrMazda86
Next Leap Day: February 29, 2016... just sayin... |
|
| reply to evil_gusgus
Looks like the line was cut between the London POI and the rest of the world. So, TekSavvy has only line for the whole city + St. Thomas and area? Really? This is the first time this word came to my mind in relation to TekSavvy: unprofessional. The whole idea of the internet was if the enemy brings down one line the traffic will find another route to the destination.
I see that traffic goes from London to London through Toronto (that is to non-TekSavvy IP's). Essentially, it is the same as it would have been with aggregated POI model. So, what is the point of the non-aggregated structure? Except it would have been better with aggregated POI because I bet Rogers' internet is the proper one, with redundancy. |
|
1 edit | said by alpovs:Looks like the line was cut between the London POI and the rest of the world. So, TekSavvy has only line for the whole city + St. Thomas and area? Really? This is the first time this word came to my mind in relation to TekSavvy: unprofessional. The whole idea of the internet was if the enemy brings down one line the traffic will find another route to the destination.
I see that traffic goes from London to London through Toronto (that is to non-TekSavvy IP's). Essentially, it is the same as it would have been with aggregated POI model. So, what is the point of the non-aggregated structure? Except it would have been better with aggregated POI because I bet Rogers' internet is the proper one, with redundancy.
Actually, I think you misunderstood the whole situation. The problem didn't lie with TekSavvy. The hardware (links) that were damaged was actually all Rogers equipment. Depending on where in the area you fall depended on whether or not you were affected, regardless of whether you were with Rogers or TekSavvy.
There were a few customers (both Rogers AND TekSavvy) who still maintained their signal somehow. I suspect that it may have been multiple links that were taken out on the same main lines. This would explain why there were a few customers who didn't loose a signal, since it would suggest that a small fragment of the system was still functional.
Before you go trying to "crucify" TekSavvy, I suggest that you first fully inform yourself of all the facts. This may save you a lot of frustrations. |
|
| reply to evil_gusgus
And all rumors that this outage affected any other networks are unconfirmed. During the outage the traffic stopped after 24-52-255-166.cable.teksavvy.com. The next hop is always TekSavvy's (24-52-255-165.cable.teksavvy.com or london3(or 2).cable.teksavvy.com). So, the problem was on TekSavvy network. The fiber lines may belong to Rogers, of course. |
|
| reply to MrMazda86
MrMazda86, do you know anyone with TekSavvy in London who did not have an outage or anyone in London who is not with TekSavvy who had an outage? You are not even in London. A couple of friends near me on Rogers didn't have any outages. Nobody with Start responded to a question about an outage. And trace routes clearly show where that outage happened. |
|
| People with Distributel DID have outages at the same time though. |
|
| reply to MrMazda86
said by MrMazda86:There were a few customers (both Rogers AND TekSavvy) who still maintained their signal somehow. And there was never a problem with the signal. The traffic just stopped after three hops. I wish I tried to trace route to any TekSavvy London IP during the outage. I bet it would have gone through. I think there was some kind of London LAN cut from WAN. |
|
| reply to Scycotic
said by Scycotic:People with Distributel DID have outages at the same time though. In London? I only know about one report of problems with Distributel in the GTA. Can it possibly be related? |
|
| Yes, in London. Someone in the first few pages of the thread reported their friend had problems with Distributel. Also, I've read reports on another forum of the same thing happening. |
|
| Yes 4 of us in London with Distributel did not have internet. |
|
| So, looks like all non-aggregated TPIA use the same physical line to connect from London to TORIX without redundancy. I highly doubt that Start had the same problems. Their traffic stays with Rogers until TORIX. Rogers customers would have had the same problems if Start had them. |
|
can00k
join:2003-07-05
London, ON | reply to evil_gusgus
Thanks for keeping us informed about repair ETAs and such.
I'm not happy about having two major outages in a week, but I'm not about to get my pitchfork out and lay blame unless solid facts come out about what exactly happened and who is responsible for preventing/fixing it as quickly as possible. All I know for sure right now is that it wasn't solely a Teksavvy problem, so I'll thank the company for at least keeping us up to date as much as possible. |
|
| reply to alpovs
said by rocca:said by londoner1:Can anyone confirm that the outage is also affecting start.ca customers on cable in London?
We were not impacted by any outage today. »Re: Teksavvy outage London? |
|
| reply to evil_gusgus
Concerning those 'confirmed reports' of Start having cable troubles in London today...
Rocca from Start said... "We were not impacted by any outage today."
edit1: Sorry alpovs... I was just slower than you. |
|
| reply to alpovs
said by alpovs:MrMazda86, do you know anyone with TekSavvy in London who did not have an outage or anyone in London who is not with TekSavvy who had an outage? You are not even in London. A couple of friends near me on Rogers didn't have any outages. Nobody with Start responded to a question about an outage. And trace routes clearly show where that outage happened.
Actually... Yes. I know both Rogers and TekSavvy customers in London. Rogers had the exact same problem. I called them myself just for shits and giggles to see if they were having the same issue. Whether with Rogers or TekSavvy, they all said the same thing.
said by alpovs:And there was never a problem with the signal. The traffic just stopped after three hops. I wish I tried to trace route to any TekSavvy London IP during the outage. I bet it would have gone through. I think there was some kind of London LAN cut from WAN.
I think perhaps I may have used the wrong choice of words in that statement. The actual RF signal wasn't the issue. What I was referring to was their ability to obtain an actual connection to anything beyond what required access beyond gw01.wdstck.phub.net.cable.rogers.com |
|
