We will be bringing up a new US server over the next 48 hours.
We will not allow Piratebay/EZTV/Mininova on this server and we ask people to use this server responsibly or we would have to take it down as well.
Update: This server is now up and running as Mohawk v 2
0 
0 
0 
0 
Commanche is experiencing some problems and we see some DDoS symptoms.
We are looking into this problem right now.
0 0 0 0 TM has been experiencing massive routing issues today and will result in degraded performance. Please do not ask us when this will resolve as we have no idea either.
Also Mohawk server has been brought down due to rampant infringement abuse which has rendered it not practical for us to maintain it.
We are looking for a replacement server for this.
Pinging Lowyat:
Pinging lowyat.net [202.190.197.143] with 32 bytes of data:
Reply from 202.190.197.143: bytes=32 time=408ms TTL=54
Reply from 202.190.197.143: bytes=32 time=356ms TTL=54
Reply from 202.190.197.143: bytes=32 time=332ms TTL=54
Reply from 202.190.197.143: bytes=32 time=337ms TTL=54
Ping statistics for 202.190.197.143:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 332ms, Maximum = 408ms, Average = 358ms
Pinging TM’s own DNS
Pinging 202.188.0.133 with 32 bytes of data:
Reply from 202.188.0.133: bytes=32 time=346ms TTL=247
Reply from 202.188.0.133: bytes=32 time=364ms TTL=247
Reply from 202.188.0.133: bytes=32 time=351ms TTL=247
Reply from 202.188.0.133: bytes=32 time=355ms TTL=247
Reply from 202.188.0.133: bytes=32 time=367ms TTL=247
Reply from 202.188.0.133: bytes=32 time=343ms TTL=247
Ping statistics for 202.188.0.133:
Packets: Sent = 6, Received = 6, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 343ms, Maximum = 367ms, Average = 354ms
0 0 0 0 At the moment we are noticing massive TM problems on a wide variety of IP ranges.
Till this is resolved we will not entertain speed troubleshooting requests as this seems to affect many international routes.
If you wish to confirm whether it’s a routing issue, please visit this FAQ.
For those who can read ping reports:
Pinging tm.net.my [208.67.219.132] with 32 bytes of data:
Reply from 208.67.219.132: bytes=32 time=488ms TTL=47
Reply from 208.67.219.132: bytes=32 time=489ms TTL=47
Reply from 208.67.219.132: bytes=32 time=485ms TTL=47
Reply from 208.67.219.132: bytes=32 time=497ms TTL=47
0 0 0 0 
