Zone Crashing

[Sostua]

avoid zoning for now, seems to cause crashes and major problems reconnecting. ranging from unknown errors to out of date spell files etc.




Keggerlan

[Rickson]

It is happening to me too. I froze while zoning and now I cannot log back in. I am getting to the character selection screen and when I try to login it just tells me that the server is not responding and then that I am disconnected.

Hopefully it gets resolved soon!

[12point]

oh no, I caught whatever they've got :(

[Siggard]

getting it aswell

[wiseguy3k]

i agree and i approve

[Gumbo]

I had it last week and once last night.

[Pinolian]

I made a post about this too, called it feels like I am on dial up in 1999. This is a real issue. I also realize this game is free and I should be grateful. I am that and much more. but I really cant play it if I am fighting staying logged in every time I zone.

[Swish]

Is this a geographical thing? You guys on the same ISP?

Connecting fine in the UK, and I don't know anyone this side of the pond who's had any issues (yet).

[Robbintha Hood]

I was getting similar results while on vacation in the Outer Banks of NC. I thought it was the wi-fi (and very well may have been).

[Deliverator]

I had some issues last night logging in but not getting kicked while zoning. It was during bum fights so that could've been part of it.

[Swish]

I had some issues last night logging in but not getting kicked while zoning. It was during bum fights so that could've been part of it.

EC was certainly packed - think there was a count of 250 at one point.

[12point]

yeah my connection issues are gone today. I was having problems with server select, so don't see how bumfights had anything to do with it. Unless so many were getting kicked they were clogging log in server?

Ill just blame Comcast. I will call them and yell

[mystang89]

I haven't had problems with zone crashing, server select or any type of crashing at all, (knock on wood,) but I do know that yesterday during the bum fights I was very close to crashing a couple of times. That little meter int he top left corner was going crazy for a while.

[Crawdad]

http://www.project1999.com/forums/showthread.php?t=197923

People have been having this problem since the last patch, but something has made it flare up the last week or so. I've been able to connect a little better since yesterday, but I still crash an inordinate amount of time while zoning, and sometimes can't get to server/character select screens.

[Tahlvin]

Networking issues are definitely annoying. I haven't noticed any problems, however. One thing you might try (especially if you have DSL) is making sure your MTU setting is correct both on your device and router, otherwise it can cause fragmentation which might be leading to some of the connection issues you are experiencing.

This article has a good description of how to determine if your setting is correct: http://www.tp-link.us/FAQ-190.html

[Pinolian]

This is definitely something that resides with P99 alone. I have no issues with other games, ruling out configuration problems. I have 130 down and 25 up. Bandwidth is not an issue either.
My ISP is Comcast.

[Tahlvin]

It could still be configuration problems on your end, depending on how the servers networking layer is integrated. There are server solutions, but often you can fix some issues by tweaking your settings over waiting for a patch that may never come.

[Rickson]

I did have this issue a while back on a different emulator of a different game. I resolved it by using a VPN that changed my location from Portland to another city. I might try that again. Apparently it had something to do with my ISP. It's just weird because it started yesterday but no problems before.

[picklefixer]

Just happened to me for the first time. Tried to zone into Kedge and i stared at the screen for about 5 min's then had to shut down EQ.

I tried to log in about 10 min's later and there are no servers at the select screen. =/

<Insert SweetAss Sig Here>
Mrtwig

[tarkhis]

Happening to me. I can get on other eqemu servers but not into P1999. Was having issues with forums before too where it kept telling me website wasn't responding or was incorrect. I'm on east coast USA so don't know if its a regional issue

[Wisteso]

If you are suddenly having major issues with zoning and logging in (out of date spells, weird errors, crashing) AND your setup hasn't changed at all then you are dealing with packet loss.

It has nothing to do with the last patch. The best thing that you guys can do is provide a copy of your traceroute to 66.55.145.2 and we can hopefully see a common network node that you guys all have in common. That node is probably damaged or had its configuration changed in the last day.

I had this issue for a solid week recently, and spent a lot of time figuring out who/what/where/when/why of it all. It took a while, but the issue was repaired.

It will look something like...
C:\Users\YourNameHere>tracert 66.55.145.2
Tracing route to 66.55.145.2 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms lolwat [192.168.1.1]
2 31 ms 28 ms 26 ms cpe-65-31-128-1.wi.res.rr.com [65.31.128.1]
3 11 ms 12 ms 12 ms tge7-1.brfdwifb02h.midwest.rr.com [24.164.233.69]
4 14 ms 15 ms 19 ms tge1-6-0-9.gnfdwibb01r.midwest.rr.com [65.29.44.54]
5 19 ms 19 ms 19 ms bu-ether16.chcgildt87w-bcr00.tbone.rr.com [66.109.6.204]
6 16 ms 16 ms 17 ms 0.ae1.pr1.chi10.tbone.rr.com [107.14.17.194]
(snipped short for brevity)

[tarkhis]

Here is what I get. I cut it short because it just kept giving me timed out error for 30 hops:
tracing route to 66.55.145.2 over a maximum of 30 hops

1 <1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 7 ms 15 ms gateway-p1-399-senjblocal1.spo.ptd.net [24.229.33.97]
4 9 ms 9 ms 9 ms xe-1-0-3-854.ar1.nyc3.us.as4436.gtt.net [69.31.95.125]
5 16 ms 11 ms 12 ms as20473.ae7.ar1.nyc3.us.as4436.gtt.net [69.31.34.62]
6 11 ms 110 ms 10 ms ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61.80.218]
7 * 10 ms 10 ms 108.61.244.50
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 *

[Tahlvin]

If some of you are willing to try that have this issue and are tech savvy, I would still recommend trying to optimize your MTU: http://www.tp-link.us/FAQ-190.html

If the packets fragment, it's definitely a higher chance for packet loss. Some of the most common DoS attacks also work by heavily fragmenting packets so sometimes fragmented packets will be flat out dropped at a node when trying to fight a DoS attack so by not fragmenting your packets it allows you to get through.

This actually happened with Destiny not too long ago. People were lowering their MTU to connect when they were being attacked and the reason that worked is largely the same reason as mentioned above.

The issue mostly occurs with DSL, which has a maximum MTU of 1492 and a lot of routers/devices are still set at 1500 because they don't know what type the underlying connection is.

Worst case, it doesn't fix your issues on P99, but will actually speed up your connection quite a bit if your MTU is indeed set wrong.

[Swish]

What's funny about a tracert is I get time outs but I don't have any problems with connecting :/

[Wisteso]

Tarkhis, yeah cutting the tail off is fine. Windows tracert will keep trying for a max of 30 hops, even if the route is much shorter than that. WinMTR does a better job but I dont expect people to have it installed.

Swish, yeah that's because network nodes often ignore or de-prioritize meta traffic. Its actually a bad idea to use packet loss of meta traffic for determining where issues occur, but people (even tech support) still does it all the time.

Tahlvin, optimizing the MTU will not help. EQ uses datagrams of size 512 (576 including the header) which is guaranteed to not fragment. (http://stackoverflow.com/questions/1098897/what-is-the-largest-safe-udp-packet-size-on-the-internet) It also wouldn't suddenly start acting up for big groups of people all of a sudden.

[Jayneweigh]

I'm having the issue as well now (I was fine yesterday), either I can't get logged in (disconnected) or when I finally got in once I was fine until I zoned and never finished zoning, had to reboot the computer. Now can't get back in, says server issue then disconnects.

[Wisteso]

Just keep trying. Its a packet loss issue so eventually you'll probably get lucky.

Rebooting wont help you.

[GinnasP99]

Getting this too

[Wisteso]

Guys, "me too" posts aren't helpful. Its not an issue with P99. Please post a traceroute.

http://kb.intermedia.net/article/682 (how-to guide)

[h4tch]

So this does appear to be a routing issue. I tried it with normal internet, and a vpn. I was able to login when using the vpn. This was all working normally for me just a few hours ago. Is 66.55.145.2 the actual ip address of the server? I get timeouts even over the vpn that I can login with. First trace is my normal internet, and second is a vpn.

C:\Users\Winterfell>tracert 66.55.145.2

Tracing route to 66.55.145.2 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 23 ms 14 ms 15 ms 96.120.48.193
3 22 ms 14 ms 14 ms te-0-2-0-5-sur01.crosstown.mn.minn.comcast.net [68.85.164.1]
4 18 ms 14 ms 12 ms te-0-5-0-0-sur02.crosstown.mn.minn.comcast.net [69.139.219.8
5 18 ms 17 ms 31 ms te-0-6-0-0-ar01.roseville.mn.minn.comcast.net [68.87.174.217
6 25 ms 27 ms 27 ms he-5-3-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.166.2
7 28 ms 27 ms 28 ms c-eth-0-2-0-pe05.350ecermak.il.ibone.comcast.net [68.86.86.3
8 33 ms 29 ms 28 ms ae12.chi11.ip4.gtt.net [199.229.229.249]
9 49 ms 48 ms 46 ms et-8-1-0.nyc38.ip4.gtt.net [89.149.180.206]
10 48 ms 50 ms 56 ms ae0-150.cr2.nyc3.ip4.gtt.net [216.221.158.234]
11 84 ms * 94 ms as20473.ae7.ar2.nyc3.us.as4436.gtt.net [69.31.34.78]
12 * * * Request timed out.
13 * * * Request timed out.
14 ^C
C:\Users\Winterfell>tracert 66.55.145.2

Tracing route to 66.55.145.2 over a maximum of 30 hops

1 110 ms 116 ms 110 ms 10.9.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 119 ms 118 ms 119 ms xe-5-0-2-0.lon-001-score-1-re0.interoute.net [194.150.37.81]
5 181 ms 184 ms * ae0-0.lon-001-score-2-re0.interoute.net [84.233.218.190]
6 199 ms 184 ms 185 ms ae1-0.nyc-002-score-1-re0.interoute.net [212.23.43.169]
7 181 ms 178 ms 183 ms ae0-0.nyc-002-score-2-re1.interoute.net [212.23.43.158]
8 184 ms 192 ms 185 ms nyiix.gi3-6.cr1.nyc1.choopa.net [198.32.160.157]
9 183 ms 190 ms 184 ms 108.61.244.50
10 * * * Request timed out.
11 * * * Request timed out.

P.S. If anyone wants me to do additional testing just let me know. I'm a network engineer though I'm a managed services guy, so I don't deal with core, or cdn routers ever.

[Wisteso]

Yep, h4tch. Thats exactly how I got around the issue when it was happening for me (till it was fixed). I used NordVPN and found a route that went around the XO Communications till it was fixed. Even with the VPN, you'll still probably have a little packet loss (its almost always there in minor amounts). Timeouts with traceroute/ping are totally normal (even for a healthy connection)

And yes 66.55.145.2 is basically the IP of the server (its technicallya shared IP for several servers, but.. yes essentially)

Both "bad" traceroutes that have been posted so far have been going through gtt.net while your "good" route does not. My guess is that gtt.net is the issue but we'll need more data to be more sure... Further, my connection does not route through gtt.net and I have consequently had no issues.

[Rickson]

I can confirm that using a VPN is working for me now as well. I posted about this earlier and now I have tested zoning and logging in and out and have had no issues. As soon as I disconnect the VPN, I get right back to the same issue.

Hopefully we do not all get flagged for having the same IP if we are using the same VPN. I am not sure if there is a way around that, though.

[evilkorn]

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.11.1 - 0 | 120 | 120 | 0 | 0 | 0 | 0 |
| cut - 0 | 120 | 120 | 8 | 11 | 28 | 8 |
| 162.151.114.249 - 0 | 120 | 120 | 8 | 13 | 71 | 30 |
|xe-11-0-0-0-sur02.delraywest.fl.pompano.comcast.net - 4 | 104 | 100 | 7 | 11 | 27 | 8 |
|xe-3-1-10-0-ar02.stuart.fl.pompano.comcast.net - 9 | 87 | 80 | 14 | 23 | 32 | 29 |
|he-0-9-0-0-ar01.northdade.fl.pompano.comcast.net - 4 | 104 | 100 | 0 | 19 | 36 | 19 |
|be-20214-cr01.miami.fl.ibone.comcast.net - 7 | 96 | 90 | 0 | 20 | 40 | 21 |
| 68.86.84.190 - 3 | 108 | 105 | 0 | 20 | 50 | 21 |
| 66.208.233.18 - 7 | 96 | 90 | 0 | 19 | 35 | 17 |
| et-8-3-0.nyc38.ip4.gtt.net - 58 | 35 | 15 | 0 | 52 | 56 | 51 |
| ae0-150.cr2.nyc3.ip4.gtt.net - 82 | 27 | 5 | 0 | 51 | 52 | 51 |
| No response from host - 100 | 23 | 0 | 0 | 0 | 0 | 0 |
| snip
|________________________________________________| ______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

[h4tch]

FYI: I did some mtu testing, and setting my mtu to 1490 allowed me to login. I'm still at work, so I can't mess with it much more. I did set my mtu back to 1500, and I wasn't able to login.

Anyone still have issues, if you try setting your mtu to 1480(was 1490) what happens?

[h4tch]

Yep, h4tch. Thats exactly how I got around the issue when it was happening for me (till it was fixed). I used NordVPN and found a route that went around the XO Communications till it was fixed. Even with the VPN, you'll still probably have a little packet loss (its almost always there in minor amounts). Timeouts with traceroute/ping are totally normal (even for a healthy connection)

And yes 66.55.145.2 is basically the IP of the server (its technicallya shared IP for several servers, but.. yes essentially)

Both "bad" traceroutes that have been posted so far have been going through gtt.net while your "good" route does not. My guess is that gtt.net is the issue but we'll need more data to be more sure... Further, my connection does not route through gtt.net and I have consequently had no issues.

That makes sense, and gtt looks like maybe a cdn, or cloud service of some type. I think maybe they are messing with the mtu as well. It worked for me on 1472, but now it's 1462. So I'll edit my other post to say 1480 should work.

Here is what I see when I run a ping test.

C:\Users\Winterfell>ping 66.55.145.2 -f -l 1463

Pinging 66.55.145.2 with 1463 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Ping statistics for 66.55.145.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Winterfell>ping 66.55.145.2 -f -l 1462

Pinging 66.55.145.2 with 1462 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 66.55.145.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

[Wisteso]

That's another person (evilkorn) with the issue that's routing through GTT.

If we get enough information, should be possible to call GTT and let them know one of their nodes is having issues. (thats what I did with XO.net)

The MTU thing... I highly doubt its going to fix your issue. EQ does not send datagrams that are at risk to fragmentation. 512/576 is the largest packet the EQ client will send. Changing your MTU settings has no effect on how GTT handles their traffic.

That makes sense, and gtt looks like maybe a cdn, or cloud service of some type.

GTT is a "Tier1" network (https://en.wikipedia.org/wiki/Global_Telecom_%26_Technology). ISPs have peering agreements with networks and other ISPs to help them route traffic. GTT is a major network that many ISPs have a peering partnership with.

[Wisteso]

I'm looking at the logs so far and everyone who's posted a traceroute is being routed through NTT's "NYC3" network nodes. It doesn't appear to be a single specific node, since each route is slightly different but they are all still going through the NYC3 cluster.

In other words, its probably not faulty hardware. More likely that they either implemented some bad configuration changes, OR they're way above capacity. Or both.

[bspa0700]

Happened to me last weekend, and again tonight.

>> tracert 66.55.145.2

Tracing route to 66.55.145.2 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.1
2 15 ms 8 ms 7 ms 98.245.120.1
3 7 ms 7 ms 7 ms xe-9-1-1-0-sur03.boulder.co.denver.comcast.net [
68.86.105.21]
4 12 ms 8 ms 7 ms ae-10-0-sur02.boulder.co.denver.comcast.net [162
.151.51.34]
5 38 ms 9 ms 16 ms ae-29-0-ar01.aurora.co.denver.comcast.net [162.1
51.51.13]
6 12 ms 10 ms 12 ms he-0-5-0-7-cr02.denver.co.ibone.comcast.net [68.
86.93.149]
7 26 ms 27 ms 27 ms be-11317-cr01.dallas.tx.ibone.comcast.net [68.86
.84.229]
8 24 ms 23 ms 24 ms he-0-10-0-1-pe03.1950stemmons.tx.ibone.comcast.n
et [68.86.86.114]
9 23 ms 23 ms 23 ms 75.149.231.30
10 90 ms 63 ms 63 ms xe-10-1-6.nyc38.ip4.gtt.net [89.149.128.129]
11 61 ms 61 ms 63 ms ae0-150.cr2.nyc3.ip4.gtt.net [216.221.158.234]
12 91 ms 91 ms 98 ms as20473.ae7.ar2.nyc3.us.as4436.gtt.net [69.31.34
.78]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.

[Kevris]

3 22 ms 18 ms 21 ms tge7-6.pldscabx01h.socal.rr.com [76.166.19.41]
4 46 ms 45 ms 44 ms agg15.pldscabx01r.socal.rr.com [72.129.38.14]
5 20 ms 20 ms 19 ms agg20.lsancarc01r.socal.rr.com [72.129.37.0]
6 17 ms 23 ms 23 ms bu-ether16.lsancarc0yw-bcr00.tbone.rr.com [66.10
9.6.102]
7 21 ms 20 ms 17 ms 0.ae0.pr1.lax00.tbone.rr.com [107.14.17.248]
8 34 ms 33 ms 36 ms ix-24-0.tcore1.LVW-Los-Angeles.as6453.net [66.11
0.59.81]
9 19 ms 18 ms 18 ms if-2-2.tcore2.LVW-Los-Angeles.as6453.net [66.110
.59.2]
10 19 ms 18 ms 17 ms 64.86.252.134
11 * 17 ms 18 ms ae-5.r21.lsanca03.us.bb.gin.ntt.net [129.250.5.8
5]
12 85 ms 89 ms 84 ms ae-6.r22.asbnva02.us.bb.gin.ntt.net [129.250.3.1
88]
13 88 ms 87 ms 89 ms ae-8.r23.nycmny01.us.bb.gin.ntt.net [129.250.2.1
48]
14 87 ms 87 ms 88 ms ae-1.r05.nycmny01.us.bb.gin.ntt.net [129.250.4.6
9]
15 122 ms 114 ms 114 ms ae-0.choopa.nycmny01.us.bb.gin.ntt.net [128.241.
2.202]
16 111 ms 110 ms 109 ms 108.61.244.41
17 * 114 ms 113 ms 108.61.244.50
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 *

etc..etc.

[Wisteso]

Kevris, you're the only person so far not going through GTT. How bad is the disconnecting for you?

I route through NTT as well (roadrunner too), but have not been having any issues for the last week. It could be that NTT is having minor issues as well, but not as severe.

Had a guildy having the issues as well, confirmed he was also routing through gtt.net

[Wisteso]

Which VPNs are you guys using with success? VpyrVPN?

[nyclin]

Packet loss on the 4 hops that showed it was bad at first but then essentially stopped. Had problems zoning/logging in all night.


|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 112 | 112 | 0 | 0 | 5 | 2 |
| 71.229.192.1 - 0 | 112 | 112 | 8 | 13 | 39 | 10 |
|xe-10-2-1-0-sur01.denver.co.denver.comcast.net - 0 | 112 | 112 | 8 | 12 | 57 | 11 |
|ae-10-0-sur02.denver.co.denver.comcast.net - 1 | 108 | 107 | 0 | 12 | 43 | 9 |
|ae-20-0-ar01.aurora.co.denver.comcast.net - 1 | 108 | 107 | 0 | 13 | 24 | 13 |
|he-0-5-0-4-cr02.denver.co.ibone.comcast.net - 0 | 112 | 112 | 11 | 16 | 31 | 18 |
|be-11317-cr01.dallas.tx.ibone.comcast.net - 1 | 108 | 107 | 0 | 29 | 40 | 29 |
|he-0-12-0-1-pe03.1950stemmons.tx.ibone.comcast.net - 1 | 108 | 107 | 0 | 28 | 36 | 28 |
| 75.149.231.30 - 0 | 112 | 112 | 24 | 27 | 40 | 35 |
| xe-3-0-1.nyc38.ip4.gtt.net - 0 | 112 | 112 | 59 | 63 | 80 | 63 |
| ae0-150.cr2.nyc3.ip4.gtt.net - 0 | 112 | 112 | 59 | 63 | 90 | 61 |
| as20473.ae7.ar2.nyc3.us.as4436.gtt.net - 0 | 112 | 112 | 63 | 76 | 126 | 72 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________| ______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

[tarkhis]

So what can be done if we don't have access to a VPN. Anyway to reroute so we can play again? What would be the next steps?

[Stormfists]

This issue has been posted across 10 different threads. Note that it is affecting Europe/rest of world as well.

The devs are aware and are working on it.

There is however a way we can all help speed up the fix. Hit the donate button, give a few dorras.

[quido]

power cycling my router and modem seems to have fixed this for me

[Kevris]

Kevris, you're the only person so far not going through GTT. How bad is the disconnecting for you?



Not horrific, but not good. I was zoning a lot collecting Rebby's rat whiskers with my druid last night and was dropping 1 in 15 times. The load times between zones were really bad, and I know it's not my PC (SSD, i7 5930 at 4.4, GTX 980).

[Michael Cera]

I agree with the OP completely

[12point]

http://www.project1999.com/forums/showthread.php?t=201530

[Wisteso]

So what can be done if we don't have access to a VPN. Anyway to reroute so we can play again? What would be the next steps?

We find the pattern. It seems pretty clear that its a GTT.net issue. At this point someone can probably call them and report an issue with their network. (Same thing I did with XO Communications).

Though its better if a legitimate business does it (like an admin from P99), rather than some random guy calling for some other random guys that cant play their game. At that point, they'll check it out and if they notice the problem too, they'll fix it (if they can).

[Deliverator]

Think it is time to start locking these extraneous threads. This is like the 15th version of this thread I've seen over the last 3 days.

[Docx]

what is this crap today?

[Wisteso]

Move the discussion to

http://www.project1999.com/forums/showthread.php?p=1966994

Official (i guess) thread, started this morning.