I believe they tried, and it didn't work either...
I think that many people made assumptions regarding the Vector
network, and unfortunately those assumptions turned out to be
What worries me much more the then technological shortcomings of the
network is lack of processes (or perhaps unsuccessful implementation?)
that would help the customers to understand what's going on and when
it's going to be fixed. Technical problems can be fixed with money,
lack of care and lack of ownership - not easily.
Updates 4h into the problem saying - no ETA and about 2h later - it
will be fixed tomorrow are just not enough. The fact that it was
virtually impossible to get hold of anyone that actually had a clue is
not something that an average business is willing to accept.
I wonder if we will see a root cause analysis for this one.
2008/6/30 Chris Hodgetts <chris(a)archnetnz.com>om>:
That usually fixes things....
Did anyone else find if appalling that Vector advised that the issue
would be resolved on Monday ..
And that it took over 9 hours to resolve?
(It has not been mentioned here but I assume everyone knows what I am
NZNOG mailing list