Cable Forum - View Single Post

Chrysalis · 01-09-2005, 02:48

IRC: 70.86.*.*
this I think is theplanet, although this is a /16 range so I dont know if I hit the right isp, theplanet as far as I am aware has no problems from NTL the traffic routes over level3 which I have seen no congestion issues on.

IRC: 208.53.*.*
this one is defenitly multiple isp's but the higher end of the ip addresses are going over cogent, so your lag problems match the cogent congestion issues. To confirm need the 3rd digit please.

IRC: UK Server is fine... (16ms) (uk.quakenet.org - 213.48.150.5)
This will be fine I am unaware of any uk peering issues.

FTP: 67.15.*.*
this one also gave me cogent, so would be the same peering problems as above, although I get slow abysmal speeds during the evenings on cogent (unable to even hit the 100kB cap in place) I havent had timeouts. Although it would be possible with low timeout settings I guess.

In summary it looks likely you are a victim of ntl's overcongested peering, but I cannot confirm this sorry.

01-09-2005, 02:48	#11
Chrysalis cf.mega poster Join Date: Sep 2003 Posts: 12,050	Re: Strange lag problem IRC: 70.86.. this I think is theplanet, although this is a /16 range so I dont know if I hit the right isp, theplanet as far as I am aware has no problems from NTL the traffic routes over level3 which I have seen no congestion issues on. IRC: 208.53.. this one is defenitly multiple isp's but the higher end of the ip addresses are going over cogent, so your lag problems match the cogent congestion issues. To confirm need the 3rd digit please. IRC: UK Server is fine... (16ms) (uk.quakenet.org - 213.48.150.5) This will be fine I am unaware of any uk peering issues. FTP: 67.15.. this one also gave me cogent, so would be the same peering problems as above, although I get slow abysmal speeds during the evenings on cogent (unable to even hit the 100kB cap in place) I havent had timeouts. Although it would be possible with low timeout settings I guess. In summary it looks likely you are a victim of ntl's overcongested peering, but I cannot confirm this sorry.