Ping Spikes to BC2 server(s). Mweb hosted?

[Lounger]

Getting some hefty ping spikes to the following game server.

It's the Uprising Mercenaries (UM) for Battlefield BC2 [196.28.69.90:19567]

Some other servers are the same - like Chaos. WebAfrica servers are fine.

Ping changes from 110 (roughly) to 999 or inbetween.

I see it goes through Mweb, so not totally surprised.

C:\Users\Me>tracert 196.28.69.90

Tracing route to 196.28.69.90 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  192.168.1.1
  2    25 ms    25 ms    25 ms  1.24.177.41-discover.co.za [41.177.24.1]
  3    24 ms    61 ms    26 ms  196.6.121.38-backbone.cybersmart.co.za [196.6.12
1.38]
  4    47 ms    48 ms    49 ms  198.32.214.32
  5    50 ms    48 ms    49 ms  GigabitEthernet0-2-1-4.cpt-up-1.mweb.co.za [196.
28.178.138]
  6    50 ms    51 ms    52 ms  GigabitEthernet0-0-1-7.vic-up-1.mweb.co.za [196.
22.169.49]
  7    48 ms    48 ms    49 ms  vl-12.vic-hscore-2.mweb.co.za [196.22.169.243]
  8    48 ms    48 ms    48 ms  tengig-3-2.vic-core-sw2.mweb.co.za [196.22.169.7
0]
  9    46 ms    48 ms    45 ms  opt-65-1.optinet.net [196.22.163.22]
 10    49 ms    47 ms    84 ms  196.28.69.90

Trace complete.

C:\Users\Me>tracert 196.28.69.90

Tracing route to 196.28.69.90 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  192.168.1.1
  2    24 ms    25 ms    25 ms  1.24.177.41-discover.co.za [41.177.24.1]
  3    24 ms    26 ms    26 ms  196.6.121.38-backbone.cybersmart.co.za [196.6.12
1.38]
  4    46 ms    47 ms    50 ms  198.32.214.32
  5    49 ms    48 ms    47 ms  GigabitEthernet0-2-1-4.cpt-up-1.mweb.co.za [196.
28.178.138]
  6     *       51 ms    50 ms  GigabitEthernet0-0-1-7.vic-up-1.mweb.co.za [196.
22.169.49]
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *       50 ms  196.28.69.90

Trace complete.

C:\Users\Me>

[TheHxckid]

The Hillbrow 1000 tickets server also had the weirdest lag. Ping would display fine but it would lag immensly.

[dadiggle]

check out the message log -- are the round trip times going up in spikes? If yes, fire up the task manager, locate the client process (the name depends on how you started it), then right-click on it and change the priority to "higher than normal" or "high".

[Tommygun]

Rather try a
ping -t ipaddress

to the closest responding ip, tracert wont give you any longitudinal or averaging data.