Dead Men Walking

Dead Men Walking - Bricks 'n Mortar => Our Server => Topic started by: GhostMjr on August 17, 2008, 08:26:12 PM

Title: Pings on server (17/8/08)
Post by: GhostMjr on August 17, 2008, 08:26:12 PM
Hi Guys,

Just got back to my parents house and loaded up css. I am getting pings of around 70ms plus. I did a tracert route and it looks like its down to the last result (green berry). I asked lee to do a tracert and he kindly did so and go the same result. Any ideas whats up? Both of us are on Virgin Media.

Thanks,

GM



QuoteTracing route to deadmen.co.uk [77.108.129.36]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.123.254
  2    16 ms     7 ms     7 ms  10.37.168.1
  3     8 ms     9 ms     9 ms  brom-t2cam1-a-v101.network.virginmedia.net [80.1
.226.113]
  4    10 ms    10 ms    19 ms  bmly-t3core-1a-ge-019-0.network.virginmedia.net
[195.182.180.193]
  5    12 ms    31 ms    23 ms  pop-bb-a-so-320-0.network.virginmedia.net [212.4
3.162.57]
  6    29 ms    12 ms    28 ms  nth-bb-b-so-010-0.network.virginmedia.net [213.1
05.172.13]
  7    11 ms    11 ms    13 ms  nth-bb-a-ae0-0.network.virginmedia.net [62.253.1
85.117]
  8    28 ms    39 ms    37 ms  fran-ic-1-so-700-0.network.virginmedia.net [62.2
53.185.81]
  9    41 ms    53 ms    28 ms  de-cix.enta.net [80.81.192.238]
 10    28 ms    39 ms    32 ms  te5-4.telecity-hex.core.enta.net [87.127.246.146
]
 11    63 ms    47 ms    50 ms  te4-1.telehouse-east.core.enta.net [87.127.236.1
01]
 12    29 ms    29 ms    29 ms  te5-1.telehouse-east2.core.enta.net [87.127.236.
98]
 13    39 ms    33 ms    37 ms  te4-1.telehouse-north.core.enta.net [87.127.236.
38]
 14    33 ms    27 ms    46 ms  bgp.brightstar-associates.co.uk.c4l [84.45.104.1
78]
 15    27 ms    27 ms    27 ms  router.brightstar.ltd.uk [77.108.128.2]
 16    67 ms    70 ms    74 ms  ashe.greenberry.co.uk [77.108.129.36]

Trace complete.
QuoteTracing route to deadmen.co.uk [77.108.129.36]
over a maximum of 30 hops:

  1     1 ms     1 ms    <1 ms  192.168.2.1
  2     6 ms     9 ms     9 ms  10.254.132.1
  3    18 ms     9 ms     9 ms  brhm-t2cam1-b-v121.network.virginmedia.net [213.
106.228.189]
  4    10 ms     8 ms     9 ms  brhm-t3core-1b-ge-012-0.network.virginmedia.net
[195.182.176.73]
  5    11 ms     9 ms     9 ms  bir-bb-b-so-020-0.network.virginmedia.net [213.1
05.174.5]
  6    11 ms    36 ms    53 ms  nth-bb-a-so-100-0.network.virginmedia.net [62.25
3.185.105]
  7    27 ms    27 ms    51 ms  fran-ic-1-so-700-0.network.virginmedia.net [62.2
53.185.81]
  8    27 ms    28 ms    29 ms  de-cix.enta.net [80.81.192.238]
  9    27 ms    27 ms    28 ms  te5-4.telecity-hex.core.enta.net [87.127.246.146
]
 10    30 ms    28 ms    31 ms  te4-1.telehouse-east.core.enta.net [87.127.236.1
01]
 11    26 ms    47 ms    27 ms  te5-1.telehouse-east2.core.enta.net [87.127.236.
98]
 12    32 ms    30 ms    28 ms  te4-1.telehouse-north.core.enta.net [87.127.236.
38]
 13    30 ms    28 ms    30 ms  bgp.brightstar-associates.co.uk.c4l [84.45.104.1
78]
 14    28 ms    29 ms    29 ms  router.brightstar.ltd.uk [77.108.128.2]
 15    70 ms    72 ms    73 ms  ashe.greenberry.co.uk [77.108.129.36]

Trace complete.
Title: Pings on server (17/8/08)
Post by: Jabbs on August 17, 2008, 11:29:26 PM
hmmmm that last result is way higher! :blink:
Title: Pings on server (17/8/08)
Post by: Anonymous on August 18, 2008, 03:07:49 AM
deadmen.co.uk is the web/forum server (separate box to the game server). My tracert to gameserver (I'm also on Virgin Media) gives:

QuoteC:\>tracert cs.deadmen.co.uk

Tracing route to cs.deadmen.co.uk [77.108.129.46]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    11 ms     8 ms    11 ms  10.125.64.1
  3    11 ms     7 ms     8 ms  80.195.0.6
  4    20 ms    18 ms    20 ms  lee-bb-b-ge-300-0.network.virginmedia.net [195.182.178.94]
  5    21 ms    19 ms    20 ms  nth-bb-a-as0-0.network.virginmedia.net [213.105.175.133]
  6    41 ms    38 ms    39 ms  fran-ic-1-so-710-0.network.virginmedia.net [212.43.162.230]
  7    37 ms    38 ms    40 ms  de-cix.enta.net [80.81.192.238]
  8    38 ms    41 ms    39 ms  te5-4.telecity-hex.core.enta.net [87.127.246.146]
  9    39 ms    39 ms    39 ms  te4-1.telehouse-east.core.enta.net [87.127.236.101]
 10    40 ms    39 ms    39 ms  te5-1.telehouse-east2.core.enta.net [87.127.236.98]
 11    37 ms    40 ms    36 ms  te4-1.telehouse-north.core.enta.net [87.127.236.38]
 12    39 ms    36 ms    50 ms  bgp.brightstar.ltd.uk.enta.net [87.127.231.114]
 13    38 ms    37 ms     *     router.brightstar.ltd.uk [77.108.128.2]
 14    39 ms    37 ms    43 ms  ba3nic1.deadmen.co.uk [77.108.129.46]

Trace complete.

C:\>
Title: Pings on server (17/8/08)
Post by: Gandalf on August 18, 2008, 07:15:07 AM
yup, ashe is the webserver. You may have been running the traces when she was doing her nightly backups, they are timed so they shouldn't impact on performance but some night owls especially like to browse when the backups are occuring!
Title: Pings on server (17/8/08)
Post by: GhostMjr on August 19, 2008, 08:05:11 PM
Hi guys thanks for the replies.

I have been having a looksie again at pingplotting/ cmd tracert plots and they are today pretty high in the telehouse areas with the plain east core causing my pings to be higher than normal.

They might be doing a backup i suppose but my pings on boomer were 60ms~80ms. All other parts of the plot showing up fine.

Is this our domain or is it outside the centre?

Also the last boomer hop is pretty high too.

Thanks for the help,

GM

QuoteTracing route to ba3nic1.deadmen.co.uk [77.108.129.46]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.123.254
  2     7 ms     7 ms     7 ms  10.37.168.1
  3     9 ms     7 ms    10 ms  brom-t2cam1-a-v101.network.virginmedia.net [80.1
.226.113]
  4    38 ms     9 ms     7 ms  bmly-t3core-1a-ge-017-0.network.virginmedia.net
[195.182.180.185]
  5    31 ms    11 ms    32 ms  pop-bb-a-so-320-0.network.virginmedia.net [212.4
3.162.57]
  6    12 ms    12 ms    10 ms  nth-bb-b-so-010-0.network.virginmedia.net [213.1
05.172.13]
  7    12 ms    35 ms    25 ms  nth-bb-a-ae0-0.network.virginmedia.net [62.253.1
85.117]
  8    32 ms    30 ms    63 ms  fran-ic-1-so-710-0.network.virginmedia.net [212.
43.162.230]
  9    39 ms    30 ms    35 ms  de-cix.enta.net [80.81.192.238]
 10    58 ms    31 ms    52 ms  te5-4.telecity-hex.core.enta.net [87.127.246.146
]
 11    68 ms   205 ms   184 ms  te4-1.telehouse-east.core.enta.net [87.127.236.1
01]
 12    32 ms    39 ms    30 ms  te5-1.telehouse-east2.core.enta.net [87.127.236.
98]
 13    50 ms    30 ms    37 ms  te4-1.telehouse-north.core.enta.net [87.127.236.
38]
 14    29 ms    31 ms    28 ms  bgp.brightstar-associates.co.uk.c4l [84.45.104.1
78]
 15    28 ms    36 ms    28 ms  router.brightstar.ltd.uk [77.108.128.2]
 16    72 ms    65 ms    65 ms  ba3nic1.deadmen.co.uk [77.108.129.46]
Title: Pings on server (17/8/08)
Post by: Jabbs on August 19, 2008, 10:40:46 PM
Here's a couple I've done tonight:

Tracing route to cs.deadmen.co.uk [77.108.129.46]
over a maximum of 30 hops:

  1    14 ms    10 ms     8 ms  10.189.0.1
  2    10 ms     8 ms    17 ms  80.235.128.33
  3   140 ms    97 ms    25 ms  195.188.231.13
  4    18 ms    11 ms    16 ms  gfd-bb-a-ge-210-0.network.virginmedia.net [195.182.178.129]
  5    12 ms    13 ms    11 ms  gfd-bb-b-ge-000-0.network.virginmedia.net [213.105.172.6]
  6    13 ms    14 ms    15 ms  redb-ic-1-as0-0.network.virginmedia.net [62.253.185.78]
  7    28 ms    29 ms    42 ms  linx-gw0.enta.net [195.66.224.151]
  8    65 ms   212 ms   156 ms  te5-1.telehouse-east2.core.enta.net [87.127.236.98]
  9    28 ms     *       28 ms  te4-1.telehouse-north.core.enta.net [87.127.236.38]
 10    14 ms    13 ms    14 ms  bgp.brightstar-associates.co.uk.c4l [84.45.104.178]
 11    13 ms    15 ms    13 ms  router.brightstar.ltd.uk [77.108.128.2]
 12    28 ms    14 ms    15 ms  ba3nic1.deadmen.co.uk [77.108.129.46]

Trace complete.


I have a feeling that there is some sort of optimisation issue at Virgin Media.  They probably wouldn't even consider it a 'problem' either.

Just wondering if anyone out there has successfully got Virgin to give them a shorter route to the internet?  I know it has been possible in the past and with specific ISP's but don't know about Virgin.

A high one at telehouse

QuoteTracing route to cs.deadmen.co.uk [77.108.129.46]
over a maximum of 30 hops:

  1    17 ms    20 ms     8 ms  10.189.0.1
  2    12 ms    18 ms    10 ms  80.235.128.33
  3    10 ms    10 ms     9 ms  195.188.231.13
  4    13 ms    11 ms    11 ms  gfd-bb-a-ge-210-0.network.virginmedia.net [195.182.178.129]
  5    12 ms    14 ms    14 ms  gfd-bb-b-ge-000-0.network.virginmedia.net [213.105.172.6]
  6    15 ms    15 ms    15 ms  redb-ic-1-as0-0.network.virginmedia.net [62.253.185.78]
  7   182 ms   204 ms   210 ms  linx-gw0.enta.net [195.66.224.151]
  8    69 ms    31 ms    31 ms  te5-1.telehouse-east2.core.enta.net [87.127.236.98]
  9    29 ms    28 ms    41 ms  te4-1.telehouse-north.core.enta.net [87.127.236.38]
 10    13 ms    23 ms    25 ms  bgp.brightstar-associates.co.uk.c4l [84.45.104.178]
 11    15 ms    15 ms    15 ms  router.brightstar.ltd.uk [77.108.128.2]
 12    14 ms    15 ms    16 ms  ba3nic1.deadmen.co.uk [77.108.129.46]

Trace complete.

A high one at enta.net though I don't know why enta.net are in the trace as they are an ISP in their own right

Third time of running all looks ok:

QuoteTracing route to cs.deadmen.co.uk [77.108.129.46]
over a maximum of 30 hops:

  1    17 ms     8 ms     9 ms  10.189.0.1
  2     8 ms    10 ms     9 ms  80.235.128.33
  3     9 ms     9 ms     9 ms  195.188.231.13
  4    11 ms    16 ms    11 ms  gfd-bb-a-ge-210-0.network.virginmedia.net [195.182.178.129]
  5    15 ms    11 ms    16 ms  gfd-bb-b-ge-000-0.network.virginmedia.net [213.105.172.6]
  6    14 ms    14 ms    16 ms  redb-ic-1-as0-0.network.virginmedia.net [62.253.185.78]
  7    27 ms    28 ms    35 ms  linx-gw0.enta.net [195.66.224.151]
  8    29 ms    31 ms    30 ms  te5-1.telehouse-east2.core.enta.net [87.127.236.98]
  9    33 ms    32 ms    29 ms  te4-1.telehouse-north.core.enta.net [87.127.236.38]
 10    15 ms    15 ms    19 ms  bgp.brightstar-associates.co.uk.c4l [84.45.104.178]
 11    13 ms    16 ms    14 ms  router.brightstar.ltd.uk [77.108.128.2]
 12    15 ms    15 ms    28 ms  ba3nic1.deadmen.co.uk [77.108.129.46]

Trace complete.

Virgin probably wouldn't even consider it a 'problem'
Title: Pings on server (17/8/08)
Post by: Penfold on August 19, 2008, 11:02:17 PM
I guess mine isn't much help

QuoteC:\>tracert cs.deadmen.co.uk

Tracing route to cs.deadmen.co.uk [77.108.129.46]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms  BelkinModem.Belkin [192.168.2.1]
  2    27 ms    27 ms    28 ms  core1.star.thn.brightstar.ltd.uk [77.108.128.38]
3    27 ms    26 ms    28 ms  ba3nic1.deadmen.co.uk [77.108.129.46]

Trace complete.
Brightstar chaps, Brightstar :thumbsup2:

PEN
Title: Pings on server (17/8/08)
Post by: Anonymous on August 20, 2008, 08:30:25 AM
telehouse and enta tend to be where the core London routers are. Its almost impossible to avoid them.

If the core routers are heavily loaded then it is not a virgin media problem although they may wish to point it out to telehouse/enta on your behalf. being  VM customer myself I know that this will happen shortly after hell freezes over.

Another possibility is that the routers have the ping response priority set to a low value so that they give higher priority to real traffic than they do to ping requests - good for traffic but makes troubleshooting a problem.
Title: Pings on server (17/8/08)
Post by: Browne on August 20, 2008, 08:42:01 AM
dont know if this will be any help as its a totally different route:

Tracing route to cs.deadmen.co.uk [77.108.129.46]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     2 ms     2 ms     2 ms  88.151.81.1
  3     3 ms     4 ms     3 ms  c3-v9-so.fastcom.ie [83.245.74.14]
  4     4 ms     3 ms     3 ms  c4-v8-so.fastcom.ie [83.245.74.34]
  5     4 ms     6 ms     4 ms  s1-v7-so.fastcom.ie [83.245.74.29]
  6     4 ms     4 ms     4 ms  r1-v8-so.fastcom.ie [83.245.74.1]
  7    10 ms    10 ms     9 ms  mm3078.dublin1.eu.level3.net [212.187.194.65]
  8    10 ms    10 ms     9 ms  ae-11-11.car1.Dublin1.Level3.net [4.69.136.93]
  9    21 ms    34 ms    20 ms  ae-5-5.ebr1.London1.Level3.net [4.69.136.90]
 10    21 ms    22 ms    20 ms  ae-11-53.car1.London1.Level3.net [4.68.116.79]
 11    20 ms    21 ms    20 ms  xe-3-3.r01.londen03.uk.bb.gin.ntt.net [129.250.8
.137]
 12    22 ms    22 ms    20 ms  83.231.146.230
 13    21 ms    21 ms    21 ms  kusanagi-wolverine.c4l.co.uk [84.45.90.41]
 14    23 ms    21 ms    22 ms  bgp.brightstar-associates.co.uk.c4l [84.45.104.1
78]
 15    21 ms    22 ms    21 ms  router.brightstar.ltd.uk [77.108.128.2]
 16    23 ms    21 ms    21 ms  ba3nic1.deadmen.co.uk [77.108.129.46]
Trace complete.
Title: Pings on server (17/8/08)
Post by: GhostMjr on August 20, 2008, 04:01:32 PM
Thanks for the replies. It looks like their may be a fault at telehouses end as its still keeping high pings to boomer and the forum. Can someone raise a support ticket about this?

Thanks,

GM
Title: Pings on server (17/8/08)
Post by: Anonymous on August 20, 2008, 04:48:15 PM
Quote from: GhostMjr;241697Thanks for the replies. It looks like their may be a fault at telehouses end as its still keeping high pings to boomer and the forum. Can someone raise a support ticket about this?

Thanks,

GM
No we cant. We have no more of a contract with Telehouse than you do. If you have high pings to Boomer through your connection then you need to raise a ticket with your ISP and get them to sort it with telehouse.

Sorry but that's the way it works, they would just ignore us.