95 replies to this topic

[PolyunsaturatedFat]

Telmasa, on 20 April 2015 - 11:28 PM, said:

Hops 11, 12, and 13, all appear to be the same router tossing me around its servers...so it's also adding, what, 30-35 ping? (though ping falls again when it hops to mwomercs.com - not sure how, but that's neat lol)

Hey - I don't work for MWO, but I am a network engineer.

When a packet is sent out, it doesn't decide where it's going next. Rather, the servers that recieve the packet decide if they can send it somewhere closer to it's destination. If they can, they forward it. If they can't, the just drop the packet, letting some other server send it on.

You can think of it as your packet stops at a streetcorner and yells at a passing pedestrian "Hey, how do I get to 1151 Broadway, New York, New York?" Most pedestrians ignore you. However, you get that one dude that says "I think New York is thataway." Keep doing this enough, and your packet eventually gets to it's address.

What's happening here is that rather than one dude answering, your packet has 3 dudes answering. Each packet has 3 legitmate "routes" to get closer to the destination. You are seeing all of these hops as legitimate "next steps" that get closer to the final destination. They aren't actually getting ring-routed, it's more of an artifact from the inherently lossy model of TCP/IP.

This metaphor is, of course, a simplification, but it gives you an idea what's going on.

[Taelon Zero]

Over the last few days my ping has gone up by 100+ on the NA and EU severs. From NZ the NA server is by far the best untill this happened. It used to be 210-240.

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

1 <1 ms <1 ms <1 ms 192.168.1.254
2 5 ms 16 ms 1 ms 122-58-236-1.jetstream.xtra.co.nz [122.58.236.1]
3 * * * Request timed out.
4 13 ms 15 ms 14 ms ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
5 15 ms 15 ms 15 ms ae5-2.akbr7.global-gateway.net.nz [210.55.202.213]
6 39 ms 38 ms 39 ms xe7-0-9.sgbr3.global-gateway.net.nz [202.50.232.182]
7 41 ms 38 ms 39 ms ae2-10.sgbr4.global-gateway.net.nz [202.50.232.246]
8 40 ms 39 ms 39 ms ae-3.a04.sydnau03.au.ra.gin.ntt.net [103.13.80.125]
9 40 ms 39 ms 39 ms ae-3.r05.sydnau01.au.bb.gin.ntt.net [202.68.64.124]
10 152 ms 153 ms 152 ms ae-8.r20.tokyjp05.jp.bb.gin.ntt.net [129.250.3.76]
11 151 ms 163 ms 167 ms ae-3.r30.tokyjp05.jp.bb.gin.ntt.net [129.250.7.70]
12 152 ms 150 ms 164 ms ae-23.r24.tokyjp05.jp.bb.gin.ntt.net [129.250.6.50]
13 199 ms 238 ms 201 ms ae-3.r23.tkokhk01.hk.bb.gin.ntt.net [129.250.3.89]
14 205 ms 207 ms 199 ms ae-8.r00.tkokhk01.hk.bb.gin.ntt.net [129.250.5.83]
15 * 258 ms 254 ms ix-24-0.tcore1.HK2-Hong-Kong.as6453.net [180.87.112.153]
16 329 ms 331 ms 340 ms if-3-2.tcore1.TV2-Tokyo.as6453.net [180.87.112.6]
17 * 371 ms * if-9-2.tcore2.PDI-Palo-Alto.as6453.net [180.87.180.17]
18 * 362 ms * if-2-2.tcore1.PDI-Palo-Alto.as6453.net [66.198.127.1]
19 320 ms 332 ms 326 ms if-1-2.tcore1.NYY-New-York.as6453.net [66.198.127.6]
20 333 ms 336 ms 325 ms if-3-2.thar1.NJY-Newark.as6453.net [66.198.70.21]
21 331 ms 321 ms 332 ms nwk-5-a9.nj.us [192.99.146.48]
22 325 ms 323 ms 332 ms bhs-g2-a9.qc.ca [192.99.146.101]
23 348 ms 358 ms 347 ms 198.27.73.233
24 318 ms 328 ms 327 ms mwomercs.com [192.99.109.192]

Trace complete.

[YakkSlapper]

look up "internet backbone maps" you will then see the MAJOR BACKBONE of the net, now look up your local isp maps, you need to go from you, to your isp, TGHROUGH your isp partners so to speak, to the 'backbone' then reverse process to got to your end destination, in the 'net' theres no direct connection, its all back n fourth through sub vendors to begine with and to end with,
to put it in dummy speak,

or look it this way, you house to your neighbours house same block opposite side(behind you) you get in your car, drive out of your garrage(wich faces the street, then you drive down the street untill you turn onto another street(net backbone/street at end of your block,) drive down that untill you reach the street behind your block from you, then turn onto that small street then drive to your friends garrage, yah SURE its faster to drive chashing through your garrage and across the ally then into the back wall of your friends houses garrage then crash into it, but thats not how we are allowed to drive(not how it works),

so even IF u live a block away from game servers, DOES NOT MEAN you have a direct connection to the game servers, you still gotta drive the back street to the main street to the back streets to your destination,

change house for your computer, chance side street to local internet infrastructure , change main street to main net back bone, yaddah yaddah yaddah, and its all simple as to why theres so many 'hops/out of the way connections

[V O L T R O N]

raceroute to 192.99.109.129 (192.99.109.129), 30 hops max, 38 byte packets
1 107-138-16-3.lightspeed.jcsnms.sbcglobal.net (107.138.16.3) 21.998 ms 21.917 ms 22.370 ms
2 99.183.77.84 (99.183.77.84) 22.055 ms 21.589 ms 56.732 ms
3 12.83.102.13 (12.83.102.13) 24.603 ms 22.670 ms 12.83.102.21 (12.83.102.21) 24.785 ms
4 12.122.157.34 (12.122.157.34) 31.121 ms 34.418 ms 59.582 ms
5 gar26.dlstx.ip.att.net (12.123.16.109) 32.326 ms 31.774 ms 31.691 ms
6 * * *
7 * * ae-21-3621.ear1.Chicago3.Level3.net (4.69.141.158) 79.415 ms
8 * * *
9 bhs-g1-a9.qc.ca (198.27.73.87) 93.256 ms 92.692 ms *
10 * bhs-g5-a9.qc.ca (198.27.73.231) 96.106 ms *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *

[V O L T R O N]

How do you one second sit here playing the game and the very next second have 500 mismatched files and unable to connect?! How is that possible? Steam lolollolololooololololololololololololol

[Gregor Utama]

I contacted my ISP and they responded that they are directly connected with the hosting provider in Los Angeles. From Los Angeles to Canada, PGI's server provider are using their own internal routing which my ISP has no control of. Could PGI's server provider optimise their routing, please? Thank you.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 38 | 38 | 3 | 4 | 6 | 6 |
| 132.147.100.1 - 0 | 38 | 38 | 5 | 9 | 35 | 5 |
| LosAngeles1.vqbn.com - 0 | 38 | 38 | 185 | 186 | 191 | 188 |
| any2ix.coresite.com - 3 | 36 | 35 | 186 | 218 | 396 | 187 |
| nwk-5-a9.nj.us - 0 | 38 | 38 | 249 | 250 | 254 | 252 |
| bhs-g2-a9.qc.ca - 0 | 38 | 38 | 257 | 258 | 261 | 259 |
| bhs-g5-a9.qc.ca - 0 | 38 | 38 | 258 | 259 | 263 | 260 |
| mwomercs.com - 0 | 38 | 38 | 257 | 258 | 263 | 259 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

[LORD ORION]

I've done alot of crap to try and fix my hitreg

Improvements were made using DNS benchmark properly (the full option that takes around 45 minutes, and then rerun the top 50 of those)
https://www.grc.com/dns/benchmark.htm

I found a faster DNS server that has less hops to reach the OVN Hosting that PGI uses.

Speed Guide .net's TCP Optmizer 4.0.3... and seriously RTFM and use the forums to ask about things you don't understand.
http://www.speedguid...t/downloads.php

Hitreg works sort of OK now (75% of what I hit, and sometimes 100% which surprises the crap out of me)
Hitreg goes bad every once in awhile (50-60% dmg of what I hit) and I blame this on PGI's servers needing a reset.... because it eventually starts working sort of again.

What I don't know, and am waiting for support to answer me (for nearly 2 weeks now) is if the OVN routers use ECN or not. (and some other stuff, but the ECN needs answering)

[Bulletsponge0]

1 2 ms 1 ms 4 ms homeportal
2 * 26 ms 20 ms 104-52-112-3.lightspeed.clmboh.sbcglobal.net [104.52.112.3]
3 23 ms 19 ms 22 ms 71.158.32.156
4 23 ms 19 ms 19 ms 71.158.32.140
5 21 ms 22 ms 23 ms 12.83.38.17
6 34 ms 43 ms 29 ms ggr4.cgcil.ip.att.net [12.122.133.33]
7 29 ms 31 ms 28 ms chi-b21-link.telia.net [213.248.87.253]
8 54 ms 58 ms 81 ms nyk-bb2-link.telia.net [80.91.246.19]
9 2359 ms 56 ms * nyk-b2-link.telia.net [62.115.134.108]
10 669 ms 55 ms 56 ms nwk-5-a9.nj.us [192.99.146.38]
11 * 53 ms 52 ms bhs-g2-a9.qc.ca [198.27.73.207]
12 54 ms 52 ms 53 ms bhs-g5-a9.qc.ca [198.27.73.233]
13 894 ms 2445 ms 1051 ms mwomercs.com [192.99.109.192]


What on earth is going on.... that one is from when I'm in the mechlab

1 847 ms 913 ms 1020 ms homeportal
2 77 ms 22 ms 22 ms 104-52-112-3.lightspeed.clmboh.sbcglobal.net [104.52.112.3]
3 319 ms 985 ms 928 ms 71.158.32.156
4 400 ms 1109 ms 986 ms 71.158.32.140
5 360 ms 2312 ms 85 ms 12.83.38.17
6 1745 ms 34 ms 29 ms ggr4.cgcil.ip.att.net [12.122.133.33]
7 30 ms 32 ms 29 ms chi-b21-link.telia.net [213.248.87.253]
8 135 ms 159 ms 59 ms nyk-bb2-link.telia.net [80.91.246.19]
9 63 ms 59 ms 57 ms nyk-b2-link.telia.net [62.115.134.108]
10 56 ms 63 ms * nwk-5-a9.nj.us [192.99.146.38]
11 1007 ms 1006 ms 3200 ms bhs-g2-a9.qc.ca [198.27.73.207]
12 56 ms 53 ms 54 ms bhs-g5-a9.qc.ca [198.27.73.233]
13 458 ms 1034 ms 1007 ms mwomercs.com [192.99.109.192]


that is from in-game

[tangles 253]

weird. im getting abnormally high ping all of a sudden. started out in the arvo with 250 which is AWESOME for me n melbourne aus, i normally get round the 270-300 mark. then later on i got up around the 450 mark.

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

1 <1 ms <1 ms <1 ms dsldevice.gateway [10.0.0.138]
2 * * * Request timed out.
3 19 ms 20 ms 18 ms 144.130.211.210
4 19 ms 20 ms 20 ms bundle-ether12.win-core10.melbourne.telstra.net [203.50.11.111]
5 31 ms 31 ms 33 ms bundle-ether12.ken-core10.sydney.telstra.net [203.50.11.122]
6 31 ms 33 ms 31 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
7 31 ms 31 ms 31 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
8 175 ms 174 ms 175 ms i-0-3-0-5.paix-core01.bx.telstraglobal.net [202.84.144.157]
9 173 ms 173 ms 174 ms i-0-5-0-4.paix02.bi.telstraglobal.net [202.40.149.122]
10 203 ms 173 ms 173 ms xe-5-3-0.paloalto2.pao.seabone.net [195.22.206.129]
11 250 ms 258 ms 258 ms et-10-1-0.miami15.mia.seabone.net [89.221.41.175]
12 251 ms 257 ms 251 ms et-4-3-0.miami15.mia.seabone.net [195.22.199.177]
13 * 436 ms * mia-1-6k.fl.us [178.32.135.208]
14 445 ms 445 ms 446 ms nwk-5-a9.nj.us [198.27.73.201]
15 444 ms 442 ms 444 ms bhs-g2-a9.qc.ca [192.99.146.101]
16 444 ms 443 ms 443 ms bhs-g5-a9.qc.ca [198.27.73.233]
17 441 ms 442 ms 442 ms mwomercs.com [192.99.109.192]

Trace complete.

any ideas?

Thanks for your time

Edited by tangles 253, 19 January 2016 - 11:18 AM.

[Mi Ro Ki]

Same thing for me, even though i'm a week late to the party. I noticed a week ago my ping jumped from 240ms average to 360-400ms consistently since, i thought it may have just been a subcable issue on the mend. So from Sydney Australia being routed through to France/Europe then to MWO ? wtf!

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| telstra.gateway - 0 | 304 | 304 | 0 | 0 | 1 | 0 |
| - 0 | 304 | 304 | 11 | 16 | 107 | 13 |
| - 0 | 304 | 304 | 12 | 12 | 15 | 13 |
|bundle-ether14.ken-core10.sydney.telstra.net - 0 | 304 | 304 | 13 | 13 | 16 | 14 |
|bundle-ether1.pad-gw11.sydney.telstra.net - 0 | 304 | 304 | 13 | 14 | 16 | 13 |
|bundle-ether1.sydp-core04.sydney.reach.com - 0 | 304 | 304 | 12 | 13 | 16 | 14 |
|i-0-1-0-1.tlot-core01.bx.telstraglobal.net - 2 | 292 | 289 | 168 | 170 | 173 | 170 |
|i-0-4-0-6.tnrt-core01.bi.telstraglobal.net - 0 | 303 | 303 | 227 | 229 | 234 | 229 |
|i-0-3-0-2.ulhc-core01.bx.telstraglobal.net - 0 | 304 | 304 | 310 | 312 | 316 | 311 |
| i-0-0-0-4.ulco01.bi.telstraglobal.net - 0 | 304 | 304 | 304 | 306 | 438 | 305 |
| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |
| sbg-g1-a9.fr.eu - 0 | 304 | 304 | 330 | 331 | 334 | 331 |
| sbg-g5-a9.fr.eu - 0 | 304 | 304 | 331 | 331 | 336 | 331 |
| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |
| mwomercs.com - 0 | 304 | 304 | 330 | 330 | 333 | 330 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Edited by Mi Ro Ki, 28 January 2016 - 12:16 AM.

[Kairaku]

Hey Mi Ro Ki I am coming from NZ and have noticed the same issues as you. I also used to sit around the 250ms average, but now are averaging 397 on the NA server. I did a traceroute and these are my results:


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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 12 ms 14 ms 10 ms lo0.internet.ivpn.pe25.telstraclear.net [218.101
.61.124]
4 23 ms 20 ms 22 ms ie2-g-0-0-0.telstraclear.net [203.98.50.2]
5 190 ms 194 ms * ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.
50.251]
6 35 ms 22 ms 23 ms unknown.telstraglobal.net [134.159.174.37]
7 154 ms 305 ms 354 ms i-0-0-4-1.1wlt-core01.bx.telstraglobal.net [202.
84.142.110]
8 432 ms 225 ms 213 ms i-0-4-0-4.tnrt-core01.bi.telstraglobal.net [202.
84.141.130]
9 298 ms 298 ms 300 ms i-0-3-0-2.ulhc-core01.bx.telstraglobal.net [202.
84.143.230]
10 296 ms 289 ms 287 ms i-0-0-0-5.ulco01.bi.telstraglobal.net [202.84.17
8.10]
11 * * * Request timed out.
12 508 ms 486 ms 510 ms sbg-g1-a9.fr.eu [37.187.232.86]
13 308 ms 306 ms 307 ms sbg-g5-a9.fr.eu [37.187.36.153]
14 * * * Request timed out.
15 397 ms 393 ms 394 ms mwomercs.com [192.99.109.192]

Trace complete.

I have done this for a few days now and the pattern is always the same.
Why am I getting routed through Africa and into France? Especially since the only cable from New Zealand is a ring between Auckland, Sydney and Hawaii.
Also Jump 11 and 14 always time out, so I have no idea of the route in these jumps.

[General Solo]

The data is being routed to France rather than across the Pacific.
I had this problem a while back.
Talk to your ISP and hopefully PGI's Network guy can talk to their ISP and get it worked out.

Edited by OZHomerOZ, 14 February 2016 - 12:26 PM.

[puckRfactor]

RustyBolts, on 28 May 2015 - 12:38 PM, said:

@Mike. I would appreciate it. I was working with Alex, but we could not find any answers. My ISP, Cox, has been out here 6 times. They checked all the equipment, changed splitters and filters and ran new cable from the outside wall to the modem/router. They are coming out tomorrow to run new cable from the street to the house. If that does not fix it I am at a loss.

Some symptoms: Whenever I disconnect it is just for a second or two and always go back to the log in screen. TS, RaidCall never drop. In fact what is funny is that in a few cases, VOIP still worked.

I have no issues with BSGO or STO either. All these issues started in early March and up till then, I do not
remember ever getting a DC in the last year.

Did you get this sorted? I had same issue.MWO would disconnect and teamspeak would still be working. Ended up being our dhcp router dropping me every 30 mins or so. I fixed my ip address on my PC network adaptor and problem solved.

[Dimento Graven]

Ok, now I'm getting to 'enjoy' the same level of crap ping.

My ping to the NA server is ~200 (prior to the last couple of weeks it was ~70), and I'm noticing via tracert, all my f'ing traffic is going through the EU!

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 192.168.1.254
2 21 ms 21 ms 21 ms 99-7-64-3.lightspeed.rcsntx.sbcglobal.net [99.7.64.3]
3 * * * Request timed out.
4 25 ms 26 ms 26 ms 12.83.80.225
5 24 ms 27 ms 27 ms gar27.dlstx.ip.att.net [12.123.16.77]
6 24 ms 26 ms 27 ms 192.205.36.94
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 160 ms 192 ms 199 ms be100-110.fra-1-a9.de.eu [37.187.232.46]
11 208 ms 210 ms 206 ms be1-1170.sbg-g1-a9.fr.eu [37.187.232.86]
12 206 ms 211 ms 205 ms vl21.sbg-g1-a75.fr.eu [213.186.32.251]
13 209 ms 204 ms 208 ms sbg-g5-a9.fr.eu [37.187.36.186]
14 215 ms 217 ms 222 ms mad-3-4m.es.eu [91.121.215.215]
15 167 ms 200 ms 204 ms 192.99.109.143

Trace complete.

Edited by Dimento Graven, 15 September 2016 - 05:10 PM.

[Ithilid]

Dimento Graven, on 15 September 2016 - 05:07 PM, said:

Ok, now I'm getting to 'enjoy' the same level of crap ping.

My ping to the NA server is ~200 (prior to the last couple of weeks it was ~70), and I'm noticing via tracert, all my f'ing traffic is going through the EU!

I'm in the same boat... prior to Sept 3 my ping was running in the 70's to 80's range and now has increased to the point that MWO is unplayable

[Dimento Graven]

Ithilid, on 15 September 2016 - 06:00 PM, said:

I'm in the same boat... prior to Sept 3 my ping was running in the 70's to 80's range and now has increased to the point that MWO is unplayable

I submitted a request on my ISP's forum, someone already responded indicating that they are having the same issue with other services hosted through OVH.

I tried contacting OVH, but support@ovh.com isn't a valid address, AND, tee-hee-hee, when I try to register myself on their forums, I get a web error ( HTTP 408/HTTP 409 ) indicating the server is to busy to respond, which of course, doesn't let me register to their site making it IMPOSSIBLE to report the issue to them.

Glad I don't have to use OVH for any of my businesses.

EDIT: Interestingly enough, I found THIS post on their forums:

https://forum.ovh.us...-Peering-Issues

Pretty sure OVH has malf'd something with AT&T.

Edited by Dimento Graven, 15 September 2016 - 06:56 PM.

[Ithilid]

Most of this stuff is over my technical skill.. This is what mine looks like today

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

1 2 ms <1 ms <1 ms homeportal [192.168.1.254]
2 23 ms 23 ms 20 ms 99-35-196-3.lightspeed.okcbok.sbcglobal.net [99.
35.196.3]
3 * * * Request timed out.
4 * * * Request timed out.
5 23 ms 20 ms 23 ms 12.83.42.9
6 28 ms 27 ms 27 ms gar25.dlstx.ip.att.net [12.122.85.233]
7 27 ms 29 ms 27 ms 192.205.36.94
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 155 ms 154 ms 155 ms be100-110.fra-1-a9.de.eu [37.187.232.46]
12 159 ms 156 ms 157 ms be1-1170.sbg-g1-a9.fr.eu [37.187.232.86]
13 163 ms 156 ms 157 ms vl21.sbg-g1-a75.fr.eu [213.186.32.251]
14 158 ms 156 ms 157 ms sbg-g5-a9.fr.eu [37.187.36.186]
15 190 ms 186 ms 186 ms mad-3-4m.es.eu [91.121.215.215]
16 165 ms 163 ms 166 ms 192.99.109.143

Trace complete.

I can completely understand it's not PGI fault. They should understand that if fewer player can play less money is going to be generated and that should be PGI concern.

[Dimento Graven]

Ithilid, on 16 September 2016 - 01:14 PM, said:

Most of this stuff is over my technical skill.. This is what mine looks like today

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

1 2 ms &lt;1 ms &lt;1 ms homeportal [192.168.1.254]
2 23 ms 23 ms 20 ms 99-35-196-3.lightspeed.okcbok.sbcglobal.net [99.
35.196.3]
3 * * * Request timed out.
4 * * * Request timed out.
5 23 ms 20 ms 23 ms 12.83.42.9
6 28 ms 27 ms 27 ms gar25.dlstx.ip.att.net [12.122.85.233]
7 27 ms 29 ms 27 ms 192.205.36.94
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 155 ms 154 ms 155 ms be100-110.fra-1-a9.de.eu [37.187.232.46]
12 159 ms 156 ms 157 ms be1-1170.sbg-g1-a9.fr.eu [37.187.232.86]
13 163 ms 156 ms 157 ms vl21.sbg-g1-a75.fr.eu [213.186.32.251]
14 158 ms 156 ms 157 ms sbg-g5-a9.fr.eu [37.187.36.186]
15 190 ms 186 ms 186 ms mad-3-4m.es.eu [91.121.215.215]
16 165 ms 163 ms 166 ms 192.99.109.143

Trace complete.

I can completely understand it's not PGI fault. They should understand that if fewer player can play less money is going to be generated and that should be PGI concern.

So is your ISP AT&T, as well?

[Ithilid]

Yes, AT&T Uverse... FYI Oklahoma

[Iron Heel]

Not having any issues, per se, just curious.


Tracing route to 192.99.109.143 over a maximum of 30 hops

1 9 ms 9 ms 9 ms homeportal [192.168.xxx.xxx]
2 30 ms 24 ms 25 ms 107-211-144-3.lightspeed.chrlnc.sbcglobal.net [107.211.144.3]
3 32 ms 32 ms 30 ms 99.133.205.104
4 24 ms 25 ms 26 ms 99.133.205.60
5 24 ms 23 ms 24 ms 12.83.102.145
6 30 ms 32 ms 30 ms 12.122.154.134
7 37 ms 31 ms 32 ms 12.122.117.97
8 44 ms 47 ms 46 ms 192.205.33.42
9 42 ms 45 ms 42 ms ash-bb4-link.telia.net [62.115.115.95]
10 48 ms 53 ms 64 ms nyk-bb2-link.telia.net [80.91.245.99]
11 51 ms 48 ms 55 ms nyk-bb4-link.telia.net [62.115.122.31]
12 48 ms 53 ms 47 ms nyk-b2-link.telia.net [62.115.134.108]
13 52 ms 48 ms 56 ms be100-154.nwk-5-a9.nj.us [192.99.146.38]
14 58 ms 66 ms 67 ms be10-1018.bhs-g2-a9.qc.ca [192.99.146.101]
15 66 ms 66 ms 66 ms vl21.bhs-g2-a75.qc.ca [198.27.73.91]
16 60 ms 60 ms 67 ms bhs-g5-a9.qc.ca [178.32.135.196]
17 70 ms 72 ms 72 ms 192.99.109.143

ISP: AT&T Uverse , which identifies as sbcglobal, formerly Southwestern Bell Telephone Company.
Hmm, 9ms to my modem? I've gotta put that thing back in my study and get off the wireless connection.
Anyway, It goes from "out in the sticks" to Charlotte NC, to VA, then NY/NJ and finally Montreal, where it hops around a couple times before arriving at the server.
The only anomaly is that last hop before the MWO servers reports as being in the middle of the Seine river in Paris, France.
I know, weird right?

Edit: As a reference point, my normal pings are:
NA 50-70ms
Europe 120-150ms
Oceanic 230-270ms

Just to be clear, I don't think that last hop is reporting correctly as being in Paris. It is odd that a mainland US player should find themselves routed through Europe on the way to Montreal under normal circumstances.
That being said, after reading through the thread some more I do question if this isn't happening sometimes when my normal 50-70ms ping to NA servers jumps to 120-150ms for a match then returns to normal for the next one.

Edited by Iron Heel, 21 September 2016 - 11:21 AM.