| reply to jfn0106
Re: slow 6M DSL Montreal (evening only?) said by jfn0106:So...they acknowledge congested links and clearly suggest a workaround to help mitigate winding up on a congested link. They did not say that they were seeing congestion from their end of things, only that Bell's shuffling seems to be causing congestion.
When people start complaining and TSI notices that AHSSPIs are congested, TSI usually responds stating that they had a load imbalance problem and are terminating L2TP sessions on over-burdened links to re-distribute the load. Since they are not doing it this time around, I take this as a hint that the current congestion issues are occurring somewhere within the Bell cloud so TSI cannot determine which links are misbehaving with their current tools. |
|
| said by InvalidError:said by jfn0106:So...they acknowledge congested links and clearly suggest a workaround to help mitigate winding up on a congested link. They did not say that they were seeing congestion from their end of things, only that Bell's shuffling seems to be causing congestion. No reason for you to disagree with me then, since I never suggested that they saw congestion "at their end":
said by jfn0106:At least Teksavvy has now acknowledged there is an issue with congested links.
I'm not sure any of us really care where the congestion is. I do think what we'd all agree on, and like to see going forward is TSI providing transparency about the congestion problems and to post updates as progress is made towards a fix. |
|
|
|
| said by jfn0106:TSI providing transparency about the congestion problems and to post updates as progress is made towards a fix. Except that if the congestion is indeed happening within Bell-land because Bell is re-arranging stuff at their end of things, there is very little that TSI can do to "fix it" since they have no control over what actually needs fixing and they won't know if their fix fixes anything until Bell is done fixing their own things first.
With some luck, maybe the reason Bell is busy re-arranging their network is to prepare for 10G AHSSPI. |
|
| its taking them a hell of a long time though, talk about service interruptions. i wonder what excuse or runaround they are giving to their own customers. Since Saturday I have noticed but some users have said even earlier like Thursday, so its going on a solid week now, wow .
--
Larry, Larry Laugher .. hehe |
|
| Agreed, I feel like a bit of a mushroom 
Speeds dropped back down again to a crawl last night, but seem to be back to normal again this morning.
If anyone from Teksavvy is following this thread, any update on the progress with the network maintenance? |
|
| reply to InvalidError
TSI could at least inform us of the situation. I don't care if who's to blame but I do care about knowing what's going on and having an ETA. Shame on TSI. |
|
| said by tsilkdjsaflk :TSI could at least inform us of the situation. Since Bell stopped providing network maintenance notices years ago, TSI does not know anything beyond "Bell is working on stuff" so there isn't any information to talk about nor ETAs.
All TSI knows is the same thing we know: it will be done when Bell gets done with it, whenever that may be. |
|
