Bad connection Nottingham
 

Hi,

Can anyone tell if there is a problem around the Beeston area in Nottingham?

I can connect, with or without my router but the speed is extreamly slow. I normaly play Starwars galaxies which is online and I use voice comms called Ventrilo, neither of these are working due to the speed of my connection.

I have tried a different proxy address and different DNS servers and this has made some improvment to web based browsing but the applications i mentioned ealier have not changed.

I tried calling NTL fault line but what ever option i choose i get a dead tone on the phone, which has given me phone rage!!!

Anyone help please?

Re: Bad connection Nottingham
 

I'm in Beeston, and eperience no problems. (With router)

Re: Bad connection Nottingham
 

I tried a tracert to microsoft.com and got these results, there where 8 or 9 time outs after the last entry.

These ping times seem very slow or is this what i should get?

Tracing route to microsoft.com [207.46.245.214]
over a maximum of 30 hops:

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]
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.238]

6 342 ms 331 ms 310 ms so-3-0-0.cr1.lhr3.uk.above.net [208.185.188.41]

7 388 ms 396 ms 388 ms so-7-0-0.cr1.dca2.us.above.net [64.125.31.186]
8 411 ms 404 ms 403 ms so-5-1-0.cr2.ord2.us.above.net [64.125.30.226]
9 530 ms 527 ms 523 ms so-5-0-0.cr2.sea1.us.above.net [64.125.30.221]
10 526 ms 528 ms 532 ms so-0-0-0.cr1.sea1.us.above.net [208.185.175.185]

11 * 546 ms 565 ms pos9-0.mpr1.sea1.us.above.net [208.185.175.177]

12 368 ms 370 ms 382 ms microsoft-above-oc12.sea1.above.net [64.125.12.1

Re: Bad connection Nottingham
 

You (like most people in your area) are probably on an oversubscribed UBR. :rolleyes:

Welcome to nthw btw. :wavey:

Re: Bad connection Nottingham
 

Hmm. I get pretty much the same, but don't really experience problems browsing. (Can get onto the microsoft site without problems)


Tracing route to www2.microsoft.akadns.net [207.46.134.157]
over a maximum of 30 hops:

1 13 ms 9 ms 13 ms 10.
2 12 ms 11 ms 14 ms nott-t2cam1-a-ge-wan61-141.inet.ntl.com [80.4.46
.25]
3 157 ms 164 ms 160 ms not-t2core-a-pos41.inet.ntl.com [80.1.79.61]
4 285 ms 293 ms 298 ms lee-bb-a-so-300-0.inet.ntl.com [62.253.185.33]
5 321 ms 314 ms 293 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

6 300 ms 302 ms 310 ms so-3-0-0.cr1.lhr3.uk.above.net [208.185.188.41]

7 372 ms 375 ms 397 ms so-7-0-0.cr1.dca2.us.above.net [64.125.31.186]
8 394 ms 393 ms 389 ms so-5-1-0.cr2.ord2.us.above.net [64.125.30.226]
9 449 ms 469 ms 463 ms so-5-0-0.cr2.sea1.us.above.net [64.125.30.221]
10 481 ms 468 ms 464 ms so-0-0-0.cr1.sea1.us.above.net [208.185.175.185]

11 451 ms 463 ms 467 ms pos9-0.mpr1.sea1.us.above.net [208.185.175.177]

12 333 ms 341 ms 331 ms microsoft-above-oc12.sea1.above.net [64.125.12.1
8]
13 444 ms 450 ms 451 ms 207.46.33.225
14 * 442 ms 451 ms 207.46.36.66
15 463 ms 463 ms 456 ms 207.46.155.17
16 * * * Request timed out.
17 * * * Request timed out.
18 *

Re: Bad connection Nottingham
 

I use this connection most nights to play Starwars and use voice comms. I very very rarely have problems other then the DNS issues everyone had a month or so ago.

Something is wrong here, not sure if its with my cable modem box or not. I've tried my laptop and get the same problems. So unless hundreds of new users have apeared over night i doubt its that my UBR (whats that?) is over subscribed.

Wish there was an easy way of sorting things with NTL. Some times i would rarther stick pins in my eyes then deal with NTL CS.

Re: Bad connection Nottingham
 

I don't know if this is relevant, but I notice that microsoft.com resolves to different ip addresses for you and me. Could we be accessing a different DNS server?

Just guessing here, to be honest, but you never know ;)

Re: Bad connection Nottingham
 

there is a known fault in Nottingham at the moment..unsure if resolved yet... can't see it on the Status Page though :rolleyes:

Re: Bad connection Nottingham
 

Take a look at a proper Server Status Report.....

http://www.solo.pipex.net/cgi-bin/ns...n=Connectivity

Re: Bad connection Nottingham
 

I wish I could use a different ISP but as far as I know NTL are the only ones offering cable in my area.

I don't think Iâ₠¬ÃƒÆ’¢â€žÂ¢ve ever seen such an appalling customer service as NTL. It's always been this way and I doubt it will ever change.

Re: Bad connection Nottingham
 

Im having browsing trouble also cant see the NTL service page

The page cannot be displayed

The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings.

had trouble connecting to this site just now had to resort to a diffrent proxy

Re: Bad connection Nottingham
 

I presume you can get a BT phone line?

That is all you need. :)

http://216.40.241.59/forum/showthread.php?t=4697

Re: Bad connection Nottingham
 

Browsing & d/ls are the pits in North East Lincs tonight - Nottingham franchise. Tried changing proxies with only marginally better results.

Re: Bad connection Nottingham
 

Why put up with it?

Follow the link I gave above, & get a reliable provider.

Re: Bad connection Nottingham
 

You really are on a one man mission to sl*g off NTL in favour of Pipex arn't you.

Out of interest, how many BB customers does pipex have ?

(FYI, I am on the Nottingham franchise and my service is just fine, one failure in 2 years).

Re: Bad connection Nottingham
 

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
 

so far it seems to be the cache servers?

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
 

Which part of Nottingham are you in (or which ubr's are you on) - I'm in North Nottingham on the Basford UBR's and they have never been a problem.

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
 

Just tried again and its the same as this time last night. Around 11pm last night it did clear up a bit but was still slow. I'm trying Starwars galaxies now and i'm getting time outs again from the servers.

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
 

Agreed - the pits again this evening.

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...

Re: Bad connection Nottingham
 

<hangs his head in shame> :blush:

Re: Bad connection Nottingham
 

Its the same again for me tonight and i dont live in Robin Hood country.

The only connection i have to Robin Hood Country is that my local NTL franchise covers that area.

Im getting :sick: of changing proxys at peek times of the night just to view local web forums.

Re: Bad connection Nottingham
 

Do a trace route, if your pings are not excessive after and including "t2core" it would be safe to assume you have a different fault not related to the problems t2 is having routing data.

If t2core is not in the trace then it definatly not related to the problem with t2.

Re: Bad connection Nottingham
 

It's not that easy Neil :(

For Telephone Number 01522793xxx on Exchange WASHINGBOROUGH

Sorry - ADSL broadband is not yet available in your area, but we are currently assessing demand.

Re: Bad connection Nottingham
 

i'm getting abysmal download speeds (in newark) - downloading at a miserable 3.4k when it should be maxed out - WHAT THE HELL IS WRONG WITH THIS DAMNED SERVICE?

Re: Bad connection Nottingham
 

You can register your interest but you dont have to have ADSL when your local BT exchange becomes ADSL enabled.

___

When doing a tracert to this forum when i have problems like "this page cannot be displayed" (i could be moving from forum to forum and i get this error when im already browsing the NTHell forum) passing via the ntl servers is ok till the trace moves outside then the pings shoot up and time out, using a different DNS to the NTL's transparent web cache the path is clear and i get no problems.

Re: Bad connection Nottingham
 

a little more info and we might be able to tell you!

Re: Bad connection Nottingham
 

Surely just about every other post on this thread gives that info!!

Re: Bad connection Nottingham
 

do i have the t2core issue?

1 <1 ms <1 ms <1 ms [192.168.0.1]
2 12 ms 7 ms 7 ms 10.145.23.254
3 11 ms 11 ms 15 ms nott-t2cam1-a-v127.inet.ntl.com [80.4.46.81]
4 150 ms 152 ms 148 ms not-t2core-a-ge-wan61.inet.ntl.com [80.1.79.57]

5 141 ms 142 ms 139 ms lee-bb-a-so-300-0.inet.ntl.com [62.253.185.33]
6 148 ms 150 ms 153 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

7 153 ms 146 ms 145 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
8 156 ms * 135 ms so-7-0.hsa2.London1.Level3.net [212.113.14.129]

9 129 ms 128 ms 127 ms so-4-0-0.mp1.London1.Level3.net [212.187.131.121
]
10 151 ms 154 ms 146 ms so-1-0-0.mp1.London2.Level3.net [212.187.128.49]

11 193 ms 191 ms 196 ms so-1-0-0.bbr1.Washington1.Level3.net [212.187.12
8.138]
12 254 ms 252 ms 245 ms so-0-1-0.mp2.Phoenix1.Level3.net [64.159.1.122]

13 258 ms 258 ms 258 ms ge-11-0.hsa1.Phoenix1.Level3.net [64.159.3.110]

14 256 ms 251 ms 257 ms ge2-2-1000M.4iron.phx1.puregig.net [63.214.160.1
54]
15 257 ms 256 ms 253 ms ge2-4-1000m.sw1.core.phx1.puregig.net [140.99.96
.45]
16 256 ms 254 ms 255 ms zip.members.easynews.com [140.99.99.100]

Re: Bad connection Nottingham
 

Seems we both do:

Tracing route to zip.members.easynews.com [140.99.99.100]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.*.*
2 16 ms 9 ms 10 ms 10.145.*.*
3 9 ms 9 ms 10 ms nott-t2cam1-a-ge-wan53-137.inet.ntl.com [80.4.46
.65]
4 129 ms 148 ms 127 ms not-t2core-a-ge-wan61.inet.ntl.com [80.1.79.57]

5 120 ms 121 ms 148 ms lee-bb-a-so-300-0.inet.ntl.com [62.253.185.33]
6 127 ms 125 ms 124 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

7 128 ms 124 ms 131 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
8 125 ms 132 ms 127 ms so-7-0.hsa2.London1.Level3.net [212.113.14.129]

9 129 ms * 108 ms so-4-0-0.mp1.London1.Level3.net [212.187.131.121
]
10 107 ms 106 ms 113 ms so-1-0-0.mp1.London2.Level3.net [212.187.128.49]

11 179 ms 178 ms 180 ms so-1-0-0.bbr1.Washington1.Level3.net [212.187.12
8.138]
12 234 ms 253 ms 232 ms so-0-1-0.mp2.Phoenix1.Level3.net [64.159.1.122]

13 233 ms 231 ms 230 ms ge-11-0.hsa1.Phoenix1.Level3.net [64.159.3.110]

14 238 ms 261 ms 242 ms ge2-2-1000M.4iron.phx1.puregig.net [63.214.160.1
54]
15 231 ms 245 ms 238 ms ge2-4-1000m.sw1.core.phx1.puregig.net [140.99.96
.45]
16 230 ms 234 ms 236 ms zip.members.easynews.com [140.99.99.100]

Also from Robin's Test:

Thu, 18 Dec 2003 18:12:43 UTC
1st 128K took 1781 ms = 73595 Bytes/sec = approx 612 kbits/sec
2nd 128K took 1844 ms = 71080 Bytes/sec = approx 591 kbits/sec
3rd 128K took 2844 ms = 46087 Bytes/sec = approx 383 kbits/sec
4th 128K took 22453 ms = 5838 Bytes/sec = approx 49 kbits/sec

thats normally constant around the top 600 mark

Re: Bad connection Nottingham
 

I'm not sure what you are trying to say here - tracert shows the direct IP path from you to the target IP, it has no connection with any proxy servers or the dns servers they may be using.

JSS & Nikko - yes, as Nikko has observed - you are both routing through the dodgy router (80.1.79.57).

Re: Bad connection Nottingham
 

Im in notts too, and im getting the same problem, funnily enough my gaming pings are fine and dandy on UK server, but amazingly shabby with alot of packetloss on servers outside of the uk (NL, Sweden, etc)

Quite annoying too, missed 2 clan games cause of this and ill probably miss more

Heres a Tracert to one of those foreign game servers.

Tracing route to alpha.es-servers.nl [81.173.116.140]
over a maximum of 30 hops:

1 11 ms 8 ms 24 ms 10.144.191.254
2 8 ms 11 ms 9 ms nott-t2cam1-a-ge-wan53-136.inet.ntl.com [80.4.46
.21]
3 1192 ms 159 ms 151 ms not-t2core-a-pos41.inet.ntl.com [80.1.79.61]
4 134 ms 131 ms 134 ms lee-bb-a-so-200-0.inet.ntl.com [62.253.188.33]
5 148 ms 143 ms 146 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

6 137 ms 140 ms 143 ms so-3-0-0.cr1.lhr3.uk.above.net [208.185.188.41]

7 159 ms 137 ms 145 ms so-0-0-0.cr2.lhr3.uk.above.net [208.184.231.146]

8 177 ms 151 ms 177 ms pos9-0.cr2.ams2.nl.above.net [64.125.31.158]
9 156 ms 158 ms 151 ms pos1-0.mpr2.ams1.nl.above.net [208.184.231.253]

10 126 ms 123 ms 140 ms amsix.globalswitch.netholding.nl [195.69.144.79]

11 * 127 ms 130 ms alpha.es-servers.nl [81.173.116.140]

Trace complete.

(I think this problem started on tuesday, when ntl were supposed to be doing their so called maintenance? =/ i think they broke it :P)

Re: Bad connection Nottingham
 

Using an NTL transparent cache

Tracing route to nthellworld.co.uk [216.40.241.59]
over a maximum of 30 hops:

1 134 ms 131 ms 131 ms
2 160 ms 111 ms 161 ms midd-t2cam1-a-ge-wan34-103.inet.ntl.com [213.106.238.17]
3 143 ms 110 ms 112 ms midd-t2core-a-ge-wan61.inet.ntl.com [213.106.237.33]
4 112 ms 110 ms 112 ms lee-bb-a-so-130-0.inet.ntl.com [62.253.187.89]
5 117 ms 117 ms 155 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
6 120 ms 126 ms 119 ms tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]
7 319 ms 319 ms 321 ms lndnuk1icx1.wcg.net [195.66.224.105]
8 330 ms 338 ms 352 ms nycmny2wcx2-oc12.wcg.net [64.200.87.149]
9 331 ms 331 ms 359 ms hrndva1wcx2-pos5-0.wcg.net [64.200.210.97]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.


_______
Tracing route to nthellworld.co.uk [216.40.241.59]
over a maximum of 30 hops:

1 11 ms 10 ms 10 ms
2 11 ms 9 ms 10 ms midd-t2cam1-a-ge-wan34-103.inet.ntl.com [213.106.238.17]
3 9 ms 10 ms 12 ms midd-t2core-a-ge-wan61.inet.ntl.com [213.106.237.33]
4 11 ms 12 ms 11 ms lee-bb-a-so-130-0.inet.ntl.com [62.253.187.89]
5 17 ms 16 ms 20 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
6 18 ms 20 ms 19 ms tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]
7 22 ms 22 ms 20 ms lndnuk1icx1.wcg.net [195.66.224.105]
8 131 ms 132 ms 130 ms nycmny2wcx2-oc12.wcg.net [64.200.87.149]
9 130 ms 130 ms 130 ms hrndva1wcx2-pos5-0.wcg.net [64.200.210.97]
10 130 ms 130 ms 129 ms hrndva1wcx3.oc48.wcg.net [64.200.95.78]
11 131 ms 129 ms 129 ms drvlga1wcx2-pos.wcg.net [64.200.210.57]
12 130 ms 135 ms 129 ms drvlga1wcx1-oc48.wcg.net [64.200.127.29]
13 131 ms 129 ms 155 ms dllstx1wcx3-oc48.wcg.net [64.200.240.21]
14 130 ms 129 ms 129 ms dllstx1wcx2-oc48.wcg.net [64.200.110.73]
15 130 ms 129 ms * hstntx1wce2-pos4-0.wcg.net [64.200.240.74]
16 135 ms 133 ms * hstntx1wce2-everyonesinternet-gige.wcg.net [65.77.93.54]
17 119 ms 120 ms 153 ms ivhou-207-218-223-34.ev1.net [207.218.223.34]

Big difference between the two even though the pings are v high

Re: Bad connection Nottingham
 

80.1.79.57 seems to have woken up, pem:


Tracing route to www.ntlworld.com [62.253.162.30]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.*.* 2 27 ms 13 ms 8 ms 10.145.*.*
3 9 ms 9 ms 10 ms nott-t2cam1-a-ge-wan53-137.inet.ntl.com [80.4.46
.65]
4 11 ms 45 ms 11 ms not-t2core-a-ge-wan61.inet.ntl.com [80.1.79.57]

5 12 ms 11 ms 11 ms lee-bb-a-so-300-0.inet.ntl.com [62.253.185.33]
6 23 ms 16 ms 34 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

7 16 ms 18 ms 17 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
8 48 ms 17 ms 18 ms win-bb-b-so-500-0.inet.ntl.com [62.253.185.202]

9 22 ms 18 ms 20 ms win-bb-a-ae0-0.inet.ntl.com [213.105.172.161]
10 22 ms 16 ms 21 ms win-dc-a-v900.inet.ntl.com [62.253.188.162]
11 19 ms 19 ms 22 ms www.ntlworld.com [62.253.162.30]

Trace complete.

Re: Bad connection Nottingham
 

Well hopefully someone has given it a good kicking ;)


Both those traces show what I said, they are both taking exactly the same route on the NTL network to the Telehouse LINX ;

2 midd-t2cam1-a-ge-wan34-103.inet.ntl.com [213.106.238.17]
3 midd-t2core-a-ge-wan61.inet.ntl.com [213.106.237.33]
4 lee-bb-a-so-130-0.inet.ntl.com [62.253.187.89]
5 pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
6 tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]

Once they leave NTL's network they are still taking the same route but then the trace on the first one stops in the middle of the Williams Communications (US) network for some reason;

First;
7 lndnuk1icx1.wcg.net [195.66.224.105]
8 nycmny2wcx2-oc12.wcg.net [64.200.87.149]
9 hrndva1wcx2-pos5-0.wcg.net [64.200.210.97]
10 * * * Request timed out.
Second;
7 lndnuk1icx1.wcg.net [195.66.224.105]
8 nycmny2wcx2-oc12.wcg.net [64.200.87.149]
9 hrndva1wcx2-pos5-0.wcg.net [64.200.210.97]
10 hrndva1wcx3.oc48.wcg.net [64.200.95.78]
11 drvlga1wcx2-pos.wcg.net [64.200.210.57]
12 drvlga1wcx1-oc48.wcg.net [64.200.127.29]
13 dllstx1wcx3-oc48.wcg.net [64.200.240.21]
14 dllstx1wcx2-oc48.wcg.net [64.200.110.73]
15 hstntx1wce2-pos4-0.wcg.net [64.200.240.74]
16 hstntx1wce2-everyonesinternet-gige.wcg.net [65.77.93.54]
17 ivhou-207-218-223-34.ev1.net [207.218.223.34]


Having said all this, your second trace starts out badly on the first step [for which you seem to have removed the IP & name details] - this is your UBR so it may be you have a local problem. (This may have been what interrupted the first trace as well).

Re: Bad connection Nottingham
 

DrAwesome transparent cache will do nothing to the ping times. Pings/trace's are ICMP requests and not get effected by cache servers

Re: Bad connection Nottingham
 

A quick check without typing tracert (what ever) in a dos prompt here 2 sample Unix traceroutes between the Giganews servers and your current location if it helps those that are lazy.

my connection during the day

news-40.giganews.com
1 330.ge-4-2-0.mpr2.iah1.us.above.net (64.125.104.19) 0.857 ms 0.676 ms 0.594 ms
2 pos-0-0.er1.atl4.us.above.net (64.125.29.69) 13.480 ms 13.379 ms 13.409 ms
3 pos12-0.pr1.atl4.us.above.net (64.125.30.234) 13.408 ms 13.243 ms 13.263 ms
4 so-5-3-0.cr1.dca2.us.mfnx.net (208.184.232.49) 24.601 ms 24.587 ms 24.565 ms
5 so-6-0-0.cr1.lhr3.uk.above.net (64.125.31.185) 96.626 ms 96.438 ms 96.424 ms
6 pop-bb-b-so-330-0.inet.ntl.com (208.185.188.42) 96.496 ms 96.378 ms 96.372 ms
7 lee-bb-a-so-700-0.inet.ntl.com (62.253.185.237) 101.947 ms 101.843 ms 101.903 ms
8 midd-t2core-a-pos31.inet.ntl.com (62.253.187.90) 103.400 ms 103.247 ms 103.329 ms
9 cache8-midd.server.ntli.net () 109.268 ms 109.136 ms 109.124 ms

news-60.giganews.com
1 gw1-vlan201.ash.giganews.com (216.196.98.2) 26 ms 38 ms 2 ms
2 g3-2.gw1.ash.giganews.com (64.200.88.101) 0 ms 0 ms 0 ms
3 hrndva1wcx2-pos0-0.wcg.net (64.200.89.49) 79 ms 79 ms 79 ms
4 nycmny2wcx2-oc48.wcg.net (64.200.240.45) 7 ms 7 ms 7 ms
5 lndnuk1lcx1-oc12.wcg.net (64.200.87.150) 78 ms 78 ms 78 ms
6 linx-gw2.router.ntli.net (195.66.226.22) 78 ms 79 ms 79 ms
7 pop-bb-b-so-430-0.inet.ntl.com (62.253.185.81) 78 ms 78 ms 78 ms
8 lee-bb-a-so-700-0.inet.ntl.com (62.253.185.237) 84 ms 83 ms 83 ms
9 midd-t2core-a-pos31.inet.ntl.com (62.253.187.90) 85 ms 85 ms 85 ms
10 cache8-midd.server.ntli.net () 91 ms 91 ms 91 ms

Re: Bad connection Nottingham
 

Does anybody know if this problem is resolved yet? I am actually getting fine pings ingame BUT it is rather shaky, with high pings sometimes, quite unstable.
As with tracerts, 1 second the ping to the t2core thing is like 600 and the next its sub 100.

Was wondering if it was resolved yet as i dunno what to make of it, and i wouldnt want to assume because i know ntl are rather random with their problems =/

Re: Bad connection Nottingham
 

DrAwesome, return path trace routes, ie from someone else to you do not take the same path as ones from you. As you will notice there are only 4 ntl servers there and one of them is the cache server. It wont give a reliable representation of what is happening.

If you wan to use a web based package to test server responce times use Visual Route (http://visualroute.visualware.co.uk/)