I called them earlier and they say there will still be outage due to the undersea cables damage, although I find it strange that 2 days ago my connection was totally smooth to Germany based servers and now it's crawling slower than a sloth.

They say fixes will be in place by around this evening(which is over) or tomorrow. We'll see..

Oversea site pings :

Ping statistics for 160.79.128.9:
Packets: Sent = 50, Received = 34, Lost = 16 (32% loss),
Approximate round trip times in milli-seconds:
Minimum = 293ms, Maximum = 295ms, Average = 294ms

Ping statistics for 87.106.139.137:
Packets: Sent = 50, Received = 37, Lost = 13 (26% loss),
Approximate round trip times in milli-seconds:
Minimum = 237ms, Maximum = 239ms, Average = 237ms

Ping statistics for 78.46.37.42:
Packets: Sent = 50, Received = 36, Lost = 14 (28% loss),
Approximate round trip times in milli-seconds:
Minimum = 239ms, Maximum = 242ms, Average = 241ms

Seems like routing is still an issue now. Problem is how long they want to take to optimize their re-routing?

Being aware is one thing, doing something about it is another

They might just ignore this citing the connection is at '70% capacity' which is their minimum 'best of service' mark

Compensation? You're kidding right?

That's too much to ask out of them really, just give me back a normal connection and I am happy enough

Stop sending our data round and round the world to get to somewhere for god sake

44% loss to europe still.

4 ping is just not consistent, try using 50 sample.

32byte DDOS attack? Might as well send bigger packet right

TMnet Techie 1 : whoa, full 128kbps upload speed from this user!
Tmnet Techie 2 : OMG It's a DOS, with our connection it's impossible to reach that speed! cut his line!
User : What the? Why my counsterstrike disconnected?

That's the best I can give back TM requested an email with my ping data yesterday, and they've just replied to it just now.

This post has been edited by SeaGates: Jan 8 2009, 11:40 PM

I am on the phone with the 9515 for about 30 minutes now. I am pushing for answer since the call attendant keep giving me 'not sure' 'don't know' 'in progress' as answer.

Seems that they're not treating this issue as an big technical problem, but rather they're treating this problem more like 'isolated case' where it takes '2 working days' to solve every issue.

It is still bad here unfortunately

Ping statistics for 160.79.128.9:(www.di.fm)
Packets: Sent = 50, Received = 35, Lost = 15 (30% loss),
Approximate round trip times in milli-seconds:
Minimum = 356ms, Maximum = 365ms, Average = 358ms

Ping statistics for 87.106.139.137:(www.gameforge.de)
Packets: Sent = 50, Received = 35, Lost = 15 (30% loss),
Approximate round trip times in milli-seconds:
Minimum = 315ms, Maximum = 319ms, Average = 317ms

Still fail =/

Added:

Ping statistics for 216.91.182.78:(savvis.net)
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 301ms, Maximum = 308ms, Average = 304ms

Ping statistics for 64.235.224.5:(mzima.net)
Packets: Sent = 50, Received = 27, Lost = 23 (46% loss),
Approximate round trip times in milli-seconds:
Minimum = 450ms, Maximum = 454ms, Average = 451ms

IP now is 118.100.x.x


This post has been edited by SeaGates: Jan 9 2009, 06:54 PM

I can never get 60 range IP, only 118/124

I am using 512kbps, and I am staying in Bandar Sungai Long

I am not concerned with latency nor I am concerned with bandwidth as I don't do huge download often. I can compensate for 0.5ms, it's hardly significant unless you're doing games that require low latency. It's the packet loss that annoys because some games will see it as timeout and disconnect you or the game fail to respond to your input.

I don't know but things did not improve for sites/services that I use unfortunately. So I am still not happy, as with the routing I already raised my concern to them about it and asked them to stop throwing out data all over the place before reaching our destination. I don't like listening to my radio when it's choppy.

Re-ping:
Ping statistics for 216.91.182.78:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 301ms, Maximum = 335ms, Average = 304ms

Ping statistics for 64.235.224.5:
Packets: Sent = 50, Received = 30, Lost = 20 (40% loss),
Approximate round trip times in milli-seconds:
Minimum = 450ms, Maximum = 454ms, Average = 451ms

Ping statistics for 216.193.218.26:
Packets: Sent = 50, Received = 45, Lost = 5 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 437ms, Maximum = 446ms, Average = 440ms

Ping statistics for 160.79.128.9:
Packets: Sent = 50, Received = 36, Lost = 14 (28% loss),
Approximate round trip times in milli-seconds:
Minimum = 356ms, Maximum = 360ms, Average = 357ms


This post has been edited by SeaGates: Jan 9 2009, 07:28 PM

Kinda pointless to just reroute specific routes etc, imo they should do a general reroute so they don't send everything around the world before reaching any destination.

The route to Germany is direct but it's still slow, so I wonder why, I can be wrong on that though, not sure how tracert reacts with router based connection.

Speed and latency is ok now, just need to rectify the vital packet loss problem.

This post has been edited by SeaGates: Jan 9 2009, 09:33 PM

Connection still fails, up to 50% packet loss now. Call up and they keep saying 'under investigation'. How long they want to investigate

Bandar Sungai Long, Kajang/Cheras area.

I've just finished my phone call with them, I managed to get the supervisor to talk to me, and here's what I have.

- There's contradicting party in the department, some say it's isolated cases, some say there's still fault with the international link.
- I suspect it's a fault at international link, because I am not the only one getting high packet loss from sites in Europe/US.
- If point 2 is true, it's a nationwide problem, TMnet assigned departments have emergency teams to tackle these issue?
- Supervisor also say he will hear more from the network engineer by Monday, that simply defeat the point of me calling up urgently on Wednesday hoping they fix it before weekend so I can use it properly through the weekend

I am getting full speed and decent latency as well. It's the packet loss that's causing all kind of problem. Packet loss affects application that requires constant low bandwidth streaming, like net radio or games that require constant input from user.

This post has been edited by SeaGates: Jan 10 2009, 03:56 PM