Since 7/30 now every zone = crash

[ld420]

Hello, did something change server side? Since 7/30 all of a sudden now when I zone I hard lock up, or crash to login almost every time I zone. If I dont crash, it takes 2 minutes sometimes to clear zoning. I havent changed ANYTHING. No updates, no unusual web browsing, I have scanned for virus, as well as malware....nothing at all has changed my end. Is anyone else having issues?

[Shyynmoore]

Indeed, very same thing. Since Saturday July 30th. No idea why. A few others in my guild have reported the exact same thing...... i keep stumbling along, hoping it gets better soon. :confused:

[papito]

same problem here

[ld420]

So I went through the trouble of reinstalling Titanium on a fresh windows install, and also using default UI, minimal graphics, still same crashes. So, im ruling out anything on my end. This is super sadface. :(

[Duvain]

Same thing is happening to me. I was thinking it was a problem with my PC since it doesn't seem to be happening to everyone. Everything else with my PC works fine so it's good to know it's not just me, it is driving me crazy. It's very frustrating. Most of the time I zone, it boots me to the login screen. I play on red99 mostly so it's making me nervous that my character might be popping out on the other side of the zone sitting there LD where someone could easily PK.

[ld420]

So I am noticing now, every so often on the crashes (it has actually gotten worse, cant get past character selection half the time now) I get black screen message, big white letters saying "The Server Is Not Responding", then same black screen, big white letters telling me I have been disconnected. :(

[Duvain]

So I am noticing now, every so often on the crashes (it has actually gotten worse, cant get past character selection half the time now) I get black screen message, big white letters saying "The Server Is Not Responding", then same black screen, big white letters telling me I have been disconnected. :(

Yea mine does that a lot also.

[Castamere]

This is happening to me too. Never was a problem before yesterday 07/30. I believe it was right after the server went down. Any updates?

I've tried a fresh install as well. I've tried it on both my solid state and my spindle drive. Tried to install outside of program files as well. No luck.

[ld420]

My weekend play has been ruined. I cant even log in anymore, all it does is crash, or freeze. Went from really bad to worse. 100% crashing and freezing now on zoning. I hope it gets fixed. Just got to where I can port people too yesterday. Guess ill go play lol or something. :(

[Castamere]

Yea it sucks. Unless you stick to one zone the game is unplayable. Hoping for a fix soon

[Castamere]

I don't know if this matters, but I tried loading up another emu server on the list (EZ server) and it started doing the same thing after a while... no idea where to look now.

[ld420]

I don't know if this matters, but I tried loading up another emu server on the list (EZ server) and it started doing the same thing after a while... no idea where to look now.

May be a prob with EQEmu or something.

[Duvain]

It is very discouraging. I may try a different router or something, wonder why it doesn't happen to everyone. My ping is only 64ms.

[papito]

still happening over here, sometimes i even sit at a loading screen for 2 mins before it either kicks me off

[Senaleb]

Something is weird, my first character I got to lvl 7. I zoned into N. Ro. Game crashes to desktop. I'm thinking ok maybe it's a corrupt N. Ro file or something. Today, on my druid who's lvl 15 or 16...I zone from West Freeport to EC. Game crashes to desktop. Now I reload EQ, it says my druid is in N. Ro...what. HALP!!!

[Caldwin]

I'm having the same issues, along with sometimes having an occasional issue with the forums.

I'm curious, I'm on Brighthouse. Anyone having issues not on Brighthouse? My sister is also on Brighthouse and has the same issues, until she connected thru her cell phone. She's had no problems with her phone. However, neither her or me have had issues with other sites, such as youtube on Brighthouse.

I did 2 trace routes, one on the project 1999 forums, the other on the login server. Below are the results. Both had time outs on hop 13. But, the login server had trouble on hop 16 and couldn't get past hop 17.

===============================================
Tracing route to wiki.project1999.com [108.61.129.170]
over a maximum of 30 hops:

1 8 ms 4 ms 11 ms XYMOX35 [192.168.1.1]
2 17 ms 18 ms 19 ms 10.52.192.1
3 18 ms 18 ms 18 ms ten0-7-0-0.ORLD23-ser1.bhn.net [72.31.194.40]
4 29 ms 28 ms 28 ms ten0-4-0-6.orld31-car1.bhn.net [97.69.194.186]
5 25 ms 28 ms 29 ms 72-31-220-148.net.bhntampa.com [72.31.220.148]
6 68 ms 23 ms 28 ms 72-31-188-104.net.bhntampa.com [72.31.188.104]
7 23 ms 18 ms 28 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66.109.6.98]
8 31 ms 28 ms 28 ms 0.ae1.pr0.mia00.tbone.rr.com [66.109.1.87]
9 33 ms 32 ms 55 ms mai-b1-link.telia.net [62.115.40.145]
10 55 ms 49 ms 48 ms ash-bb4-link.telia.net [62.115.136.204]
11 52 ms 58 ms 55 ms nyk-bb2-link.telia.net [62.115.136.200]
12 52 ms 57 ms 59 ms nyk-b2-link.telia.net [213.155.130.30]
13 * * * Request timed out.
14 53 ms 58 ms 57 ms vl24-br2.pnj1.choopa.net [108.61.248.14]
15 53 ms 57 ms 69 ms vl20-br1.pnj1.choopa.net [108.61.244.41]
16 52 ms 49 ms 59 ms ethernet1-2-1-c8-12-b2-1.pnj1.choopa.net [108.61.244.50]
17 53 ms 49 ms 59 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
18 55 ms 79 ms 61 ms 170.rogean.com [108.61.129.170]

Trace complete.

===============================================

Tracing route to login.eqemulator.net [66.55.145.2]
over a maximum of 30 hops:

1 9 ms 9 ms 3 ms XYMOX35 [192.168.1.1]
2 16 ms 18 ms 19 ms 10.52.192.1
3 13 ms 31 ms 15 ms ten0-7-0-0.ORLD23-ser2.bhn.net [72.31.194.42]
4 29 ms 28 ms 19 ms ten0-4-0-6.orld31-car2.bhn.net [97.69.194.188]
5 29 ms 22 ms 26 ms 72-31-220-150.net.bhntampa.com [72.31.220.150]
6 27 ms 28 ms 29 ms 72-31-188-180.net.bhntampa.com [72.31.188.180]
7 24 ms 28 ms 28 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66.109.6.98]
8 30 ms 30 ms 29 ms 0.ae1.pr0.mia00.tbone.rr.com [66.109.1.87]
9 25 ms 37 ms 41 ms mai-b1-link.telia.net [62.115.40.145]
10 45 ms 48 ms 48 ms ash-bb3-link.telia.net [62.115.143.68]
11 64 ms 79 ms 58 ms nyk-bb1-link.telia.net [62.115.138.22]
12 62 ms 58 ms 58 ms nyk-b2-link.telia.net [213.155.130.28]
13 * * * Request timed out.
14 54 ms 58 ms 105 ms vl23-br2.pnj1.choopa.net [66.55.130.53]
15 59 ms 58 ms 78 ms ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61.80.218]
16 * 76 ms 66 ms ethernet1-2-1-c8-12-b2-1.pnj1.choopa.net [108.61.244.50]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

[Tankdan]

When I had this issue, I just used a free VPN (Cyberghost) for a week until it went away. I tried all kinds of fixes such as changing DNS, resetting IP, etc, but VPN was only thing to work and eventually it was back to normal after 4-5 days.

[Duvain]

I do have Brighthouse so maybe that's where the issue lies. I'm in Florida.

[Caldwin]

I just noticed the first trace in my earlier post was for the wiki, but www.project1999.com (which contains the forums) has a similar trace as the wiki, where hop 13 timed out. But, it may be a router that doesn't respond to trace route commands.

Anyway, it looks like the login server trace is still timing out on hop 16 or 17 (choopa.net).

[Shyynmoore]

BTW.....Florida, and Brighthouse here too...... Starting to see a trend.....

[trite]

I do have Brighthouse so maybe that's where the issue lies. I'm in Florida.

Having issues with slow zones and LD zones. Also using brighthouse in florida

[Castamere]

Florida brighthouse here

[Castamere]

Also, I tried using cyberghost and it looks like it blocks the required ports for project 1999. I tried from multiple European countries as well with no luck.

[Duvain]

I'm currently talking to Brighthouse support about it, I sent them the trace route info.

[Castamere]

I'm currently talking to Brighthouse support about it, I sent them the trace route info.

Thanks Duvain, keep us posted

[Duvain]

They opened a ticket with their networking team. If you guys get a chance, try to call Brighthouse support about it also, the more tickets they get on it the quicker they'll look at it. Number is 1-855-222-0102. Make sure you tell them there seems to be a routing issue for everyone with Florida Brighthouse to login.eqemulator.net.

[Castamere]

Ok I just put in a call as well and told then which hop it was getting hung up at. I'm assuming everyone's getting stopped at choopa.net. They said that the more tickets that are in the queue for this issue the faster they will get to it. So, please folks put in the call. It took me 10 minutes to go through the process.

Meanwhile, if anyone knows of a workaround for this that would be great.

[ld420]

Im on Bright House in Orlando as well. Sonofa. Tracert hangs at choopa, and ping gives 100% packet loss. this is super lame =(

[Castamere]

Im on Bright House in Orlando as well. Sonofa. Tracert hangs at choopa, and ping gives 100% packet loss. this is super lame =(

1-855-222-0102

The more people call, the faster we'll be able to play again.

[Savok]

BH here as well... I'm going to call tomorrow as well.

[Savok]

Ask for level 2 and that you would like to submit a tracert file.

[Savok]

If you sign up and post here: https://www.dslreports.com/forum/bhousedirect you can get in contact with BHN support directly by engineers who can do something about it.

[Castamere]

I've had a couple [Non-BrightHouse] friends go to http://www.downforeveryoneorjustme.com/ and query login.eqemulator.net, and they each get DOWN as a result. So, that would suggest this is a misleading server to run a tracert on for our purposes.

If you sign up and post here: https://www.dslreports.com/forum/bhousedirect you can get in contact with BHN support directly by engineers who can do something about it.

I'd be happy to post on those forums, but after reading what Kinaki posted, i'm not even sure we're giving them the right information. Any ideas?

[LGraves]

Same here. BHN in Florida. I'll call when I can.

[Gilder]

Brighthouse and Florida checking in.

There are literally dozens of us!

[surron]

BH in FL checking in. It's also a problem for me on TAKP so it looks like eqemu.

here is from work (also on BH)

login.eqemulator.net [66.55.145.2]


3 6 ms 5 ms 5 ms 5.GigabitEthernet1-2.GW2.ORL4.ALTER.NET [152.179.146.117]
4 13 ms 13 ms 13 ms 0.ae10.GW1.MIA19.ALTER.NET [140.222.231.83]
5 15 ms 14 ms 13 ms teliasonera-gw.customer.alter.net [152.179.236.22]
6 36 ms 37 ms 36 ms ash-bb3-link.telia.net [62.115.141.119]
7 121 ms 41 ms 41 ms nyk-bb1-link.telia.net [213.155.131.226]
8 41 ms 41 ms 46 ms nyk-b2-link.telia.net [213.155.130.28]
9 45 ms 49 ms 49 ms vultr-ic-318452-nyk-b2.c.telia.net [62.115.149.39]
10 42 ms 42 ms 44 ms vl24-br2.pnj1.choopa.net [108.61.248.14]
11 41 ms 42 ms 41 ms ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61.80.218]
12 * 43 ms 43 ms ethernet1-2-1-c8-12-b2-1.pnj1.choopa.net [108.61.244.50]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26

here is from home


3 8 ms 9 ms 7 ms ten0-0-0-3.orld28-ser2.bhn.net [71.44.48.40]
4 11 ms 11 ms 11 ms ten0-0-0-9.orld31-car2.bhn.net [72.31.188.140]
5 15 ms 20 ms 12 ms 72-31-218-46.net.bhntampa.com [72.31.218.46]
6 14 ms 14 ms 14 ms hun0-2-0-8.ORLD71-cbr1.bhn.net [72.31.220.240]
7 18 ms 15 ms 19 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66
109.6.98]
8 19 ms 18 ms 19 ms 0.ae1.pr0.mia00.tbone.rr.com [66.109.1.87]
9 21 ms 23 ms 23 ms mai-b1-link.telia.net [62.115.40.145]
10 39 ms 38 ms 39 ms ash-bb4-link.telia.net [62.115.141.80]
11 46 ms 43 ms 44 ms nyk-bb2-link.telia.net [62.115.136.200]
12 48 ms 47 ms 45 ms nyk-b2-link.telia.net [62.115.134.108]
13 49 ms 49 ms 49 ms vultr-ic-318452-nyk-b2.c.telia.net [62.115.149.3
]
14 53 ms 45 ms 46 ms vl24-br2.pnj1.choopa.net [108.61.248.14]
15 46 ms 47 ms 46 ms vl20-br1.pnj1.choopa.net [108.61.244.41]
16 * * 46 ms ethernet1-2-1-c8-12-b2-1.pnj1.choopa.net [108.61
244.50]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

trace complete.


I called the number above and the robot lady asked for a reason I said "internet difficulties" and then I was routed to a guy who asked for my account info. I stated a trace route on ip address 66.55.145.2 was failing at a specific hop (choopa.net 108.61
244.50) and I would like to report this issue. The guy confirmed the issue on his end by pinging 66.55.145.2 and then said he would escalate the issue up to the engineers. Probably will help if more people do this.

[Duvain]

It does seem better today, maybe they fixed it. We'll see later.

[Shyynmoore]

Working good so far!!!! I've zoned 10 to 15 times so far with no issues :) Yay!