Friday, October 06, 2006

The NTSCMP Affair: Final Words

Regarding lack of access to ntscmp.com, Mister B sent an email to PCCW Netvigator's Tech Support on Thursday, 14 September. That elicited a standard Netvigator autobot reply. From Customer Service (?):
Many thanks for writing to us. This message serves as an acknowledgement that your mail has been received. A response to your enquiry will be provided within two working days.
Mister B then received another Netvigator autobot reply on Saturday, 16 September. From Tech Support:
With regards to your message, kindly be informed that we have passed your concern to our relevant department for investigation. Once they have completed the findings, we will get back to you.
Could this be a corporate run-around? Be that as it may, Mister B was unwilling to wait any longer -- and made a first post in the late afternoon of 18 September about the apparent blocking by PCCW Netvigator of ntscmp.com

Lo and behold, today (6 October) a reply from Netvigator:
I am writing in response to your previous enquiry about accessing "http://ntscmp.com", kindly be informed that the situation is resolved. Please kindly try again.
A Netvigator reply which isn't half as interesting as the one sidekick got on 3 October (scroll down comments):
With regards to your last email about the website (www.ntscmp.com). Inform by our backend engineering department, the problem had been resolved. Please kindly try to access again.
Backend engineering department?

Hong Kong's Office of the Telecommunications Authority (ofta) was somewhat prompter. Its reply arrived on 5 October:
With reference to your earlier complaint on blocking of access at the website www.ntscmp.com, we would like to reply as follow:
This Office has made enquiries to PCCW-IMS Limited and Hutchison Global Communications Limited regarding the issue. However, there is no evidence showing that they have wilfully blocked the website "www.ntscmp.com".
Therefore, this Office cannot take any regulatory action under the Telecommunications Ordinance at this stage. We will continue to monitor the situation.
So what did Netvigator's backend engineering department do? Or undo? Whatever. It's done. Case closed, final words, et cetera. Thanks!

No comments: