My routes to the hook seem screwed.
Tracing route to //www.deadmen.co.uk [193.110.88.19]
over a maximum of 30 hops:
1 7 ms 10 ms 10 ms 192.168.0.1
2 26 ms 29 ms 30 ms btdhg512-hg1.ealing.broadband.bt.net
3 24 ms 29 ms 29 ms 217.47.30.161
4 22 ms 30 ms 29 ms 217.47.30.234
5 22 ms 29 ms 19 ms inh3cs02-500.imsnet3.btopenworld.com
6 275 ms 289 ms 290 ms btfl02-gig7-7.imsnet3.btopenworld.com
7 283 ms 289 ms 279 ms core1-pos4-3.ealing.ukcore.bt.net [194.72.9.241]
8 285 ms 279 ms 289 ms core1-pos10-0.redbus.ukcore.bt.net
9 683 ms 289 ms 289 ms linx2.telecomplete.net [195.66.226.139]
10 294 ms 300 ms 299 ms r1.tcw.telecomplete.net [193.0.255.230]
11 300 ms 300 ms 299 ms netserve-gw.cust.telecomplete.net
12 296 ms 300 ms 299 ms 193.110.88.19
to USA.COM
1 7 ms 9 ms 10 ms 192.168.0.1
2 24 ms 29 ms 30 ms btdhg512-hg1.ealing.broadband.bt.net
3 21 ms 30 ms 29 ms 217.47.30.161
4 26 ms 29 ms 29 ms 217.47.30.234
5 28 ms 29 ms 29 ms inh3cs02-500.imsnet3.btopenworld.com
6 22 ms 29 ms 29 ms btfl04-gig8-7.imsnet3.btopenworld.com
7 22 ms 160 ms 49 ms core1-pos6-2.ealing.ukcore.bt.net [194.72.9.249]
8 20 ms 29 ms 29 ms transit1-pos3-0.ealing.ukcore.bt.net [194.72.9.234]
9 55 ms 29 ms 29 ms t2c1-p1-0.uk-eal.eu.bt.net [166.49.168.13]
10 28 ms 29 ms 30 ms t2c2-p8-0.uk-lon1.eu.bt.net [166.49.208.110]
11 29 ms 29 ms 29 ms t2a1-ge7-0.uk-lon1.eu.bt.net [166.49.135.49]
12 24 ms 29 ms 29 ms ge-0.linx.londen03.uk.bb.verio.net [195.66.224.138]
13 55 ms 26 ms 29 ms p16-7-0-0.r01.londen03.uk.bb.verio.net [
14 104 ms 109 ms 109 ms p16-0-0-0.r80.nycmny01.us.bb.verio.net
15 100 ms * 109 ms p16-0-1-3.r21.nycmny01.us.bb.verio.net
16 185 ms 189 ms 189 ms p16-1-1-3.r20.sttlwa01.us.bb.verio.net
17 199 ms 189 ms 189 ms ge-0-1-0.a12.sttlwa01.us.ra.verio.net
18 177 ms 169 ms 179 ms p1-0-0-2.a12.sttlwa01.us.ce.verio.net
19 172 ms 179 ms 179 ms border3.ge2-0-bbnet1.sef.pnap.net [63.251.160.7]
20 infosp-4.border3.sef.pnap.net [63.251.162.218] reports: Destination net unreachable.
I'm having probs too. My trace appears to be b0rked at Tele House (ntl).
So i'm not the only one who has probs like this.
What's your tracert?
TL.
Tracing route to homer.deadmen.co.uk [193.110.88.20]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms SpeedTouch.lan [10.0.0.138]
2 18 ms 16 ms 16 ms lo1-bba1.th.eclipse.net.uk [212.104.130.141]
3 17 ms 16 ms 15 ms ge5-1-core4.th.eclipse.net.uk [81.5.191.41]
4 18 ms 18 ms 18 ms linx2.telecomplete.net [195.66.226.139]
5 25 ms 26 ms 26 ms r1.tcw.telecomplete.net [193.0.255.230]
6 28 ms 26 ms 26 ms netserve-gw.cust.telecomplete.net [213.160.121.26]
7 27 ms 26 ms 26 ms homer.deadmen.co.uk [193.110.88.20]
Mine sometimes borks too, I've seen 400ms + on MH recently but this is the normal route. Hmm, it's been one of these days, know whats wrong but recreating it is another matter. :angry:
Albert. Yer 5 days too late m8 :D
QuoteOriginally posted by BlueBall@Mar 12 2004, 06:47 PM
Albert. Yer 5 days too late m8 :D
That has to be the worst case of lag I've seen so far...... :whistle:
I'll get my coat.......
TL.
Slow electrons I reckon :D
Looks like possible problems at one of the NAPs.... maybe Linx? who knows.
God how many days late is this reply? :lol:
:oops:
Better late then never!
While we are at it, I had some pretty ropey connections to the server last July. Stryker, can you get that fixed please? :devil:
I was having bad pings a while back and it was always at the same router. So I sent a complaint into BT about it and they've fixed it :D Sent me a nice reply and then phoned to check it was all OK 8)
Good service.
Think we may be having the same problem down here i thought about phoning in but no need as im moving. Oldie didnt you say you had some problems as well?
Alot of these problems may be caused by cs:cz. It seems to stop and start of its own accord, even if you pause or cancel it. Another wonderful steam idea!!
QuoteOriginally posted by DarkAngel@Mar 15 2004, 11:11 PM
Think we may be having the same problem down here i thought about phoning in but no need as im moving. Oldie didnt you say you had some problems as well?
Yep. ntl forum's are full of disgruntled bods. :angry:
I think there may be issues with one of Crosswired's upstreams upstream... erm if you get my drift.
Rest assured I'm looking into it :ph34r:
QuoteYep. ntl forum's are full of disgruntled bods.
Gonna see if its any better here at my sisters as started move today think they got 128 see if i can play online with it ;) . Anyone know much about wireless cable supposed to be getting 1mb wireless dish connection in new house when we move in <_< then better once the place upgrades. Wondered if any1 has it or used it?
You know I said that my ping problems had been resolved, well, they're back again :( and it's the same router again!
C:\>tracert 193.110.88.20
Tracing route to homer.deadmen.co.uk [193.110.88.20]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 18 ms 18 ms 18 ms btdhg522-hg2.ealing.broadband.bt.net [217.47.135
.201]
3 19 ms 18 ms 20 ms 217.47.135.161
4 19 ms 20 ms 21 ms 217.47.135.238
5 20 ms 19 ms 22 ms inh3cs02-500.imsnet3.btopenworld.com [213.1.119.
62]
6 256 ms 260 ms 257 ms btfl02-gig7-7.imsnet3.btopenworld.com [213.1.119
.149]
7 251 ms 251 ms 272 ms core1-pos4-3.ealing.ukcore.bt.net [194.72.9.241]
8 274 ms 277 ms 273 ms core1-pos10-0.redbus.ukcore.bt.net [194.74.65.25
4]
9 274 ms 280 ms 276 ms linx2.telecomplete.net [195.66.226.139]
10 279 ms 282 ms 272 ms r1.tcw.telecomplete.net [193.0.255.230]
11 336 ms 281 ms 265 ms netserve-gw.cust.telecomplete.net [213.160.121.2
6]
12 257 ms 258 ms 256 ms homer.deadmen.co.uk [193.110.88.20]
Trace complete.
Oh well back to BT to find out what they're going to do about it. :angry:
I got ADSL via virgin.net (http://www.virgin.net) but I can see a few ntl boxes in that there there trace! :help:
Tracing route to homer.deadmen.co.uk [193.110.88.20]
over a maximum of 30 hops:
1 17 ms 17 ms 16 ms glfd-bam-1.inet.ntl.com [194.145.148.4]
2 17 ms 16 ms 17 ms gfd-t2core-b-ge-wan63.inet.ntl.com [62.254.207.173]
3 16 ms 18 ms 17 ms gfd-bb-b-so-300-0.inet.ntl.com [62.253.185.29]
4 20 ms 18 ms 18 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]
5 19 ms 18 ms 18 ms ntl-gw.telecomplete.net [213.160.97.41]
6 29 ms 27 ms 27 ms r1.tcw.telecomplete.net [193.0.255.230]
7 29 ms 28 ms 29 ms netserve-gw.cust.telecomplete.net [213.160.121.26]
8 30 ms 29 ms 28 ms homer.deadmen.co.uk [193.110.88.20]
Trace complete.
QuoteOriginally posted by Sn00ks@Mar 16 2004, 06:29 PM
You know I said that my ping problems had been resolved, well, they're back again :( and it's the same router again!
C:\>tracert 193.110.88.20
Tracing route to homer.deadmen.co.uk [193.110.88.20]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 18 ms 18 ms 18 ms btdhg522-hg2.ealing.broadband.bt.net [217.47.135
.201]
3 19 ms 18 ms 20 ms 217.47.135.161
4 19 ms 20 ms 21 ms 217.47.135.238
5 20 ms 19 ms 22 ms inh3cs02-500.imsnet3.btopenworld.com [213.1.119.
62]
6 256 ms 260 ms 257 ms btfl02-gig7-7.imsnet3.btopenworld.com [213.1.119
.149]
7 251 ms 251 ms 272 ms core1-pos4-3.ealing.ukcore.bt.net [194.72.9.241]
8 274 ms 277 ms 273 ms core1-pos10-0.redbus.ukcore.bt.net [194.74.65.25
4]
9 274 ms 280 ms 276 ms linx2.telecomplete.net [195.66.226.139]
10 279 ms 282 ms 272 ms r1.tcw.telecomplete.net [193.0.255.230]
11 336 ms 281 ms 265 ms netserve-gw.cust.telecomplete.net [213.160.121.2
6]
12 257 ms 258 ms 256 ms homer.deadmen.co.uk [193.110.88.20]
Trace complete.
Oh well back to BT to find out what they're going to do about it. :angry:
Snooks, your problem is quite clearly with BT, get on the phone to them!
Who do you work for again Sn00ks?
Strange :unsure:
On ISDN via Fast24 r1.tcw.telecomplete.net [193.0.255.230]
was giving me grief last night. I tracked it through on PingPlotter. But in the post above it seems clear :(
TL.
QuoteOriginally posted by TeaLeaf@Mar 17 2004, 04:35 PM
Strange :unsure:
On ISDN via Fast24 r1.tcw.telecomplete.net [193.0.255.230]
was giving me grief last night. I tracked it through on PingPlotter. But in the post above it seems clear :(
TL.
Clear? I wouldn't call
Quote10 279 ms 282 ms 272 ms r1.tcw.telecomplete.net [193.0.255.230]
particularly clear or were you getting seriously nutty mad mental horrible grief?
Nope, I was looking at suicidal_monkey's post.
Quote29 ms 27 ms 27 ms r1.tcw.telecomplete.net
I hadn't noticed Snooks, but it looks like the big nasty for him starts well before r1.tcw.telecomplete.net
I'll have a go at my ISP too though :D
TL.
Microsoft Windows XP [versie 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Dhr. Klok>cd \
C:\>tracert 193.110.88.20
Bezig met het traceren van de route naar homer.deadmen.co.uk [193.110.88.20]
via maximaal 30 hops:
1 2 ms 1 ms 1 ms SpeedTouch.lan [10.0.0.138]
2 12 ms 11 ms 10 ms 195.190.241.248
3 27 ms 17 ms 25 ms iawxsrt-pbw-bb13a.wxs.nl [195.121.255.193]
4 16 ms 16 ms 16 ms iawxsrt-m6-bb14a.wxs.nl [195.121.0.149]
5 28 ms 26 ms 27 ms amsix1.telecomplete.net [195.69.144.178]
6 36 ms 36 ms 35 ms r1.tcw.telecomplete.net [193.0.255.230]
7 36 ms 36 ms 36 ms netserve-gw.cust.telecomplete.net [213.160.121.26]
8 37 ms 36 ms 37 ms homer.deadmen.co.uk [193.110.88.20]
De trace is voltooid.
It is very rate we have an issue via telecomplete. Also the crosswired router that peers with that upstream is due an upgrade.... watch out in the server issues forum.