Just to share my experience on this 1gbps signup to installation with all...
on the first day 1gbps was announced, I logged in to the system to sign up.
But I was not able to. Was later announced that server overloaded and to try later.
I finally got to sign up about 11am.
I am told that the schedule will be starting from 3Q.
An email was received indicating the same almost immediately.
few days later, MR came out and said there will be beta, and will start accepting application in Feb.
Feb came and nothing.
somewhere in late Feb, beta acceptance started, and I signed up.
no information if beta application was accepted.
I think this was the point where people started complaining of bad communication.
I PM johnnny after he mentioned somewhere that we can check with him.
He replied that I am in the list, and someone from CS will contact me again on installation date.
from then, no news from MR's CS.
and with what johnnny told me in the PM, I waited.
People then started saint that they have received installation calls to fix date.
I PM johnnny again telling him that I will be in japan for a while, and if cannot get to me, call me again. I still want to be in beta. He said ok.
on 13 march, I got a call from MR, asking me if 27 March 2-6pm is ok.
Accepted the timing.
Got an email on the confirmed schedule.
on 27 March, the FE from MR called me at about 10 and ask if he can go over to my place. If yes, he will let ON know and switch over.
I was away from home, so he went to another case first.
an email was received to tell me that my staticIP will be changed.
Reached home about 1pm, called the FE back, and he is already downstairs.
within the next 5 mins, my ONT started flashing red.
FE came up, fixed up the new ONT, everything synced.
But horror! No internet.
He stayed and tried to get it done for the next 3 hours, calling MR, and ON. Testing, reconfigured my router, changed to new router, etc. He din have lunch.
He then came to me, and told me that he has another appointment which is late by 3 hours already, and I said its ok that he can go first. but please follow up.
He called to CS and told them what happened, and told them to call me back to inform me what exactly happened.
He refused to let me sign off the job since it was not done up.
an hour later, CS called. (I think this took too long honestly).
That night, up to almost 11pm, I received SMS to apologise and asked me to help them do testing on the ONT, which I gladly helped.
At least I know that someone is trying to get things fixed up for me.
Finally, they told me they have to change the ONT to try.
Next morning, the same FE called and asked if he can go up to my place at about 9am.
Told him to go at 11 instead.
This time he was late, but he called to inform me that he was held back by another installation.
He reached about 12:30.
again for the next 2 hours, he was testing and on the phone with MR.
He left for another appointment and came again at about 4.
During his absence, I got a call from MR saying that they are sending down an engineer to the CO to troubleshoot since everything at the back end looks perfectly normal.
at about 7, everything was up and running!
and the cause of it?
someone did a bad job splicing the Optic fiber, and there was no connection from that port to the core router.
yes, it took a while for the set up, and I am hosting... but then, I feel very happy that so many people put effort into it and finally found a fault which is not even theirs.
And it seems like all those involved are young chaps!
It is hartening to see young people so passionate about the job!
To be honest, I am not happy with the way communication from MR has been for the last few months... but the backend team I like a lot!
And to be frank, a lot of posts I see here are not fair to MR, but I have to agree that MR has to bear part of the responsibility.
From here on, I hope people will direct the anger at the correct party, with the help from MR, and not solely hit on them only.
If it is their fault, they better be honest about it and do something about it.
But if its something out of their control, go target the correct party... and in many cases... its ON.
I took 2 days leave for this and I am not happy about it, but the dedication of the backend team makes up for it.