Recent zone loading freezes, crashes, & failure to connect to server

[phiren]

Can you other AT&T users open up command prompt .. do a:
tracert login.eqemulator.org >eqtrace.txt

It will output the file "eqtrace.txt" in whatever directory you are in .. usually:
C:\Users\<yourname>\eqtrace.txt

I did a few different ones staggered:

tracert login.eqemulator.org >eqtrace111.txt
1 minute later
tracert login.eqemulator.org >eqtrace222.txt
1 minute later
tracert login.eqemulator.org >eqtrace333.txt
1 minute later
tracert login.eqemulator.org >eqtrace444.txt

See if you notice any similarity in the hops.

The hop in between my 3rd and 5th .. 70.143.193.158 was a 25% 'success' in traceroute. Could be a few reasons .. but 25% is about the success rate of logging in. If all you AT&T users are being routed through that IP address, and it's flaky, that could be the source.

#3 Hop: 5 ms 4 ms 4 ms 71.155.29.24
#4 Hop: 4 * 7 ms 7 ms 70.143.193.158
#5 Hop: 5 9 ms 7 ms 7 ms 12.83.80.233

In other words .. if you are AT&T and do a traceroute .. it would be interesting to see if we are ALL getting routed through:
71.155.29.24 -> 70.143.193.158 -> 12.83.80.233
Most likely it would be your 3rd / 4th / 5th hops .. but it might be different #s depending.

If you are getting a * * * * * between the 71.155.29.24 hop and the 12.83.80.233 hop , that might be telling it's the source. How to get that fixed is a different problem. Hopefully AT&T knows it's broken or having problems and fixes it soon on their own.

Or it could just be normal that 70.143.193.158 doesn't respond to traceroutes *sometimes*... although that would be weird.

[Abner]

I tried the tracert to the eqemulator as well and got the same timeouts after the choopa.net stuff:


13 * 49 ms 49 ms vl23-br2.pnj1.choopa.net [66.55.130.53]
14 * 51 ms 51 ms ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61.80.218]
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 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

[PerroDeAqua]

This started happening to me a few days ago

[Erica]

10 91 ms 91 ms 91 ms vultr-ic-318452-nyk-b2.c.telia.net [62.115.149.39]
11 * * * Request timed out.
12 91 ms * * ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61.80.218]
13-30 * * * Request timed out.

This might have happened a couple times in the past, but never this bad. I've been experiencing it since Friday I believe. Today it is even worse than previous days.

If I finally get on I'm fine unless I zone, then I need to cross my fingers.

[EQBallzz]

How are you guys getting that to work? I get "unable to resolve target system name login.eqemulator.org". It works when I just do eqemulator.org but that login prefex isn't working.

That being said I'm seeing the same timeout using just eqemulator.org when it hits ae-0.choopa.nycmny01.us.bb.gin.ntt.net and v1203-cr1.ewr3.choopa.net. I'm also using ATT Giggapower service. I been having this issue all weekend and can't log in today either.

[herb_gotti]

Same thing is going on with me. It seemed to get worse today after I did the file update for the patch. It was working decent until an hr into the game. Now I can't even get back into the game. I too am an AT&T user.

[EQBallzz]

BTW, I called the "choopa" hosting service tech support and they said their servers don't respond to pings or tracert commands so would probably show as a timeout or question mark but he also said if I didn't have an account with them they couldn't provide me technical support so who knows.

[Sactar]

Having same issues here as well with server screen and zone crashes. Is worse today then last couple of days. I also have Att in TX

[phiren]

The "Choopas" are going to be fine in my opinion. Those aren't AT&T.. and if the "Choopas" were the problem ... EVERYONE would probably have problems right now. But since this seems to be an AT&T U-verse problem ... it's most likely a problem with the hops that are AT&T related... "before the Choopas" [You must be logged in to view images. Log in or Register.]

In other words your internet traffic goes from:
Your router -> AT&T stuff -> Choopas (Probably where eqemulator is hosted)

Everyone else who plays P99 would go:
Their Router -> Their internet company's stuff -> Choopas (Probably where eqemulator is hosted)

So the problem is going to be somewhere in the "AT&T stuff" hops

[phiren]

You AT&T guys -- I'm moreso curious about your first 10 hops -- because that's all AT&T related stuff.

I'm particularly curious if you are seeing these 3 in your first 10-15 hops:
71.155.29.24 <-- seems fine
70.143.193.158 <-- this is the one I think is the problem .. but could really only confirm if other people see it too, might have to run a few iterations of a staggered tracert like i suggested
12.83.80.233 <-- seems fine