How is it possible to have a lower ping to a Euro Server than a North American one?

Well I am here until 8pm cst, but will be back in at 930am tomorrow. So if they don't catch me tonight then they can get me in the morning, hopefully they can drop me some contact info if they miss me.

@RobertMinneman

I have received email from OVH and I have replied with the information we show. So now we wait.

@RobertMinneman

we have been playing ping pong with who is fix the problem. OVH had eventually put their AT&T contact on an email, and they were able to back up our original findings. So hopefully they take another look at their stuff again (stuff is very technical term, lol.. actually I don't know what all is propreitary and what is not, i do not want to accidentally put out some stuff I shouldnt). I am the type of person that if the trouble was on AT&T then I wouldn't hesitate to admit it, with that being said, our side appears to be in order. 

Its fixed now.

Ping is 40.

yes it is, i just got the email from them and ran my own trace route.

Thanks for your help.

It's better for me, but I'm certainly not getting the responsiveness that Ethan has reported to me.

While playing I was still seeing pings in the 100's.  DEFINITELY better, but not where you'd think it would be on a "high speed" network.

Here's my latest tracert:

C:\Users\Robert>tracert mwomercs.com

Tracing route to mwomercs.com [192.99.109.143]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dsldevice.attlocal.net [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    23 ms    22 ms    23 ms  12.83.80.225
  5    24 ms    27 ms    26 ms  gar26.dlstx.ip.att.net [12.123.16.109]
  6     *        *     1441 ms  4.68.62.229
  7     *        *        *     Request timed out.
  8    72 ms    69 ms    65 ms  be100-104.nwk-1-a9.nj.us [192.99.146.253]
  9   169 ms   162 ms   164 ms  be10-1037.bhs-g1-a9.qc.ca [192.99.146.99]
 10    85 ms    82 ms    80 ms  vl21.bhs-g1-a75.qc.ca [198.27.73.63]
 11    81 ms    81 ms    80 ms  bhs-g5-a9.qc.ca [178.32.135.194]
 12    73 ms    74 ms    74 ms  192.99.109.143

Trace complete.

As you can see hops 2 and 3 aren't responding to ICMP.  So, ATTDSLCare, show this to the other techs you were working with and let them know that even "if" all AT&T routers are in fact setup to respond to ICMP, there could be problems where they cant.

Obviously there's problems at hops 2&3 that are causing significant ICMP packet loss, to the point that to standard tracert, they're coming up as non-responsive.

Hop 6, shows us that L3 needs love too, that's a painful amount of latency and packet loss there.

And at hop 9, we can see that even BHS has some issues, but at least it's "healthy" enough to provide a consistent response.

Using WinMTR to measure the route over a period of time, here's what we see: 

WinMTR Statistics

If we could figure out what's keeping me from a 50 ping, I'd love it.

This is definitely an improvement and my gameplay over all reflected it (in my personal headshot challenge I'm only 5 away from completing 600, and some lucky victim winning a 'mech pack).

C:\Users\xxx>tracert mwomercs.com

Tracing route to mwomercs.com [192.99.109.143]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.254]
2 10 ms 7 ms 9 ms 172-13-0-1.lightspeed.mssnks.sbcglobal.net [172.
13.0.1]
3 3 ms 3 ms 3 ms 71.150.19.34
4 4 ms 3 ms 3 ms 71.150.32.188
5 4 ms 7 ms 7 ms 12.83.42.157
6 13 ms 15 ms 15 ms gar26.dlstx.ip.att.net [12.123.16.85]
7 * * * Request timed out.
8 * * * Request timed out.
9 40 ms 40 ms 40 ms be100-155.nwk-5-a9.nj.us [198.27.73.29]
10 48 ms 48 ms 48 ms be10-1018.bhs-g2-a9.qc.ca [192.99.146.101]
11 48 ms 48 ms 48 ms vl21.bhs-g2-a75.qc.ca [198.27.73.91]
12 49 ms 48 ms 49 ms bhs-g5-a9.qc.ca [178.32.135.196]
13 47 ms 47 ms 48 ms 192.99.109.143

Trace complete.