Server on the fritz?

[Shaun]

Example:


C:\>tracert www.cyclechat.net

Tracing route to www.cyclechat.net [80.87.131.154]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.10.1
2 7 ms 7 ms 7 ms static-xx-xx-xx-xx.karoo.KCOM.COM [xx.xx.xx.xx]
3 204 ms 203 ms 216 ms 10.102.241.201
4 14 ms 58 ms 32 ms 10.102.240.221
5 12 ms 12 ms 12 ms 10.102.57.7
6 12 ms 12 ms 13 ms ldn-s2-rou-1041.UK.eurorings.net [134.222.146.54
]
7 14 ms 14 ms 14 ms ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]

8 19 ms 15 ms 15 ms xe-1-0-0.mpr2.lhr3.uk.above.net [64.125.27.174]

9 15 ms 14 ms 15 ms ge-3-3-0.mpr1.lhr3.uk.above.net [64.125.28.145]

10 14 ms 14 ms 15 ms 213-152-252-220.available.above.net [213.152.252
.220]
11 21 ms 21 ms 22 ms www.tvshack.net [80.87.131.154]

Trace complete.

C:\>

(NOTE TO TECHIES: Yes, I know the destination is wrong - my local ISP is having DNS issues, which is really helpful when I'm trying to diagnose the server NOT!!)

 

[ianrauk]

Tracing route to www.cyclechat.net [80.87.131.154]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms homeportal [192.168.1.254]
2 2 ms 42 ms 47 ms host81-134-96-1.in-addr.btopenworld.com [81.134.
96.1]
3 48 ms 45 ms 42 ms 213.120.182.141
4 29 ms 41 ms 40 ms 213.120.161.82
5 33 ms 49 ms 50 ms 217.41.222.22
6 50 ms 57 ms 41 ms 217.41.222.178
7 43 ms 39 ms 40 ms acc1-10GigE-0-7-0-4.bm.21cn-ipp.bt.net [109.159.
248.70]
8 48 ms 54 ms 50 ms core-te0-4-0-4.ealing.ukcore.bt.net [109.159.248
.9]
9 38 ms 50 ms 63 ms transit1-xe0-0-0.ealing.ukcore.bt.net [62.6.200.
106]
10 39 ms 51 ms 54 ms t2c1-ge14-0-0.uk-eal.eu.bt.net [166.49.168.25]
11 53 ms 66 ms 54 ms t2c2-p3-0-0.uk-lon1.eu.bt.net [166.49.208.210]
12 56 ms 43 ms 52 ms t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.110]

13 45 ms 60 ms 37 ms ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]

14 46 ms 41 ms 56 ms xe-1-0-0.mpr2.lhr3.uk.above.net [64.125.27.174]

15 56 ms 49 ms 48 ms ge-4-2-0.mpr1.lhr3.uk.above.net [64.125.27.157]

16 52 ms 44 ms 44 ms 213-152-252-220.available.above.net [213.152.252
.220]
17 52 ms 56 ms 62 ms pod-154.dolphin-server.co.uk [80.87.131.154]

Trace complete.

 

[Shaun]

Thanks Ian.

 

[theclaud]

I'm rather disappinted that this thread has nothing to do with Irving Berlin...

 

[Bman]

Tracing route to [url="http://www.cyclechat.net"]www.cyclechat.net[/url] [80.87.131.154]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms [192.168.0.1]
2     7 ms    64 ms    10 ms  cpc2-stev6-2-0-gw.9-2.cable.virginmedia.com [213.107.88.1]
3    27 ms    10 ms     9 ms  lutn-core-1a-ge-300-2088.network.virginmedia.net [80.4.221.21]
4    22 ms     8 ms     9 ms  popl-bb-1a-as5-0.network.virginmedia.net [213.105.175.149]
5    10 ms    11 ms    11 ms  popl-bb-1b-ae0-0.network.virginmedia.net [213.105.174.230]
6    10 ms    11 ms    12 ms  glfd-bb-1a-so-010-0.network.virginmedia.net [213.105.172.137]
7    22 ms    23 ms    23 ms  213.152.245.49
8   218 ms   208 ms     *     so-1-1-0.mpr1.lhr3.uk.above.net [64.125.27.222]
9    23 ms    23 ms    23 ms  213-152-252-220.available.above.net [213.152.252.220]
10    28 ms    27 ms    39 ms  pod-154.dolphin-server.co.uk [80.87.131.154]

Trace complete.

 

[Shaun]

Thanks.

 

[ColinJ]

tracert www.cyclechat.net

Tracing route to www.cyclechat.net [80.87.131.154]
over a maximum of 30 hops:

1 * * * Request timed out.
2 40 ms 38 ms 39 ms lo98.sc-acc-sip-2.as9105.net [212.74.102.15]
3 38 ms 64 ms 37 ms 10.72.4.49
4 93 ms 39 ms 38 ms 10.72.4.126
5 39 ms 38 ms 38 ms xe-0-2-0-10.lon10.ip4.tinet.net [213.200.77.73]
6 39 ms 38 ms 38 ms xe-2-0-0.lon14.ip4.tinet.net [89.149.183.170]
7 55 ms 38 ms 38 ms xe-5-3-0.mpr1.lhr1.uk.above.net [64.125.12.105]
8 39 ms 39 ms 40 ms xe-3-3-0.mpr2.lhr3.uk.above.net [64.125.28.97]
9 39 ms 41 ms 39 ms ge-3-3-0.mpr1.lhr3.uk.above.net [64.125.28.145]
10 41 ms 39 ms 39 ms 213-152-252-220.available.above.net [213.152.252.220]
11 45 ms 46 ms 46 ms pod-154.dolphin-server.co.uk [80.87.131.154]

Trace complete.

 

[Shaun]

Thanks

 

[sgw]

Don't know if you still need these but:-
----

Tracing route to www.cyclechat.net [80.87.131.154]
over a maximum of 30 hops:

1 773 ms 479 ms 460 ms 172.30.132.209
2 1015 ms 479 ms 479 ms 195.50.119.9
3 911 ms 459 ms 499 ms ae-4-4.ebr1.London1.Level3.net [4.69.133.102]
4 407 ms 469 ms 499 ms ae-12-51.car2.London1.Level3.net [4.69.139.67]
5 415 ms 497 ms 479 ms xe-3-2-0.mpr1.lhr1.uk.above.net [64.125.14.17]
6 441 ms 529 ms 509 ms xe-0-0-0.mpr2.lhr3.uk.above.net [64.125.27.162]

7 459 ms 499 ms 459 ms ge-3-1-0.mpr1.lhr3.uk.above.net [64.125.27.153]

8 415 ms 509 ms 489 ms 213-152-252-220.available.above.net [213.152.252
.220]
9 439 ms 520 ms 588 ms pod-154.dolphin-server.co.uk [80.87.131.154]

Trace complete.

----

Haven't had a problem here today but got a few "Data Base" errors over last few days.

 

[Shaun]

The database errors will have been due to me stopping and starting the database server after making configuration changes, sorry. I've stopped twiddling with it for now, so those should go away. (If you do notice any, please post the details in Feedback, thanks).

THE GOOD NEWS is that the datacentre have confirmed they've noticed the outage issue too so they're going to look into it.

If you do notice the site being unresponsive for more than 10 seconds or so, please post the time and how long it was off in here so I can report back to them. In the meantime, they're trying to figure out what's going on at their end so hopefully it'll be resolved soon enough. (Although it may take a little while due to the intermittent nature of it.)

Cheers,
Shaun

 

[Shaun]

Just noticed some "stuttering" over the past few minutes - anyone else?

Cheers,
Shaun

 

[ColinJ]

Just noticed some "stuttering" over the past few minutes - anyone else?

Cheers,
Shaun

I have, though my system sometimes 'stutters' on other sites too so that doesn't necessarily mean much...

 

[Bman]

yes, a few timeouts here over the last hour or two

 

[ColinJ]

CC has been annoyingly intermittent for me today. Sites in other browser tabs have been fine so my connection was okay.

 

[Shaun]

Network issues at the datacentre; they're working on it, but it's intermittent so will be a bugger to pin down.

They're top class techies though, so I've no doubt they'll sort it before too long.

Cheers,
Shaun