61 replies to this topic

[Kin3ticX]

everyone in teamspeak has been disco'd twice. Maybe its a bad hop?

[Bartholomew bartholomew]

dunno dc'd twice and now can't get back in network timeout

[WVAnonymous]

Around 9:00 PM PDT, I was about the 12th to get blown out. It was interesting to watch the "disconnected" popping up one after another. Until I disconnected of course

[Kendricke]

Two games in a row, full crash (saw a dozen disconnects right before my own client crashed...my full drop team crashed when I did).

[Son of the Flood]

seeing some connectivity issues that seem widespread tonight. Disconnected and lost session at around midnight eastern US time. The disco conveniently happened when I was having a great match. I was en route to at least 5 or 6 kills and some of those might have even been on the other team .

[nuked4ever]

Seeing the same disconnect issues here..better not be some DDoS attack or something because of some grumpy QQ forumwarrior lol

[Prophetic]

Lost 6 people on both sides of our match tonight. Followed by my entire group at once after logging back in 5 mins ago. Both were half way through matches. I also emptied half my UAC/5 ammo into a heavy for very little dmg.

Needless to say we are done for the night. Hopefully just some server hiccups?

[Kendricke]

Kendricke, on 28 September 2013 - 08:13 PM, said:

Two games in a row, full crash (saw a dozen disconnects right before my own client crashed...my full drop team crashed when I did).

Also, both times received Network Timeout errors from client for a few minutes afterwards when i tried to log back in. (Both times within 20 minutes of this post).

[JudgeDeathCZ]

Kendricke, on 28 September 2013 - 08:16 PM, said:

Also, both times received Network Timeout errors from client for a few minutes afterwards when i tried to log back in. (Both times within 20 minutes of this post).

^

[Celtic Warrior]

Same here, got kicked off twice tonight, I lost credit for 5 kills and all other credits. Total waste of time and money!!!!!!

[Dedzone]

Brilliant launch!

[DragonsFire]

Folks, if you're seeing disconnects, try and get a traceroute run from you to the MWO servers. It would be helpful in establishing a pattern of who is being disconnected and what routers that they are traversing to get to said servers.

There are some issues that are beyond PGI's direct control, this might be one of those issues. That being said, if they at least have a battery of information from multiple users to show a common router crossed by them, they can then possibly approach their Service Provider about getting a peering switch.

[Bartholomew bartholomew]

how would you go about running one of those?

[Deathlike]

Strange network outages/disconnects TWICE @ around 12AM EST (I'd get the Network Timeout Error), and one match I had to manually disconnect from in 11:45AM EST (yes, just less than a half hour before this post) because the match wouldn't seem to end (I could not wait for it TBH).

This is not a good sign.

Edited by Deathlike, 29 September 2013 - 08:13 AM.

[Cest7]

75% of my matches had one player disconnecting

[Draxyl Icharu]

Lets go PGI, get on this please. It's just getting worse. We should also expect to see a refund in some Premium Time. Thanks, love you.

[DragonsFire]

Under Windows you just need to bring up the Command Prompt (type cmd in under the Start Menu) and then type tracert 70.42.29.74. The trace will timeout as it gets to the final hop so you can stop it by hitting CTRL-C. Also, your first 2-3 hops won't be terribly important either (unless you have a high ping) so you can remove those before posting as well. For example:


3 16 ms 15 ms 15 ms 66.26.45.181

4 20 ms 22 ms 19 ms ae19.chrlncpop-rtr1.southeast.rr.com [24.93.64.2]

5 31 ms 31 ms 31 ms bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.109.6.82]

6 27 ms 28 ms 28 ms 107.14.19.11

7 32 ms 28 ms 28 ms 64.209.106.17

8 50 ms 47 ms 48 ms te8-1-10G.asr1.YYZ1.gblx.net [67.16.131.186]

9 65 ms 63 ms 63 ms 64.214.150.82

10 66 ms 64 ms 62 ms border1.te7-1-bbnet1.tor001.pnap.net [70.42.24.132]


Hop 9 is the peering router outside of the data center and I believe either it or the handoff to it from Global Crossing (gblx, hop 8) is where the issue is potentially originating.

Alternatively you can use a freeware program such as PingPlotter to track you connection and see if there are any routing changes that happen at the time of disconnect. I unfortunately have not caught one yet but I haven't played much over the weekend. Either way, getting multiple folks with the same type of captures will help to nail down the issue even further so that PGI has more ammo when approaching their SP (service provider) about a potential route/peer flap.

As to the refund, while it sucks it's happening, it's not exactly something that they have the direct or even indirect ability to control from what I've seen, so this wouldn't necessarily fall under a refundable event/outage.

Edited by DragonsFire, 29 September 2013 - 02:21 PM.

[Caboose30]

There is about a 33% disconnect ratio on average. Basically, out of 15 games, mine will freeze on five. I think that's pretty constant among a large number of players.

[Sturmwind]

http://postimg.org/i...b2d1etrk9/full/

Network problems much? I'm european...and I'm assuming the rest that stayed in the game were, too...

[JoolNoret]

Having this issue all weekend. Tracert is timing out on the 2nd hop then proceeds 18 total hops to [70.42.24.132] Seems to be happening mostly at night for me. (Mountain time, US) Played a few matches today and all was well. Got back on about 10 pm mst and I'm losing the session left and right. When it happens I am also unable to login to the forums or the game for a couple minutes.

2 * * *

3 18ms 10ms 13ms mtrco001cr5-GE-1-1-5-U0.int.bresnan.net [69.146.239.181]

4 12ms 13ms 14ms 69.146.239.148

5 13ms 14ms 13ms gdjco001cr5-XE-5-2-0-U0.int.bresnan.net [72.175.110.234]

6 50ms 51ms 48ms seawafh1cr5-XE-4-3-0-U0.int.bresnan.net [72.175.110.40]

7 55ms 50ms 53ms seawafh2tr5-XE-5-2-0-U0.int.bresnan.net [69.145.214.121]

8 54ms 57ms 53ms 12.90.77.21

9 57ms 58ms 58ms cr2.st6wa.ip.att.net [12.123.46.130]

10 54ms 53ms 54ms cr81.st0wa.ip.att.net [12.122.5.197]

11 53ms 53ms 54ms 12.122.82.9

12 63ms 64ms 65ms 192.205.37.62

13 63ms 65ms 63ms if-13-0-0-4.core1.00S-Seattle.as6453.net [64.86.124.13]

14 121ms 131ms 125ms if-5-1-0-0.tcore2.CT8-Chicago.as6453.net [206.82.141.9]

15 105ms 107ms 107ms if-22-2.tcore1.CT8-Chicago.as6453.net [64.86.79.2]

16 121ms 131ms 125ms if-6-1-0.core4.TNK-Toronto.as6453.net [63.243.172.37]

17 123ms 122ms 122ms ix-4-0-3,core4.TNK-Toronto.as6453.net [216.6.49.2]

18 122ms 122ms 128ms border1.te7-1-bbnet1.tor001.pnap.net [70.42.24.132]

Edited by JoolNoret, 29 September 2013 - 09:28 PM.