hoho that's good... so u keep downloading at that time
who knows will happen again...

Well, think logically.

Around this time is when most businesses are operating, and most regular users are awake, so they throttle p2p at around this time as to not affect the speed of the other users.

At night when offices are close, they unthrottle p2p allowing us to at least get some downloads done. So in that sense, at least they do have 'some' concern for us p2p users.

Kudos to TMNet for that. Better than 24/7 throttling.

Next step for them is to improve their international bandwidth link!

Yeah, that's the time to download. I realised the time they throttle and unthrottle varies for different people. No idea why.

This post has been edited by dxreaper: Feb 7 2007, 04:51 PM

Logically, that should be the case; however the truth is that some area still got throttled 24/7. There is a huge group of Streamyx subscribers still suffers and those TMNut fellows don't give a Sxit about.

Hmmm... Maybe the throttling/unthrottling has to do with the amount of bandwidth available at the particular area? Like the throttling in the morning before business hours is fixed but unthrottling is dependent on bandwidth availability?

Hmmm... =\...

I've noticed one thing before and after the earthquake, 218.111 IP range used to be one of the best IP range before earthquake, but after the earthquake somehow this IP range became the worst IP range, and turned out 60.5X IP range gave me the best d/l n surfing speed, so strange.

me only got 2kbps
whats the shit happening rite now,throttling?

Don't you know it's happening all along?

i using vpn service....to bt...last week all ok can connect international peer....but today dont know y.....when i connect vpn service the streamyx will disconnect itself..i try many times to connect back. after i success connect streamyx n vpn service it show i just can connect local peer....n the other peer all gone...?the streamyx got new tech block vpn now?then really wait for hell to bt only...

is there anybody can tell me when p2p will working again??cannot use limewire...

I cant switch on my BT...once switch on then my dns goes crazy..
sh*t...

My LimeWire still can't be used (my friend's computer beside mine can).. What's the problem and how to solve it?

This post has been edited by DFlo: Feb 10 2007, 01:22 AM

jz started using ARES since limewire can't connect...

but ARES oso cannot connect...keep on sez 'connecting'

dont reveal ur p2p application here..
there's a spy here.demn.. then later ur application also cant connect.

now, limewire got no hope. but the other application is downloading fast.

Yup, other application is doing well than Limewire and Ares currently.

what application is dl fast? pm me the programs... bitcomet really hopeless le

Good news for me... my limewire is back now.. can connect and download with connection speed up to 100KB/s

Im getting a tracker error http error 500 for 3 of my BTs, anyone solutions to this?
It was downloading well for a while untill yesterday, since then i could not connect to a single seed/peer and worst of all my dl is at 98%

Guys... don't you all know that those tiny winney nuts TM is feeding us broadband just like those cookies commercials - Kejap Ada... Kejap Tak[U] Ada. So stop cracking your brain why your speed went like roller coaster.

I used to go crazy tweaking my p2p client and all the variables hoping to improve speed but now no more. Consider it kerja sia-sia coz those small nuts fellas won't change the way they do things one... Hopeless!!

My bt speed still cannot go more than 50kB/s. Most of the time less 10kB/s.

Need a Nut Cracker to be used to those small ones (TMNuts).

P2P throtle is back again, it seems.... Even the bad ping times are back!


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

Reply from 66.94.234.13: bytes=32 time=1528ms TTL=53
Reply from 66.94.234.13: bytes=32 time=1301ms TTL=54
Reply from 66.94.234.13: bytes=32 time=1466ms TTL=53
Reply from 66.94.234.13: bytes=32 time=1402ms TTL=53

Ping statistics for 66.94.234.13:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1301ms, Maximum = 1528ms, Average = 1424ms

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

Reply from 202.190.197.144: bytes=32 time=940ms TTL=52
Reply from 202.190.197.144: bytes=32 time=866ms TTL=52
Reply from 202.190.197.144: bytes=32 time=865ms TTL=52
Reply from 202.190.197.144: bytes=32 time=1078ms 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 = 865ms, Maximum = 1078ms, Average = 937ms





Attached thumbnail(s)