Ping woes.

[[BTF]adam]

* [BTF]Ad^m wrote to abovenet, ill post their reply if I receive one. BT one is unlikely, because I can connect to other servers (inc. east.tastysp..) and its fine, as BT is my ISP, it will be using that BT router anyway.. surely?

[console]

BT one is unlikely, because I can connect to other servers (inc. east.tastysp..) and its fine, as BT is my ISP, it will be using that BT router anyway.. surely?

It doesn't really change what I mentioned about the border routers between those two networks.  Can you post a traceroute to east.tastyspleen.net ?

[[BTF]adam]

Last one I posted was the one to east.. showing 100 or so ping.

Tracert to east server.


Tracing route to east.tastyspleen.net [69.9.168.4]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.2
  2    14 ms    14 ms    15 ms  esr1.sheffield3.broadband.bt.net [217.47.73.140]

  3    14 ms    14 ms    14 ms  217.47.73.13
  4    17 ms    15 ms    14 ms  217.41.176.17
  5    16 ms    15 ms    15 ms  217.41.176.122
  6    14 ms    13 ms    14 ms  217.41.176.58
  7    13 ms    14 ms    13 ms  217.47.110.178
  8    15 ms    14 ms    13 ms  217.32.171.213
  9    17 ms    17 ms    17 ms  core1-pos5-0.manchester.ukcore.bt.net [194.74.16
.197]
 10    21 ms    19 ms    20 ms  core1-pos3-1.bletchley.ukcore.bt.net [62.6.204.1
10]
 11    23 ms    21 ms    23 ms  core1-pos13-0.ealing.ukcore.bt.net [62.6.196.245
]
 12    25 ms    24 ms    23 ms  core1-pos5-0.telehouse.ukcore.bt.net [194.74.65.
129]
 13   106 ms   104 ms   105 ms  linx.peer.nac.net [195.66.224.94]
 14     *      108 ms   107 ms  0.so-5-0-0.gbr1.mmu.nac.net [209.123.11.53]
 15   108 ms   107 ms   108 ms  0.ge-6-0-0.gbr2.mmu.nac.net [209.123.11.10]
 16   158 ms   108 ms   108 ms  0.so-3-3-0.gbr2.nwr.nac.net [209.123.11.61]
 17   107 ms   108 ms     *     0.ge-6-2-0.gbr2.nyc.nac.net [209.123.11.181]
 18   100 ms   103 ms   102 ms  voxel-3.customer.nyc.nac.net [209.123.118.27]
 19   105 ms   103 ms   102 ms  0.so-0-1-0.cr1.lga1.us.voxel.net [69.9.185.130]

 20    99 ms    99 ms    99 ms  5.ge0-2.esw7.lga1.us.voxel.net [69.9.164.40]
 21   101 ms   102 ms    98 ms  vicious.voxel.net [69.9.166.38]
 22   104 ms   101 ms   103 ms  69.9.168.4

Trace complete.

[Art]

I'm not sure we can say for sure whether the congestion is on the bt.net end or the above.net end, meaning I think it might be possible the bt.net link to above.net is saturated and so the bt.net router (#13) is responding to pings fast itself, but is experiencing delays trying to stuff packets into a full pipe toward above.net.

[[BTF]Defiant!]

I'm west coast and get similar packet loss as Adam, though my ping is much better.  I'm fine on most servers, but have packet loss on tourney4 and ra2.

It is bad enough where I'll press to switch a weapon and it doesn't switch, or fire and it doesn fire, etc..

Def

[Lemonzest]

* Lemonzest loves 8bit dithered screen shots

back to topic tho, i noticed i get a little packet loss also on the tourney servers

[reaper]

ya , when you look at the traceroute, you can see where the latency is high.  only thing you could do is call your isp, it's their responsibility.  you can just tell them where you are trying to go, and maybe you could send them a traceroute if it shows high times
it's nice to use pathping also, to get a more accurate picture of what's going on.  it's the same thing as traceroute, but sends 100 packets to each hop instead of 1
most times when there's high latency, it's because of congestion like console mentioned

[[BTF]adam]

I emailed my ISP and they fixed it, now its back to normal :d