IanUK
11-03-2006, 17:42
HI,
As many of you know I fairly recently went through a protracted agonising 'conversation' with NTL finally involving executive office staff to get routing to my server sorted.
Well the bad routing is back :(
I REALLY REALLY do not want to go through the Call Centre route yet again, as no amount of rebooting my modem will fix this, its an NTL peering/routing problem.
The mail server is 'mail.national-net.com' who I host several sites with, and download speeds are usually about 600k, they still are in the morning but from about 3-4pm onwards they slow to less than 10k which is just unnaceptable, National net have checked and its nothing their end, which as usual leaves NTL.
This is *exactly* the same routine as last time this happened, and it took weeks of Responsetek/phone calls and emails to executive office to finally get it fixed.
I would really hope it wouldn't take that long again.
Are there any engineers here from NTL that can take a look at the routing to or from this address - specifically from about 4pm onwards.
Thanks
---------- Post added at 16:42 ---------- Previous post was at 16:09 ----------
As before I have put up a test file from the server at National Net:
http://www.froopter.com/manual.test
I'm currently getting less than 30k a sec, changing proxies so far has made no difference, as its also affecting the mail server I'd guess that proxies are not the problem.
As many of you know I fairly recently went through a protracted agonising 'conversation' with NTL finally involving executive office staff to get routing to my server sorted.
Well the bad routing is back :(
I REALLY REALLY do not want to go through the Call Centre route yet again, as no amount of rebooting my modem will fix this, its an NTL peering/routing problem.
The mail server is 'mail.national-net.com' who I host several sites with, and download speeds are usually about 600k, they still are in the morning but from about 3-4pm onwards they slow to less than 10k which is just unnaceptable, National net have checked and its nothing their end, which as usual leaves NTL.
This is *exactly* the same routine as last time this happened, and it took weeks of Responsetek/phone calls and emails to executive office to finally get it fixed.
I would really hope it wouldn't take that long again.
Are there any engineers here from NTL that can take a look at the routing to or from this address - specifically from about 4pm onwards.
Thanks
---------- Post added at 16:42 ---------- Previous post was at 16:09 ----------
As before I have put up a test file from the server at National Net:
http://www.froopter.com/manual.test
I'm currently getting less than 30k a sec, changing proxies so far has made no difference, as its also affecting the mail server I'd guess that proxies are not the problem.