![]() |
Re: Bad connection Nottingham
Quote:
Agreed pem. Come on neil - you may have had a recent disagreement, but in fairness your constant pushing of alternatives has become transparent, to the point that frankly you could be construed of abusing your admin position. If its a personal opinion, fine - but remember you have authority here - I won't say don't abuse it, but step back and consider how it may be seen to a new member - 'helping customers' is now advise an alternative supplier? |
Re: Bad connection Nottingham
Quote:
|
Re: Bad connection Nottingham
Have a poor connection too (Nottingham also), slow browsing, stutter in streaming radio etc. Funny how it always happens after maintainance work :)
|
Re: Bad connection Nottingham
having exactly the same issues here in north derby :/
|
Re: Bad connection Nottingham
Quote:
I do find that the Nottingham caches (esp cache10) seem to be a bit dodgy sometimes - I have ended up switching to Leeds on a couple of occasions. |
Re: Bad connection Nottingham
Still fine in Beeston.
Out of interest, I, with my poor knowledge of these networks wonder why the OP is having problems and I'm not (the OP specifically mentioned the area I'm in so I'm thinking we can't be more than a few miles apart, yet someone in or near Derby (15 miles away) reports the same problems (as do other people in Nottingham). (I'm trying to learn something here ;)) |
Re: Bad connection Nottingham
I am no network guru, but as I understand it, Nottingham is a core point on the fibre network.
Distribution is made locally via UBR's - Nottingham Basford Clifton Stapleford Mapperley etc and also to regional outposts - Derby, Leics, Grimsby etc. Oversimplisic, but if a problem occurs regionally, it can pass down the line but will not neccessarily affect all areas. Doubtless someone will eleborate more accurately. |
Re: Bad connection Nottingham
Hey guys, there is a problem with one of the T2 Core routers in notting (i think its that way round) its being rather 'slow' to relay packets etc and should cause intermittant browsing/poor gaming pings. Will let you know when I get an update! Sorry for the inconvenience
Edit : 3 157 ms 164 ms 160 ms not-t2core-a-pos41.inet.ntl.com Yes thats the one, notice the ping times are fine up to it, and then god awfull afterwards. Hope this hasnt been pointed out already, but I just read the enough of the thread to get the jist of it Edit : Yes it would appear no one has noticed this. You should all be ashamed. Edit : Just to show im not crazy 1 11 ms 7 ms 10 ms 10.186.31.254 2 7 ms 7 ms 7 ms nott-t2cam1-a-ge-wan61-144.inet.ntl.com [80.4.47.81] Yes Yes Smooth sailing to this point 3 154 ms 156 ms 159 ms not-t2core-a-pos41.inet.ntl.com [80.1.79.61] 4 292 ms 290 ms 294 ms lee-bb-a-so-200-0.inet.ntl.com [62.253.188.33] 5 307 ms 306 ms 307 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.23] |
Re: Bad connection Nottingham
FYI guys,
If it was a cable useage problem the very first hop would be high becuse that ip is the ip of the CMTS/UBR. :) |
Re: Bad connection Nottingham
All back together again fine this morning!
|
Re: Bad connection Nottingham
Quote:
guess they didnt fix what ever problem there was... |
Re: Bad connection Nottingham
Its more likely to be worse during peak times
|
Re: Bad connection Nottingham
Its very slow currently - not had it bad like this in ages :(
Speed Test Report Broadband Speed Test - for ntl:World - 512k service By Daniel Elwell - dannyelwell2001@msn.com Get this test from http://www.vantage.pwp.blueyonder.co.uk *** THIS TEST IS NOT OWNED OR PAID FOR BY BLUEYONDER *** If you like this Speed Test, please make a donation to help me meet the development costs. No ISPs pay me to maintain this test. More information: http://www.vantage.pwp.blueyonder.co.uk/donate.htm ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ These results are only a snapshot of this particular moment. They are dependant on any other Internet use on this computer and any delays on the Internet. To improve accuracy, run the test several times. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Section 1: General Ping Results A Ping test is the time taken for a server to reply to a request ntl:World Server: 137ms - Poor - it should be less than 100ms UK Server 1 (www.demon.net): 0ms - *** PING timed out *** Tracert to specified location: Tracert was cancelled UK Server 2 (www.bbc.co.uk): 18ms - Excellent - better than expected UK Server 3 (www.ic24.net): 24ms - Normal - it's about right! USA East Coast Server (www.yahoo.com): 0ms - *** PING timed out *** Tracert to specified location: Tracert was cancelled USA West Coast Server (www.lycos.com): 96ms - Fast - very fast response European Server (www.marcopoly.com): 26ms - Excellent - better than expected ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Section 2: Custom Server Ping Results These results are to four user-definable servers. Blueyonder Counter-Strike 1: 0ms - *** PING timed out *** Tracert to specified location: Tracert was cancelled Blueyonder Team-Fortress Leage 1: 0ms - *** PING timed out *** Tracert to specified location: Tracert was cancelled BarrysWorld Master Server (all games): 0ms - *** PING timed out *** Tracert to specified location: Tracert was cancelled Japanese Ping Server (VERY long distance!): 0ms - *** PING timed out *** Tracert to specified location: Tracert was cancelled ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Section 3: Download Speed Results Three downloads are tested; one from one of your ISPs servers, one through your Transparent Cache and one through an alterntive cache. This will give you an idea of how capable your connection is. Note: You should take the highest download speed into account. ntl:World - 512k service Server Download: 9KB/s (72Kb/s) - Dismal - this is extremely poor Download through Transparent Cache: 70KB/s (560Kb/s) - Superb - much higher than expected Download through alternative Cache (webcache.blueyonder.co.uk): 0KB/s (0Kb/s) - **** SERVER ERROR: Unexpected error from Server**** ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Section 4: Packet Loss 50 Ping Requests are sent to your server. The packet loss is measured by how many of the packets don't bounce back to the client. High packet loss may slow down your connection. 50 packets were sent, 48 bounced back; 4% loss (estimated) Excellent - hardly any packets discarded ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Section 5: Transparent Cache Page Fetch Time This test times how long your Transparent Cache takes to fetch a page from the Internet. Please note that this test is subject to many different parameters and sometimes may not be 100% accurate. This test can be used to show delays when trying to view Internet sites. The timing takes place from the moment the request for the file is sent to the moment the proxy server responds. Average time taken to retrieve a page: 55ms - Fine, nothing to worry about ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Test Statistics: Information on the test Time and Date: 17/12/2003 20:02:43 Test duration: 199 secondsIP address: [Not Disclosed] Username: [Not disclosed] Test Version: 2.81 Broadband Speed Test - www.vantage.pwp.blueyonder.co.uk |
Re: Bad connection Nottingham
Pings really bad here also, web browsing and e mail seems fine.
|
Re: Bad connection Nottingham
Quote:
But please, Neil, don't tell me to sign up for Pipex: that's not the sort of advice I expect on an ntl-related site, which should be to help resolve ntl issues, not to sell another provider's services... |
| All times are GMT +1. The time now is 04:37. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum