Guys,

Some progess updates.

Spoke to TMNET's staff, Ms. Norehan.  I had her verbal confirmation that

1.  their Vice President (VP) will be in the discussion and the VP will be able to say "yes" or "no" on the issue we're going to discuss. 
2.  It will be a closed door meeting.

I had made my initial objective to them including the issues we're facing.  Secondly, i've requested, in fact, insist TMNET to announce whatever conclusion made during the coming discussion via either the press conference or press release.

MCMC and PMO's PCB (Public Complaint Bureau), both of their boss is following up the case and the discussion.

One things that makes me wondering was, during the conversation, Ms Norehan, told me there'll be a "good news" in the discussion.  Even though, i'm wondering, i told her that the only good news to me is when intended result had become a reality.

I'll update you guys when i have the latest updates.

Good news ?

AAG will launch very very soon ( estimated Q2 2009 ) extra bandwidth to TM ?
HSBB package will announce too.

I know HSBB is under testing.
there are a lot of RDSLAM install around my area. my teman at least got 3. which only have TM logo only.

Old news but they haven't launch / start yet

HSBB - package 10Mb/2Mb - Price unknown.

Hi, webdesignempire, thanks for taking it up.

I believe this single step is better than all the energy, bandwidth and efforts in the rant section.

I were talking with the tech support at 100 too.. and the thing is, they're pretty much 'isolated' and 'limited' in their trouble shooting capacity.

We experienced downtime yesterday, as per some of the other users reported here too.

When I was calling TM's support line, i specifically asked how do they determine if there's no issues on TM's side. And their answer is, their boss didn't inform them of any issues.

I were specifically questioning him on the kind of information available to him, and was disappointed to see that he's just a guy with a telephone attached to him, and there's no 'actual troubleshooting' being done.

If I'm TM, i'd imagine the guys at the support line to have something like this.
1) Computer, of course
2) The computer should be connected to a database of current issues.
3) He'll need to have access to all the latest cases reported in 24/48 hours.
4) If there's a sudden spike in reported cases, especially reported cases from geeks/IT personnel who are sure their network/virus/what os you're using is not to blame.
5) Then confirm, there's a problem with streamyx end.
6) Reply to customer, yes, I can see within the xxx hours, a lot of other technically competent users are complaining of the same problem too, therefore, we believe we have an issue in streamyx's network, particularly relating to our DNS server, and our technical team are already working on bringing the DNS server back up.

...

This is what I want to hear from them!!
But instead of this, seems like TM's support is working on a case by case basis, they don't know how to put 1+1 = 2....

actually, if they train their frontline to be smarter, and give them more information to link 1+1=2, then TM will be saving a lot of money from sending their technicians out.

Everytime I make a call, they say send technician...
Every technician sent out is a cost to TM, why send the technician out if they can determine, OK 2,000 of the reported cases are an internal streamyx servers issue, we resolve on our side first. no need to send technician out.

Imagine the savings!

They need to empower their frontline staffs who're taking in calls, put smart ppl in there, and give them power to direct the technical team around, NOT the other way!!

The front liners who answer our calls are either smart ppl limited by stupid process, or they're not so smart, and TM don't even trust their own front liner's troubleshooting abilities.

Like in ur case, WHY ON EARTH need to send technician out?

It's really a no brainer.

If ppl complain to me my 2.0 is 1.3

I'll check on my side, is it wrongly capped first? Especially, since this is not the first time it happened.

The frontliner's user terminals should have all this ability built in... check cap limit on TM server, compare with signed package, if wrong, ask technician to cap correctly. case closed an hour later.

But they always send technician, send technician.
This is fine if they're dealing with non IT savvy customers, but for technical guys like you and me, who live, breath IT, they shouldn't treat us as dumb guys who needs confirmation of probleem by their technician...

Speaking of which, our international line is still experiencing packet losses.....

A recap.

FYI, I take no orders from TMNET.  However, i'll follow instruction given by the authority, example MCMC at 100% provided the orders or instructions are justifiable.

I'll show you what kind of integrity i have in this matter.  Again, as my post's footer.  I'm not God-like, Help me Help you.

Thanks alot for your understandings, appreciate very much.

I've been sort of force to use the service for around your time of length too. TMNET has too many issues that rooted for so many years and it's not something can fix within a few days kind of things. 

Personally, i suggested to Syamsul, during the discussion, of 3 month period else compensation to all affected users.  He thought i'm giving him a firm deadline.  In fact, i had no power to do so.  So i told him and i emphasize that this is only an suggestion, also telling him that "but you don't tell me you need 6 years to fix it".  I told him, i need a date of all these will be in place.  He agreed to get back to me with the answers.

I know i had no power to push them do what they suppose to do especially with the "3 month period else compensation" thingy.  But, i'll bring this to MCMC, who has the power and authority to have TMNET comply.  Things i wanna share is, we gotta know what's the position we're in and what's the limitation we have in this battlefield (discussion of the issues).  Only by then, we know where and who should we get help from to fill up the portion we lack of.

Like most of the Service Provider, we dying for a fastest fix than any individual.  Because, when their service went down.  All customers will call us up, and we might ended picking calls from morning till evening for days; repeating the same explanation to all customers.  After that customers are taken care, the job ain't finish yet.  We'll have to process and highlight the issue to TMNET on their behalf.  Imagine, what kind of situation we're in.  It's a greatest mind torture and pressure that i bet most of you do not want to get into.  And that makes us the group that dying the most of the fix asap as much as anyone does.

Why it is impossible for me, personally to take up a potential special offers from TMNET?  First, if i did this, what other customer would think of me?  A person without integrity is not trustworthy at all. 

And more importantly, if i were to take the potential offers from TMNET, how am suppose to stand at the ground i'm standing from the first day i post the topic here?  If i were to fight for special arrangement for myself, i have no ground to support me to go to MCMC.  Hope you guys really see the point over here. 

A stable and reliable broadband is for everyone, NOT to me, not my customers, friends or family only.  But to all of the users.

TM tech who came to your house to fix your line has no authority to change routing or IP's

All IP's / Routing/ ATM configuration / BRAS must be approved from NOC b4 TM tech can touch.

It was told by my tech from my area.

However, Why after a several complain about bad IP's U had changed to other IP range ?
It was done by the TM Tech changed your Telephone PORT to other ATM which generate diff IP range.
Example, My neighbor jst next door, connected to different BRAS.
which give different IP range compare to me. 

To overcome this, subscribe 2MB/4MB package and u will get premium IP which is 218.111.

However, TM NOC is monitoring us. Good Luck.

  If I were him I'd have to be nice too... because if you were to go to PMO, I'll be in trouble!   

Smile is the key~~~~eheh jokes jokes...chill

Tonight there will be major network core upgrades in TM until tomorrow morning, lets see what happens after the upgrades. I pray to god that the upgrades have something to do with AAG which will benefit us.

Guys,

These result happened to be yesterday's.  Insanely hilarious.....

To the TM DNS:
===========

Ping statistics for 202.188.0.133:
    Packets: Sent = 126, Received = 123, Lost = 3 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 832ms, Average = 572ms

Ping statistics for 202.188.0.133:
    Packets: Sent = 872, Received = 850, Lost = 22 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 9ms, Maximum = 1436ms, Average = 483ms

Ping statistics for 202.188.0.133:
    Packets: Sent = 951, Received = 926, Lost = 25 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 9ms, Maximum = 1436ms, Average = 496ms
Email to TM's AGMs
=============
Dear All,

Some recap for your kind review and advise.  This is one of those repeating issues from Streamyx.  The information below is abstracted from the TRACE ROUTE which TM claims to be potentially causing ICMP overhead and has been blocked for that reason and security measures.

Please refer to the result below, the response time increased sharply on hop #3 onward (219.93.218.177, 219.93.216.157, 58.27.104.206, 219.94.9.166).  The funny thing is, the respond time beyond TM's infrastructure seems to be perform alot better.

I recalled as per our previous discussion, one of the IP's location still await TM's confirmation on why it has high jump on respond time (ms).  Have you found it?  What about the 90% commitment to the users?

Tracing route to HOST [IP] with TTL of 32:

1  1ms    0ms    0ms    10.0.1.1
2  1ms    1ms    1ms    192.168.1.1
3  343ms  524ms  *    219.93.218.177
4  836ms  848ms  726ms  219.93.216.157
5  802ms  727ms  607ms  58.27.104.206
6  875ms  869ms  893ms  219.94.9.166
7  783ms  999ms  *    gi2-8.mpd01.sjc04.atlas.cogentco.com [154.54.12.65]
8  211ms  211ms  211ms  te3-1.mpd01.sfo01.atlas.cogentco.com [154.54.28.81]
9  406ms  472ms  427ms  te7-4.mpd01.mci01.atlas.cogentco.com [154.54.24.106]
10  485ms  268ms  267ms  te7-2.mpd01.ord01.atlas.cogentco.com [154.54.7.137]
11  284ms  284ms  284ms  te2-1.mpd01.bos01.atlas.cogentco.com [154.54.6.17]
12  295ms  291ms  300ms  te8-3.mpd03.jfk02.atlas.cogentco.com [66.28.4.202]
13  293ms  294ms  293ms  te4-1.ccr01.phl01.atlas.cogentco.com [154.54.2.109]
14  293ms  294ms  293ms  te4-1.ccr01.phl03.atlas.cogentco.com [154.54.0.190]
15  278ms  278ms  278ms  hostnoc.demarc.cogentco.com [38.112.240.34]
16  293ms  295ms  304ms  ec1-00.gwy02.HOST.HOST [IP]
17  399ms  399ms  402ms  ec1-20.agg04.HOST.HOST [IP]
18  398ms  387ms  389ms  HOST [IP]

Traceroute complete.

Seems like TM's backyard is jammed.