Microsoft Windows [Version 6.1.7600]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\Tinklepuff>ping www.tmnet.com.my -t -l 1024

Pinging www.tmnet.com.my [202.71.97.41] with 1024 bytes of data:
Reply from 202.71.97.41: bytes=1024 time=168ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=175ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=169ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=163ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=169ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=174ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=173ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=172ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=174ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=172ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=169ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=166ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=172ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=171ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=170ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=172ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=172ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=173ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=166ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=172ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=170ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=174ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=172ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=171ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=168ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=166ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=165ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=168ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=161ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=166ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=342ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=1128ms TTL=121
Request timed out.
Reply from 202.71.97.41: bytes=1024 time=190ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=176ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=166ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=171ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=174ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=179ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=168ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=165ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=157ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=156ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=159ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=164ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=161ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=157ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=182ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=216ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=171ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=171ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=167ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=247ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=168ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=169ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=168ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=165ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=162ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=171ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=167ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=175ms TTL=121

Ping statistics for 202.71.97.41:
Packets: Sent = 61, Received = 60, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 156ms, Maximum = 1128ms, Average = 190ms

This is with nothing on not even browser cuz if I load anything it will go haywire.. And I'm in melaka, I usually get response of 40-60ms frm this ping

Hope they fix it quick..

They just haven't done fixing the AAG cables yet I guess.. or even started.. the smarties never even state a date of estimated completion.

Nah they still havent fix the AAG thingy. I'm still getting 150+- ms pinging tmnet when not having anything open, and with browser like facebook open it can go from 500ms- over 1k ms. spikes then maintain a handsome 300-400ms n may slide back down to 200ms. And you do not know wanna know my ping to overseas. And previously before this broken cable thing, I was getting regular 40-59ms pinging them.

Still high ping since 16th June, I would assume and hope its due to the SMW4 or AAG cable isn't fix yet, since they announce the prob on the 17th. Cuz if it is, means its only temporary prob

Well hope they fix it soon since I'm actually playing WoW, this kinda sux.. I walk around with such high latency, I can't raid, I'm bored.

Btw, what is their twitter?

Try ping Europe/America..

My ass -.- I'm using 1meg line and is having same issues with all of you guys...

http://forum.lowyat.net/topic/1058751/+60

So November 1st they done with w/e they doing.

1mb user in Melaka here, disconect , lag, and request time out all day.

sigh... so supposely fixed by november 2 rite? lets see if they will suprise us with no delays

---

Added on November 2, 2010, 7:15 amNope, Internet is still HORRENDOUS today

This post has been edited by babycookie: Nov 2 2010, 07:15 AM

No I'm in melaka... Supposely they said they fix some stupid undersea cable and fixed by Nov2? my ass.

Still crap... DC, Dc, request Time Out are all critting me on the face.

Melaka here. 1mbps user.

Shark 3D starring TMnet's undersea cable...

Since the last cable broke, I lag like mad when gaming. And Disconects with timeouts. But for the last few days, it maintian a good morning and when afternoon hits, its start to lag, and gets worse along until the night. But today, I got prob in the morning as well... So another cable issue, or TMNET IS JUST FILLED WITH ISSUES?

Omg its half of the speed it use to be, im lagging bad in raids.

Usual latency is 218ms ... in WoW
now latency is 580ms...

Something seems wrong...

It fluctuates but it stays on the bad side more often then good. Gamers gets hurts bad

Yea, my ping to local is fine but I'm a Wow player and my servers are hosted in the usa, and disconnects and latency sky high is forcing me to not be able to raid. Even communication services like Ventrillo are effected with disconnects and high ping.

It seems like certian websites are slow if they arent locally hosted.

using 60.xx.xx.xxx IP

This post has been edited by babycookie: Jan 13 2011, 11:59 AM

My friend told me he called TMnet, and they told him to restart his computer, cuz everything is fine on thier side and they claim they have not recieve any complaints from other users bout international connection problems

So... wtf?

---

Added on January 13, 2011, 12:34 pm

Ping to Cyberjaya (Speedtest)


Ping to malaysia (Ping test)


Local pinging is fine, but having latency of 30k ingame latency isnt with the help of WowTunnels still the lowest it goes to is 3000ms and numerous disconnect.. Ventrillo latency is chain disconnect and it shotted up to 19k earlier...

This post has been edited by babycookie: Jan 13 2011, 12:34 PM

Actually i think its not that they think we are dumb, I think some of the ppl that are working there are very retarded besides the usual responses that is probably printed and plastered into the wall infront of their face, so they can repeatedly read that whenever someone calls.