How to get the lowest ping to our servers!

[TeaLeaf]

The answer to this question is easy really.  Consider using Hi-Velocity for your ADSL connection.  Here's my trace route to the dMw servers:

Tracing route to 82-197-65-246.hi-velocity.net [82.197.65.246]:

 1  <1 ms  <1 ms  <1 ms
 2  17 ms  18 ms  17 ms jenna.hi-velocity.net [82.197.70.53]
 3  17 ms  18 ms  17 ms 82-197-65-246.hi-velocity.net [82.197.65.246]

Trace complete.

Now that's 3 hops to our server on my Hi-Velocity ADSL connection - and remember, the first hop is my ADSL router, the second hop is the ADSL terminator in Redbus (Docklands, London) and the final hop is the dMw server itself.

If you are thinking that pings to other servers is important too, not just the dMw server then check out the trace routes at the bottom of this post.

So that's it folks, use Hi-Velocity as your ADSL provider and you'll find you get some stormingly good pings to our servers and the others you play on :thumbsup:  Remember, I am only just eligible for ADSL based on my line quality and distance from the exchange, so if you have a decent connection you may well see better pings.

If you want to see a trace to anywhere else then let me know.

TL.

Originally posted by Trace to Jolt servers+-->

QUOTE(Trace to Jolt servers)

Tracing route to clarity.jolt.co.uk [195.149.21.11]
over a maximum of 30 hops:

 1  <1 ms  <1 ms  <1 ms  
 2  18 ms  15 ms  17 ms jenna.hi-velocity.net [82.197.70.53]
 3  18 ms  15 ms  17 ms 82-197-65-226.hi-velocity.net [82.197.65.226]
 4  17 ms  15 ms  16 ms 82.197.95.90
 5  17 ms  16 ms  18 ms lon1-10.nildram.net [217.79.160.15]
 6  19 ms  16 ms  17 ms lon1-9.nildram.net [195.149.20.130]
 7  16 ms  18 ms  21 ms jolt-gw.nildram.net [195.149.20.126]
 8  17 ms  19 ms  18 ms clarity.jolt.co.uk [195.149.21.11]

Trace complete.[/b]

Originally posted by Trace to BoD server@
Tracing route to 213.208.119.75 over a maximum of 30 hops

 1  <1 ms  <1 ms  <1 ms  
 2  20 ms  15 ms  17 ms jenna.hi-velocity.net [82.197.70.53]
 3  19 ms  17 ms  17 ms 82-197-65-226.hi-velocity.net [82.197.65.226]
 4  17 ms  17 ms  17 ms 82.197.95.90
 5  20 ms  18 ms  18 ms lon1-10.nildram.net [217.79.160.15]
 6  16 ms  17 ms  18 ms lon1-9.nildram.net [195.149.20.130]
 7  18 ms  18 ms  18 ms jolt-gw.nildram.net [195.149.20.126]
 8  21 ms  18 ms  18 ms 213.208.119.75

Trace complete.

[Whitey]

Looking good.  My exchange gets enabled on the 2nd Feb and I'm planning on going with Hi-Velocity  :dribble:

[smite]

[Jamoe]

sadly its not the case for everyone on hi-velocity.

Tracing route to 82-197-65-246.hi-velocity.net [82.197.65.246]
over a maximum of 30 hops:

 1  <1 ms  <1 ms  <1 ms 192.168.0.1
 2  21 ms  20 ms  19 ms rdsl-lond-uk02.nw.mediaways.net [62.55.96.197]
 3  19 ms  19 ms  18 ms rmwc-lond-uk02-gigaet-6-1.nw.mediaways.net[62.55.96.9]
 4  18 ms  19 ms  20 ms rmws-lond-uk02-gigaet-0-3-0-0.nw.mediaways.net [195.71.254.21]
 5  58 ms  19 ms  19 ms rmws-lond-uk01-gigaet-0-0-0-0.nw.mediaways.net [213.20.251.237]
 6  20 ms  20 ms  19 ms linx-thn.hotlinks.co.uk [195.66.224.52]
 7  29 ms  27 ms  25 ms 82.197.95.121
 8  25 ms  23 ms  25 ms 82-197-65-246.hi-velocity.net [82.197.65.246]

Trace complete.

but i still get good pings so narnar

[TeaLeaf]

Are you connecting via xdsluk or ispnet.com?

TL.

[Jamoe]

Originally posted by TeaLeaf@Dec 27 2004, 01:05 PM
Are you connecting via xdsluk or ispnet.com?

TL.

[post=73114]Quoted post[/post]

[/b]

no idea what they are im afraid?

I was never given an option. Is there anyway I can choose? if so which one is best

cheers

EDIT 1:

ok just found out some stuff

http://forum.hi-velocity.net/modules.php?n...viewtopic&t=257

i need to try the user name with xdsluk.

im using the ispnet.com one  ill post my results if i can connect using the other

EDIT 2:

Ok i have tried using the xdsluk but it fails authentification. Ill contacted hi-V they are looking into it, I'll find out soon enough i suppose

EDIT 3:

Ive just found out BT are behind with rolling out xdsluk, it might be later in the new year for me. Ah well.

[smite]

Originally posted by Jamoe@Dec 30 2004, 01:32 PM

EDIT 3:

Ive just found out BT are behind with rolling out xdsluk, it might be later in the new year for me. Ah well.

[post=73398]Quoted post[/post]

[/b]

Bastards mate....BT should suck my cherry plum.......did i say bastards?

[Jamoe]

Tracing route to 82-197-65-246.hi-velocity.net [82.197.65.246]
over a maximum of 30 hops:

 1  <1 ms  <1 ms  <1 ms 192.168.0.1
 2  20 ms  21 ms  20 ms jenna.hi-velocity.net [82.197.70.53]
 3  22 ms  21 ms  25 ms 82-197-65-246.hi-velocity.net [82.197.65.246]

Trace complete.

Pinging 82.197.65.246 with 32 bytes of data:

Reply from 82.197.65.246: bytes=32 time=20ms TTL=125
Reply from 82.197.65.246: bytes=32 time=20ms TTL=125
Reply from 82.197.65.246: bytes=32 time=19ms TTL=125
Reply from 82.197.65.246: bytes=32 time=18ms TTL=125

Ping statistics for 82.197.65.246:
  Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
  Minimum = 18ms, Maximum = 20ms, Average = 19ms

as you can see my xdsluk realm is working

3 hops and 19 ping ohohoh so sweet.

n1 Hi-V

[Anonymous]

Not bad for Blueyonder I suppose:

TraceRoute - Friday, December 31, 2004 11:08:35

Address: 82.197.65.246 - 82.197.65.246
Number of Packets: 1
Packet size: 32
Don't Fragment: No

#1 192.168.1.1: 10 ms
#2 10.125.64.1: 10 ms
#3 gsr01-ed.blueyonder.co.uk (62.31.64.33): 10 ms
#4 194.117.136.138: 20 ms
#5 c4l.xchangepoint.net (217.79.160.68): 80 ms
#6 82-197-65-246.hi-velocity.net (82.197.65.246): 30 ms

Statistics: Out 6, in 6, loss 0%, times (min/avg/max) 10/26/80 ms

xchangepoint.net is still being a bit of a pain I see but I think TL said that would be fixed in January.

[Jamoe]

On ispnet.com

Pinging 82.197.65.246 with 32 bytes of data:

Reply from 82.197.65.246: bytes=32 time=168ms TTL=118
Reply from 82.197.65.246: bytes=32 time=181ms TTL=118
Reply from 82.197.65.246: bytes=32 time=168ms TTL=118
Reply from 82.197.65.246: bytes=32 time=165ms TTL=118

Ping statistics for 82.197.65.246:
  Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
  Minimum = 165ms, Maximum = 181ms, Average = 170ms

C:\Documents and Settings\James>tracert 82.197.65.246

Tracing route to 82-197-65-246.hi-velocity.net [82.197.65.246]
over a maximum of 30 hops:

 1  <1 ms  <1 ms  <1 ms 192.168.0.1
 2  145 ms  142 ms  155 ms rdsl-lond-uk02.nw.mediaways.net [62.55.96.197]
 3  119 ms  115 ms  122 ms rmwc-lond-uk02-gigaet-6-1.nw.mediaways.net [62.5
5.96.9]
 4  146 ms  157 ms  152 ms rmws-lond-uk02-gigaet-0-3-0-0.nw.mediaways.net [
195.71.254.21]
 5  171 ms  170 ms  168 ms rmws-lond-uk01-gigaet-0-0-0-0.nw.mediaways.net [
213.20.251.237]
 6  181 ms  164 ms  156 ms linx-thn.hotlinks.co.uk [195.66.224.52]
 7  163 ms  170 ms  166 ms 82.197.95.121
 8  168 ms  165 ms  171 ms 82-197-65-246.hi-velocity.net [82.197.65.246]

Trace complete.

On xdsluk

Tracing route to 82-197-65-246.hi-velocity.net [82.197.65.246]
over a maximum of 30 hops:

 1  <1 ms  <1 ms  <1 ms 192.168.0.1
 2  128 ms  136 ms  136 ms jenna.hi-velocity.net [82.197.70.53]
 3  132 ms  133 ms  135 ms 82-197-65-246.hi-velocity.net [82.197.65.246]

Trace complete.

C:\Documents and Settings\James>ping 82.197.65.246

Pinging 82.197.65.246 with 32 bytes of data:

Reply from 82.197.65.246: bytes=32 time=94ms TTL=125
Reply from 82.197.65.246: bytes=32 time=70ms TTL=125
Reply from 82.197.65.246: bytes=32 time=64ms TTL=125
Reply from 82.197.65.246: bytes=32 time=113ms TTL=125

Ping statistics for 82.197.65.246:
  Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
  Minimum = 64ms, Maximum = 113ms, Average = 85ms

C:\Documents and Settings\James>tracert 82.197.65.246

Tracing route to 82-197-65-246.hi-velocity.net [82.197.65.246]
over a maximum of 30 hops:

 1  <1 ms  <1 ms  <1 ms 192.168.0.1
 2  115 ms  111 ms  112 ms jenna.hi-velocity.net [82.197.70.53]
 3  120 ms  122 ms  121 ms 82-197-65-246.hi-velocity.net [82.197.65.246]

Trace complete.

worse then my isdn line . Although i believe the issue is with BT and not Hi-V, lets hope its fixed soon..

[Gh0st Face Killah]

Tracing route to 82-197-65-246.hi-velocity.net [82.197.65.246]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    11 ms    13 ms    10 ms  10.9.192.1
  3    12 ms    11 ms    11 ms  gsr01-az.blueyonder.co.uk [62.30.64.33]
  4    16 ms    14 ms    16 ms  tele1-azt-pos.telewest.net [194.117.136.2]
  5    16 ms    15 ms    16 ms  c4l.xchangepoint.net [217.79.160.68]
  6    16 ms    15 ms    16 ms  82-197-65-246.hi-velocity.net [82.197.65.246]

Trace complete.

My Blueyonder trace. Nice!!

[TeaLeaf]

Originally posted by Jamoe@Jan 3 2005, 11:59 AM
worse then my isdn line . Although i believe the issue is with BT and not Hi-V, lets hope its fixed soon..

[post=73704]Quoted post[/post]

[/b]

It is indeed a BT problem Jamoe.  BT are currently hiding behind the 'holiday season and nobody is in' excuse.  They will have their collective nuts chewed off by several of the Hi-V Directors tomorrow morning when some semblance of normality returns to BT's 'service'.  When BT fix the realm properly then the problem shoudl disappear and get back to the nice pings I posted at the top of this thread (before BT porked it for everyone).

TL.

[TeaLeaf]

All core routers were re-booted at last night for firmware and settings changes.  This appeared to improve pings etc, but as a result of clearing those issues up they found the main problem became mroe obvious.  From the Hi-V forums today:

Originally posted by "M_a_r_k_o"
Hi All

We have identified a hardware issue with the Carriers core transit router and related infrastructure and are planning on having the issue fully resolved tomorrow.

I will keep you all apprised of any developments as they happen.

Once again please accept my appologies for any inconvenience.

Regards

Mark

They hope to have it fixed by the end of today (Tuesday).  It's been the source of all the variable ping.  I guess we're just 'lucky'

TL.

[Jamoe]

hurrah, lets all cross our fingers then .

If pings are back to normal im hoping to introduce a friend to CSS tonight, (TCS style if i can), i would get him on cs/cz but he doesnt have those yet. (probably wont as he is more of a console gamer sadly)

[A Twig]

I had the best pings last night, and I was on BT