I know that. The point is the ultra high ping times also indicates that the connection is delayed, possibly going thru a long route or too many routers, even packet/traffic shapers. My ping times are utterly ridiculous. For LOCAL PEERS, a one second ping is highly suspicious.

Not working here. Tried both PAWS and BitSpirit. Getting 0KB/s!

My latest pings (only slight improvement, probably because everyone else is "jammed" by TMNutz on my side)....

Pinging lowyat.net [202.190.197.144] with 32 bytes of data:

Reply from 202.190.197.144: bytes=32 time=953ms TTL=52
Reply from 202.190.197.144: bytes=32 time=1050ms TTL=52
Reply from 202.190.197.144: bytes=32 time=786ms TTL=52
Reply from 202.190.197.144: bytes=32 time=750ms TTL=52

Ping statistics for 202.190.197.144:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 750ms, Maximum = 1050ms, Average = 884ms

Pinging 202.188.0.133 with 32 bytes of data:

Reply from 202.188.0.133: bytes=32 time=1042ms TTL=57
Reply from 202.188.0.133: bytes=32 time=974ms TTL=57
Reply from 202.188.0.133: bytes=32 time=774ms TTL=57
Reply from 202.188.0.133: bytes=32 time=892ms TTL=57

Ping statistics for 202.188.0.133:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 774ms, Maximum = 1042ms, Average = 920ms

Pinging yahoo.com [216.109.112.135] with 32 bytes of data:

Reply from 216.109.112.135: bytes=32 time=1065ms TTL=46
Reply from 216.109.112.135: bytes=32 time=774ms TTL=46
Reply from 216.109.112.135: bytes=32 time=1310ms TTL=46
Reply from 216.109.112.135: bytes=32 time=1318ms TTL=46

Ping statistics for 216.109.112.135:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 774ms, Maximum = 1318ms, Average = 1116ms

Looks like my connection is on that BT throtling deep packet inspection one...

Edit: I can connect to trackers here without using proxy or User Agent mods. That's how I arrive at my conclusion. WEB BROWSING is still SLOW here...

This post has been edited by lex: Jan 18 2007, 03:58 PM

Whoa, those are horrible ping times man. Pinging tmnet's DNS shouldn't take THAT long. I ran a few pings myself, pretty unstable, i get anyway from 50-800ms o-O.

If ping to local IP is suffering high latency, there must be something wrong with the TMNut's router.
I did encounter strange problem, status in modem show connected, but ping gateway even get timeout, have to DC and connect again.

Pinging to www.tm.net.my here (my office) looks okie, avg 30ms.

Guys, are you pinging any site when using P2P at the same time?
If yes, you will suffering slow response when too many connection at you modem/router, even pinging your gateway.

To get accurate statistic, don't run any P2P program, if you just close it, wait for about 10 minutes to let your connection closed properly, completely.

If you use cFosSpeed, try toggle the 'Favour Ping Time'.

YiQi, I do have a rather good connection here. I also have a firewall. Yesterday night I can get the usual pings (before TMNutz throttling mess) when they bypass the packet shapers for a while. Local peers can get consistently BELOW 60ms! Fastest being 9ms This is with my torrent running in the background also! I even tested the mule again.. Same results.

Anyway, ping times update...

Pinging www.3dns.tm.net.my [202.71.97.48] with 32 bytes of data:

Reply from 202.71.97.48: bytes=32 time=18ms TTL=118
Reply from 202.71.97.48: bytes=32 time=12ms TTL=118
Reply from 202.71.97.48: bytes=32 time=12ms TTL=118
Reply from 202.71.97.48: bytes=32 time=11ms TTL=118

Ping statistics for 202.71.97.48:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 18ms, Average = 13ms

Pinging lowyat.net [202.190.197.144] with 32 bytes of data:

Reply from 202.190.197.144: bytes=32 time=14ms TTL=52
Reply from 202.190.197.144: bytes=32 time=9ms TTL=52
Reply from 202.190.197.144: bytes=32 time=10ms TTL=52
Reply from 202.190.197.144: bytes=32 time=100ms TTL=52

Ping statistics for 202.190.197.144:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 100ms, Average = 33ms

All this with torrents running

Speeds picked up a bit now, from 0KB/s to 9.5KB/s.. Another packet shaper bypass?

Edit: Web browsing picked up speed again also!

This post has been edited by lex: Jan 18 2007, 04:59 PM

Yea, P2P was running. Though i've done pings before with P2P running and the spikes were never that huge.

I wonder how long this will last? See pix...


Attached thumbnail(s)

i got these problem as well since yesterday.. was using utorrent.. reinstall everything.. even try other client(bitcomet).. problem still persist.. download upload is still running but assuming the tracker is a private tracker, ur upload or download there will not be counted if they got seeder bonus or ratio system in an example.. no worries leecher will still get your upload but just there is no point..
right now im using ktorrent and everything was running fine..

Well, something to figure out where is the bottleneck, traceroute (tracert) maybe useful. I found quite a lots of time the bottleneck is the gateway itself. e.g.

My traceroute from my office:
traceroute to www.lowyat.net (202.190.197.144), 30 hops max, 38 byte packets
1 60.xx.xx.xx (60.xx.xx.xx) 0.646 ms 0.592 ms 0.525 ms
2 219.93.218.176 (219.93.218.176) 43.576 ms 23.214 ms 9.311 ms
3 219.93.216.225 (219.93.216.225) 4.362 ms 4.334 ms 5.092 ms
4 210.187.143.1 (210.187.143.1) 4.467 ms 4.309 ms 4.072 ms
5 219.93.182.232 (219.93.182.232) 5.064 ms 4.279 ms 4.371 ms
6 202.71.100.9 (202.71.100.9) 4.359 ms 4.583 ms 4.349 ms
7 202.75.52.3 (202.75.52.3) 4.643 ms 4.570 ms 4.363 ms
8 218.100.22.243 (218.100.22.243) 4.659 ms 4.555 ms 4.646 ms
9 218.100.22.34 (218.100.22.34) 5.189 ms 5.885 ms 7.429 ms
10 ge3-0.jsr4.jaring.my (161.142.173.10) 4.904 ms 5.389 ms 5.445 ms
11 * * *
12 * * *

ignore the 11, 12.. and further, probably traceroute ICMP is blocked there.
Usually, try to ping your gateway first, in my example, the No.2.
Occasionally, I found huge delay at the gateway, especially when my line is in high utilization, when some peoples download heavy stuff (software patches, movie trailers....), until their download finish, the ping time drop to normal. This is my experience.

Is TM Net blocking connection to trackers permanently or temporarily? What do you guys think?

i bet they will block till the end of world, no question about it

TODAY... my BT ROCKSSSS

218.111 + cFoSspeed + Tuotu
location - tmn maluri

This post has been edited by Suk: Jan 18 2007, 07:41 PM


Attached thumbnail(s)

First they put the packet shaper that causes "connection closed by peer" locally... This kills any torrents trying to start at the tracker.

Pinging lowyat.net [202.190.197.144] with 32 bytes of data:

Reply from 202.190.197.144: bytes=32 time=67ms TTL=53
Reply from 202.190.197.144: bytes=32 time=46ms TTL=53
Reply from 202.190.197.144: bytes=32 time=62ms TTL=53
Reply from 202.190.197.144: bytes=32 time=77ms TTL=53

Ping statistics for 202.190.197.144:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 77ms, Average = 63ms


Then they put the other packet shaper that throttles and kills encrypted torrent connections internationally...

Pinging yahoo.com [216.109.112.135] with 32 bytes of data:

Reply from 216.109.112.135: bytes=32 time=2166ms TTL=40
Reply from 216.109.112.135: bytes=32 time=2218ms TTL=40
Reply from 216.109.112.135: bytes=32 time=2218ms TTL=40
Reply from 216.109.112.135: bytes=32 time=2187ms TTL=41

Ping statistics for 216.109.112.135:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2166ms, Maximum = 2218ms, Average = 2197ms

The picture tells my story...

This post has been edited by lex: Jan 18 2007, 09:35 PM


Attached thumbnail(s)

I still managed to finish a file I started 8 hours ago. Eventhough cannot connect to tracker, there's still hope.

How come your pings are so damn horrible?
My torrents are moving at around 30-40kBps (total) atm, and when i ping yahoo i get a response in about 300ms which is quite normal.

I experienced a sudden unthrottle mode yesterday midnite. I was able to connect to many international peers (as Msian IP normally starts with 60, 218 & 219) and all my BT speed went sky rocketing high. It was maxed out for about 10mins or so then it slowly die down to 0kB/s. After some 15 seconds or so, it went sky rocketing again for a couple of minutes. Then out of nowhere my BT client was cut off and I'm not connected to anyone. Also I can't do web browsing at all. After some time I just DC & reconnect again. Things went back to the way it was, throttle, sigh. I'm sure TM Nut was doing some restructuring. Life without throttle is good. Just seeing the numbers and stats are mind blowing.

And today I can't connect to any torrents. All of them closed by peer. Cilaka punya TM.

Yups, TMNutz is definitely doing some "restructuring" (with their traffic/packet shapers). That accounts for those sudden surges in speeds due to bypassing the shapers, with the intention of either rerouting to new shapers or upgrading existing shapers.

Guess what, that short surge of bandwidth didn't save one download I had since November. Of the 4 last November ones I had, 1 went unfinished and now the tracker replies "Failure: torrent not registered with this tracker".

I got this problems also damn Tm.Net sux

Please further all discussions here. Thank you.