Does anybody have any cast iron evidence that eclipse is throttling p2p traffic,i phoned tech support on friday to complain about the speed and the guy told me they have problems with one of their boxes (dont ask me what boxes i do not know,just what he told me)then i phoned again yesterday (saturday)spoke to a different guy and he tells me a different answer and to do a 5 speedtests but this will not tell me why my p2p is performing slower than a snail on a salt path.Nobody seems to have proof that they are throttling and eclipse denies it but it depends on who you speak to at eclipse.Anybody got any evidence please .
Another Eclipse Question(sorry)
- Thread starter davyr
- Start date
Well, so far:
Gateway starting with 212 = lots of packet loss on L8NC graph, poor P2P speed (seems capped for download and upload)
Gateway starting with 82.153 = nice P2P speed during the day, a lot less packet loss on L8NC
Last night I was throttled on P2P on the 82.153 gateway IIRC though. I've also noticed some differences in the peering with Jolt.co.uk/Pipex on the different gateways as well, on the 212 one it went all the way to Franfurt via Level3 but on the 82.153.1.4 gatway it goes 1 hop to Above.net and then straight to Pipex, then Nildram, then Jolt (as it should do)
Pings to jolt on 82.153.1.4 = 14-15ms
Pings to jolt on other gateway = 30ms
Something's definitely going on at the moment, though it's going to take either time to work out exactly what is happening (whether the low P2P cap is intentional) or for Eclipse to come out and say exactly what they're doing.
Hopefully in the end they'll just end up either:
or
A blanket cap on P2P 24/7 would be a very very bad idea IMO, but something needs to be done to stop it swamping http and other time sensitive traffic at peak periods.
Gateway starting with 212 = lots of packet loss on L8NC graph, poor P2P speed (seems capped for download and upload)
Gateway starting with 82.153 = nice P2P speed during the day, a lot less packet loss on L8NC
Last night I was throttled on P2P on the 82.153 gateway IIRC though. I've also noticed some differences in the peering with Jolt.co.uk/Pipex on the different gateways as well, on the 212 one it went all the way to Franfurt via Level3 but on the 82.153.1.4 gatway it goes 1 hop to Above.net and then straight to Pipex, then Nildram, then Jolt (as it should do)
Pings to jolt on 82.153.1.4 = 14-15ms
Pings to jolt on other gateway = 30ms
Something's definitely going on at the moment, though it's going to take either time to work out exactly what is happening (whether the low P2P cap is intentional) or for Eclipse to come out and say exactly what they're doing.
Hopefully in the end they'll just end up either:
- Throttle back P2P during peak periods and leave it unlimited for the rest of the time
or
- Dynamically shape P2P 24/7 in relation to network load
A blanket cap on P2P 24/7 would be a very very bad idea IMO, but something needs to be done to stop it swamping http and other time sensitive traffic at peak periods.
Midday yesterday I was seeing max of 50k down and 30k up on torrents, that was with encryption turned on, if that makes any difference.
Usenet was fine though, still hitting 750-800k on that.
This morning torrents looked like they were going around ~150k before I left for work.
Usenet was fine though, still hitting 750-800k on that.
This morning torrents looked like they were going around ~150k before I left for work.