O2 Tracert help

GM@N

GM@N

GM@N

Associate
Joined
7 Nov 2002
Posts
2,096
Location
Normally in Bed Sleeping
I am getting a lot of loss to our TF2 server over the past month here is a few trace routes to the server. Can some please explain what is going on here.

Thanks!

Code: 
C:\tracert 188.165.226.117

Tracing route to ns313163.ovh.net [188.165.226.117]
over a maximum of 30 hops:

  1    27 ms    99 ms    99 ms  O2WirelessBox.lan [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    15 ms     *       15 ms  sw1.tc.lon.ovh.net [195.66.224.220]
  5    98 ms    24 ms     *     vss-3-6k.fr.eu [213.251.130.73]
  6    25 ms    25 ms    25 ms  ns313163.ovh.net [188.165.226.117]

Trace complete.

C:\tracert 188.165.226.117

Tracing route to ns313163.ovh.net [188.165.226.117]
over a maximum of 30 hops:

  1    20 ms    99 ms    99 ms  O2WirelessBox.lan [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4   130 ms    34 ms     *     sw1.tc.lon.ovh.net [195.66.224.220]
  5    28 ms     *      174 ms  vss-3-6k.fr.eu [213.251.130.73]
  6    25 ms    24 ms    24 ms  ns313163.ovh.net [188.165.226.117]

Trace complete.

C:\tracert 188.165.226.117

Tracing route to ns313163.ovh.net [188.165.226.117]
over a maximum of 30 hops:

  1    58 ms    99 ms   100 ms  O2WirelessBox.lan [192.168.1.254]
  2  1411 ms   945 ms  1094 ms  94-195-72-1.zone9.bethere.co.uk [94.195.72.1]
  3     *        *        *     Request timed out.
  4    16 ms     *       16 ms  sw1.tc.lon.ovh.net [195.66.224.220]
  5    26 ms     *       26 ms  vss-3-6k.fr.eu [213.251.130.73]
  6    26 ms     *       25 ms  ns313163.ovh.net [188.165.226.117]

Trace complete.
 
Is the first hop your router? That's an extremely high ping for something on your LAN. It should be <1.

I just ran a ping and tracert and it's fine from here.
 
Last edited:
Yea as said above even if that first hop is WiFi its terrible! I have a KimSufi box @ OVH myself and get sub 20ms ping's. I am with bethere which is hte same network as O2.
 
The o2 routers are speedtouch routers (or something like that) which have always responded to pings slowly, not sure why but 99ms is the norm for them. It also appears the first two hops after that are set up not to reply to pings.

It may be better to use the command: ping -t serveraddress

Let it sent 100 or so packets and see if there is any packet loss or unstable latency.
 
Please try this program:
http://winmtr.sourceforge.net/
It will do end-to-end pings and to every hop along the way, you should be able to pin down which hop is causing the problem quite quickly. :)

-------------------------------------------------------------
I'm on O2 LLU.

Tracing route to ns313163.ovh.net [188.165.226.117]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * 15 ms * sw1.tc.lon.ovh.net [195.66.224.220]
5 19 ms * 34 ms vss-3-6k.fr.eu [213.251.130.73]
6 18 ms 18 ms 18 ms ns313163.ovh.net [188.165.226.117]

Trace complete.
-------------------------------------------------------------------------
Pinging 188.165.226.117 with 32 bytes of data:

Reply from 188.165.226.117: bytes=32 time=18ms TTL=59
Reply from 188.165.226.117: bytes=32 time=18ms TTL=59
Reply from 188.165.226.117: bytes=32 time=18ms TTL=59
Reply from 188.165.226.117: bytes=32 time=18ms TTL=59

I'm getting a LOT of jitter at 195.66.224.220 and 213.251.130.73 (from subsequent ping tests). This makes me think the problem is ovh's choice of peering and equipment at that datacentre.
Wouldn't surprise me if they're located in telecity in France, le cheapo le cheap.
 
Last edited:
If the server is pinging fine as it is there I would suggest that the previous hops are giving pings a lower priority which is why they drop packets and give an unstable latency.
 
You must log in or register to reply here.
Back
Top Bottom