95 replies to this topic

[Jon Cunningham]

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

Just adding in - not really cause I have a problem, compared to other folks here, just curious about a couple things:

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 9 ms 9 ms 9 ms L100.LSANCA-VFTTP-121.verizon-gni.net [173.58.73.1]
3 15 ms 13 ms 13 ms G0-14-3-2.LSANCA-LCR-22.verizon-gni.net [130.81.131.44]
4 * * * Request timed out.
5 13 ms 37 ms 11 ms 0.ae2.XL4.LAX15.ALTER.NET [140.222.227.21]
6 17 ms 13 ms 15 ms TenGigE0-5-4-0.GW4.LAX15.ALTER.NET [152.63.115.246]
7 16 ms 14 ms 12 ms teliasonera-gw.customer.alter.net [152.179.21.42]
8 27 ms 26 ms 25 ms palo-b1-link.telia.net [80.91.248.191]
9 94 ms 93 ms 102 ms 192.99.146.32
10 * * * Request timed out.
11 87 ms 88 ms 86 ms mtl-1-6k.qc.ca [198.27.73.183]
12 104 ms 93 ms 95 ms bhs-g1-6k.qc.ca [198.27.73.1]
13 123 ms 135 ms 121 ms 198.27.73.231
14 99 ms 96 ms 93 ms mwomercs.com [192.99.109.192]


So, what I've discovered:
Hops 8 & 9, iplocation.net tells me, is the hop from Palo Alto (south of San Francisco) CA, over and up to you boys in Quebec. Not bad for going across the continent, eh? I'm assuming that's expectable. (edit: going back, previous hops possibly are going between Virginia, New York, and Las Vegas first though...this is confusing! I'm guessing it's really just bumping me around the L.A. basin over to San Fran, and the ip info is just a bit mixed up)

My question:
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)
What's the explanation for what's happening there? I'm scratching my head over it...especially cause my ping in-game appears as 121-135 more often than 93-96.

Ping traffic is often not prioritized. 198.27.73.231 is receiving your ping and saying, "I'm busy, I'll respond to this later." On the other hand, traffic that goes through 198.27.73 and on to mwomercs is handled at the normal rate (which is faster), and then our server responds as soon as it gets it.

[Telmasa]

Cool, thanks!

[Looreed]

I have very strange (and very different) results from tracert.

The first run looks pretty good to me. This look like the usual results.

 1	 1 ms	 1 ms	<1 ms  fritz.box [192.168.178.1]
2	24 ms	23 ms	23 ms  217.0.118.192
3	27 ms	27 ms	27 ms  87.186.237.214
4	28 ms	30 ms	27 ms  217.239.52.66
5	29 ms	59 ms	28 ms  fra-1-6k.de.eu [94.23.122.153]
6	32 ms	33 ms	31 ms  sbg-g2-a9.fr.eu [91.121.128.125]
7	31 ms	32 ms	31 ms  37.187.36.155
8	 *		*		*	 Zeit&#252;berschreitung der Anforderung.
9   120 ms   121 ms   121 ms  mwomercs.com [192.99.109.192]

But the next run a few minutes later shows some very different numbers which are very high.

 1	 6 ms	<1 ms	<1 ms  fritz.box [192.168.178.1]
2	24 ms	23 ms	24 ms  217.0.118.192
3  2965 ms	24 ms	28 ms  87.186.237.214
4	29 ms	28 ms	28 ms  217.239.52.66
5	63 ms	30 ms	29 ms  fra-1-6k.de.eu [94.23.122.153]
6	42 ms	41 ms	33 ms  sbg-g2-a9.fr.eu [91.121.128.125]
7	35 ms	32 ms	33 ms  37.187.36.155
8	 *		*		*	 Zeit&#252;berschreitung der Anforderung.
9  2789 ms   120 ms   121 ms  mwomercs.com [192.99.109.192]

Im really confused.

[FatYak]

Could someone please have a look at this, what exactly does it show? Thanks in advance

Edited by FatYak, 06 May 2015 - 01:57 AM.

[Jeffrey Wilder]

Jon Cunningham, on 10 April 2015 - 09:47 AM, said:

Q. What would actually be a problem, then?

A. I'll give some examples from real problems



A1. This is a problem! Why is it taking a user in Ireland 177ms to reach our fibre in France when the average user in London can get there in 20ms?



A2. This is a problem! Why is this user in JAPAN being sent to Milano, Italy.

Let me know if you see issues like this. : )

There's some other types of problems that are a bit more complicated to discuss that I've left off the list here, but these are the common ones.

How will the average user knows what is considered a reasonable PING like the example in A1?

[Modo44]

Jeffrey Wilder, on 06 May 2015 - 05:58 AM, said:

How will the average user knows what is considered a reasonable PING like the example in A1?

Find out your location's typical ping to the MWO servers. It is similar for all players from the same region. It will be the lowest stable ping you get in matches with a ~5% variance.

[dalemming]

Who cares about icmp? In case of udp packet loss is work as designed, for tcp jitter due retransmission is a big point.
This can't be determined by sending some echo requests. Icmp timeout can also just mean an according acl on the device, dropping it.

icmp might be helpful for looking up fragmentation or looking if the destination is at least reachable, beside that it's meaningless in this case. Especially it doesn't mean packets take the same route ten minutes later. (mpls, underlying igp etc.)

You can have 20ms latency and game still lags as hell.

so far this topic is snakeoil.

just my 2cents

[Kossack 7]

Yeah, so maybe clan mechs should be nerfed further because of this, because it must be 'THEIR' fault. ****, everything else is.

[Mike Forst]

FatYak, on 06 May 2015 - 01:19 AM, said:

Could someone please have a look at this, what exactly does it show? Thanks in advance

Sorry for the late reply. I've taken over looking at these problems now. I'll be doing some research into your traceroute and will start a PM thread with you when I have more info for you.

[Mike Forst]

FatYak, on 06 May 2015 - 01:19 AM, said:

Could someone please have a look at this, what exactly does it show? Thanks in advance

I've reviewed this trace and it looks like your route to our servers are about as good as they're going to get. The big latency jump hits when your connection crosses the Pacific Ocean which still looks standard.

I'm afraid your ping times are as good as they're going to get based on your current location.

[RustyBolts]

Here is my tracert and I get a lot of DC's.Would love to play game without a DC.


over a maximum of 30 hops:
1 205ms 11ms 13ms 10.5.0.1
2 16ms 12ms 12ms ip68-100-3-220.dc.dc.cox.net [68.100.3.229]
3 13ms 17ms 13ms ip68-100-3-109.dc.dc.cox.net [68.100.3.109]
4 18ms 22ms 17ms nyrkbprj02-ae3.0.rd.ny.cox.net [68.1.5.161]
5 17ms 17ms 14ms 198.27.73.216
6 * * * Request timed out.
7 29ms 21ms 17ms 192.99.146.94
8 77ms 75ms 75ms 192.99.146.84
9 39ms 40ms 38ms 198.27.73.231
10 34ms 28ms 28ms mwomercs.com [192.99.109.192]
Trace complete.

I also got this when I was running a continuous ping to google.
Reply from 8.8.8.8: bytes=32 time=23ms TTL=45
Reply from 8.8.8.8: bytes=32 time=18ms TTL=45
Reply from 8.8.8.8: bytes=32 time=20ms TTL=45
Reply from 8.8.8.8: bytes=32 time=29ms TTL=45
Reply from 8.8.8.8: bytes=32 time=27ms TTL=45
Reply from 8.8.8.8: bytes=32 time=19ms TTL=45
Ping: transmit failed. general failure.
Ping: transmit failed. general failure.
Reply from 8.8.8.8: bytes=32 time=29ms TTL=45
Reply from 8.8.8.8: bytes=32 time=21ms TTL=45
Reply from 8.8.8.8: bytes=32 time=20ms TTL=45
Request timed out.
Reply from 8.8.8.8: bytes=32 time=19ms TTL=45
Reply from 8.8.8.8: bytes=32 time=20ms TTL=45
Reply from 8.8.8.8: bytes=32 time=19ms TTL=45

[H A S T A]

OVH hosting problem tonight.. 198.27.73.233

ping is really too high im in montreal, and i normally have a ping between 8ms and 12ms, and it's 67-70ms jumping to 120ms in game right now and worse.

[Mike Forst]

RustyBolts, on 27 May 2015 - 05:28 PM, said:

Here is my tracert and I get a lot of DC's.Would love to play game without a DC.


over a maximum of 30 hops:
1 205ms 11ms 13ms 10.5.0.1
2 16ms 12ms 12ms ip68-100-3-220.dc.dc.cox.net [68.100.3.229]
3 13ms 17ms 13ms ip68-100-3-109.dc.dc.cox.net [68.100.3.109]
4 18ms 22ms 17ms nyrkbprj02-ae3.0.rd.ny.cox.net [68.1.5.161]
5 17ms 17ms 14ms 198.27.73.216
6 * * * Request timed out.
7 29ms 21ms 17ms 192.99.146.94
8 77ms 75ms 75ms 192.99.146.84
9 39ms 40ms 38ms 198.27.73.231
10 34ms 28ms 28ms mwomercs.com [192.99.109.192]
Trace complete.

I also got this when I was running a continuous ping to google.
Reply from 8.8.8.8: bytes=32 time=23ms TTL=45
Reply from 8.8.8.8: bytes=32 time=18ms TTL=45
Reply from 8.8.8.8: bytes=32 time=20ms TTL=45
Reply from 8.8.8.8: bytes=32 time=29ms TTL=45
Reply from 8.8.8.8: bytes=32 time=27ms TTL=45
Reply from 8.8.8.8: bytes=32 time=19ms TTL=45
Ping: transmit failed. general failure.
Ping: transmit failed. general failure.
Reply from 8.8.8.8: bytes=32 time=29ms TTL=45
Reply from 8.8.8.8: bytes=32 time=21ms TTL=45
Reply from 8.8.8.8: bytes=32 time=20ms TTL=45
Request timed out.
Reply from 8.8.8.8: bytes=32 time=19ms TTL=45
Reply from 8.8.8.8: bytes=32 time=20ms TTL=45
Reply from 8.8.8.8: bytes=32 time=19ms TTL=45

Looking at your general pings to Google DNS leads me to believe that there is something wrong either on your ISP end or even possibly in your home network. If you'd like I can see if I can help dig a further deeper in personal messages.

HastaLaVistaMec, on 27 May 2015 - 07:14 PM, said:

OVH hosting problem tonight.. 198.27.73.233 ping is really too high im in montreal, and i normally have a ping between 8ms and 12ms, and it's 67-70ms jumping to 120ms in game right now and worse.

Yeah there was a serious fibre cut overnight that caused a lot of havoc. It has been fixed now and everything appears to be back to normal.

[Vlad Striker]

What packet size do you recomment for ping testing? How can I watch ingame packet loss ratio?

[RustyBolts]

@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.

[Mike Forst]

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.

It's the "general failure" results in your ping to Google DNS that are most concerning to me. Those are not normal at all and seem to indicate some other problem with the network connection on your computer. Please open a personal message thread with me and I will be happy to see if I can help you diagnose the issue.

[anfadern]

I'm having problems to connect to the MWO servers.
Playing out of Europe and the situation has deteriorated to a point where it's not posible to connect at all.
I have a wired 20MB dsl connection and wired ethernet.
Any ides what to do to help the situation?

Spårar väg till mwomercs.com [192.99.109.192]
över högst 30 hopp:

1 <10 ms <10 ms <10 ms dsldevice.lan [192.168.1.1]
2 17 ms 17 ms 16 ms gw3-no54.tbcn.telia.com [81.232.2.1]
3 16 ms 16 ms 16 ms s-b5-link.telia.net [213.155.134.123]
4 16 ms 16 ms 16 ms s-bb3-link.telia.net [62.115.141.202]
5 55 ms 39 ms 39 ms ffm-bb1-link.telia.net [62.115.143.128]
6 38 ms 38 ms 40 ms ffm-b11-link.telia.net [80.91.246.39]
7 * 49 ms 48 ms fra-1-6k.de.eu [213.186.32.221]
8 1284 ms 1232 ms * sbg-g1-a9.fr.eu [37.187.232.86]
9 48 ms 48 ms 48 ms 37.187.36.153
10 * * * Begäran gjorde timeout.
11 * * * Begäran gjorde timeout.
12 129 ms 128 ms 129 ms mwomercs.com [192.99.109.192]

Spårning utförd.

tracert 192.99.109.192
Spårar väg till mwomercs.com [192.99.109.192]
över högst 30 hopp:

1 <10 ms <10 ms <10 ms dsldevice.lan [192.168.1.1]
2 16 ms 16 ms 15 ms gw3-no54.tbcn.telia.com [81.232.2.1]
3 16 ms 16 ms 16 ms s-b5-link.telia.net [213.155.134.123]
4 21 ms 16 ms 16 ms s-bb3-link.telia.net [62.115.141.202]
5 39 ms 39 ms 39 ms ffm-bb1-link.telia.net [62.115.143.128]
6 42 ms 37 ms 41 ms ffm-b11-link.telia.net [80.91.246.39]
7 48 ms 48 ms 48 ms fra-1-6k.de.eu [213.186.32.221]
8 * 1239 ms * sbg-g1-a9.fr.eu [37.187.232.86]
9 49 ms 49 ms 48 ms 37.187.36.153
10 * * * Begäran gjorde timeout.
11 * * * Begäran gjorde timeout.
12 129 ms 129 ms * mwomercs.com [192.99.109.192]
13 129 ms * * mwomercs.com [192.99.109.192]
14 * 129 ms * mwomercs.com [192.99.109.192]
15 128 ms 128 ms 128 ms mwomercs.com [192.99.109.192]

Spårning utförd.

Edited by anfadern, 10 July 2015 - 12:35 PM.

[Bulletsponge0]

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

1 1 ms 1 ms 1 ms homeportal [192.168.1.254]
2 23 ms 25 ms 23 ms 104-52-112-3.lightspeed.clmboh.sbcglobal.net [10
4.52.112.3]
3 21 ms 19 ms 25 ms 71.158.32.156
4 19 ms 22 ms 27 ms 12.83.38.21
5 34 ms 101 ms 40 ms ggr4.cgcil.ip.att.net [12.122.133.33]
6 29 ms 29 ms 29 ms chi-b21-link.telia.net [213.248.87.253]
7 48 ms 54 ms 46 ms nyk-bb2-link.telia.net [62.115.137.58]
8 59 ms 53 ms 91 ms nyk-b2-link.telia.net [213.155.130.30]
9 75 ms 78 ms 77 ms nwk-1-6k.nj.us [178.32.135.212]
10 83 ms 166 ms 78 ms bhs-g1-a9.qc.ca [198.27.73.205]
11 77 ms 97 ms 91 ms 198.27.73.231
12 84 ms 86 ms 88 ms mwomercs.com [192.99.109.192]

Trace complete.


Why is it routing me from central ohio, through kansas, then to germany, switzerland, france, and new jersey before getting to montreal?

Its making the game absolutely unplayable, not because of the ping, but because it takes my hit reg down to zero....none of my shots register damage on enemy mechs

Edited by Bulletsponge0, 21 July 2015 - 03:24 PM.

[Bulletsponge0]

Bulletsponge0, on 21 July 2015 - 02:54 PM, said:

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

1 1 ms 1 ms 1 ms homeportal [192.168.1.254]
2 23 ms 25 ms 23 ms 104-52-112-3.lightspeed.clmboh.sbcglobal.net [10
4.52.112.3]
3 21 ms 19 ms 25 ms 71.158.32.156
4 19 ms 22 ms 27 ms 12.83.38.21
5 34 ms 101 ms 40 ms ggr4.cgcil.ip.att.net [12.122.133.33]
6 29 ms 29 ms 29 ms chi-b21-link.telia.net [213.248.87.253]
7 48 ms 54 ms 46 ms nyk-bb2-link.telia.net [62.115.137.58]
8 59 ms 53 ms 91 ms nyk-b2-link.telia.net [213.155.130.30]
9 75 ms 78 ms 77 ms nwk-1-6k.nj.us [178.32.135.212]
10 83 ms 166 ms 78 ms bhs-g1-a9.qc.ca [198.27.73.205]
11 77 ms 97 ms 91 ms 198.27.73.231
12 84 ms 86 ms 88 ms mwomercs.com [192.99.109.192]

Trace complete.


Why is it routing me from central ohio, through kansas, then to germany, switzerland, france, and new jersey before getting to montreal?

Its making the game absolutely unplayable, not because of the ping, but because it takes my hit reg down to zero....none of my shots register damage on enemy mechs

Sent a ticket to support about this on the 21st. Still haven't heard anything back. Anyone have any ideas???

[Aceramic]

Based on a combination of some geolocation, the hostnames of the hops in question, checking Telia's own network map, and some traceroutes of my own, my conclusion is that the geolocation is incorrect.

Your route appears to go from Columbus, Ohio (I'm assuming that's where you are located, unless your ISP is either incredible, or lying) > Wichita, Kansas > Chicago, Illinois > New York > New Jersey > Montreal, Canada. (Not sure exactly where in New York/New Jersey those hops are). There most likely isn't a direct route available to your ISP from Ohio to Illinois, so Kansas is probably the best route available.

I'm cheating a little bit and doing this from work, so I've got a much better route, but... My route to the last hop in Telia's network on your traceroute goes directly from Los Angeles to Telia. There is no cable direct from LA to anywhere near Germany, Switzerland or France that I can find, so I can only assume it takes the link from LA to New York (given that Telia does have a direct link between those two locations). The route to the hop after Telia goes from LA to Chicago (on Level 3's network), and then times out, but it's a reasonable guess to make that it's in New Jersey, not Europe.