Server Issues?

[furen]

One of my friends who hadn't been able to log on at all since thrusday (since he couldn't change his IP) finally got on not too long ago. I went to LJ (one of my dead zones) and it works now. This might be fixed now.


Edit: and if it doesn't work for you, maybe they have to go through characters over time so maybe it will be fixed for everyone over the next while I guess we'll see.

[GanondorfLeviathan]

Update: Misa Coast and Ru'Lude are fine now, I'll assume Xarca and Tree are going to be nice to me again too >.> since update lol...hope everyone else gets fixed soon :/

Ganon

[Taj]

Update: Misa Coast and Ru'Lude are fine now, I'll assume Xarca and Tree are going to be nice to me again too >.> since update lol...hope everyone else gets fixed soon :/

Ganon

You called me a noob for kiting Steelfleece. Fuck you.

[Tekki]

Yay for kaiser. Dead zones, and update problems fixed.

[Xavier]

Dead zone really screwed w/ me earlier. I was all set to camp Simurgh after the maint (I want the rare/ex boots, because rare/ex = legit player damnit)...except Crawler's Nest decided to be the gateway to hell for both my chars.

I had trouble around 8:30pm or so w/ Apollyon, but plugging directly into my modem and skipping the router fixed it.

[S N K]

Dead zone really screwed w/ me earlier. I was all set to camp Simurgh after the maint (I want the rare/ex boots, because rare/ex = legit player damnit)...

I *almost* missed the sarcasm in that post.

[GanondorfLeviathan]

<3

Ganon

[Ravenlokk]

Unrelated to this threads current discussion but. . .
Just wanted to mention: the Dead Zone Thread is getting filled with shit that should be posted in here. So that one can stay fairly clean and easy to datamine.

Also- in response to the people doing a Netstat to see what FF Server they're connected to- each zone has an independent server (they load at dif times after maint); therefor, the zone you are in may be impacting your Netstat. Not sure about that, but just a thought.

[doofy]

Dead zone issue seems resolved, but now the same "abnormal R0ing" is occuring in other zones after a certain period of time (about 1 hour). Same exact type of d/c as the dead zones were, log off/on and it works again for about an hour before happening again. Anyone else seeing something similar?, has happened 3 times now while farming diorite.

-Vyzrael (Asura)

[Ravenlokk]

Going to test lower jeuno now since you mentioned Dead zones fixed (it was dead for me yesterday).

Someone in my LS found his first dead zone today... After we gathered for Dynamis-Bubu and tried to enter. . .

/comfort Briste ;_;

He tried rebooting, releasing IP, plugging into modem, using PC and PS2. . . nothing was workin for him.

Edit: OH SHIT IT WORKS!!

[Zirk]

My north sandy deadzone randomly fixed itself like a day or two before this update, so I don't think they ninjad anything, just a matter of time.

[Carrots]

My north sandy deadzone randomly fixed itself like a day or two before this update, so I don't think they ninjad anything, just a matter of time.

mmhmm ISPs around the world united in an unprecedented effort to fix this problem,
that has once again existed(?) since SE patched server & client software, during the exact
same time as SE scheduled a maintenance & client update - what an effort!

...say hi to the easter bunny next month 8)

[Priran]

I can now log into POL, zomg

[Aethaeryn]

Dead zone issue seems resolved, but now the same "abnormal R0ing" is occuring in other zones after a certain period of time (about 1 hour). Same exact type of d/c as the dead zones were, log off/on and it works again for about an hour before happening again. Anyone else seeing something similar?, has happened 3 times now while farming diorite.

-Vyzrael (Asura)

I've had the abnormal R0 thing going on for the past few weeks... I don't think it's ISP related because A) I play other games without any issues, and sometimes I have them going at the same time and never notice a thing. And B) It only happens in certain areas. Usually mine is just an r0 out of no where that happens 2-3 times before it finally stops. ._. Or I can just move to another area and it stops after the first time. I dunno if it's related to the other problems, but I really hope so. It's not fun being disconnected while fighting an NM or when you're up for priority on something in Dynamis. Getting frustrated. ;_;

[Aerides]

Quick check round my mules my main town dead zones (Upper J, B Mines, Metal, W Port) all clean and running BAU.

Maybe I get to go to Limbus thursday afterall!

[colomis]

All of my "dead zones" appear to be gone now as well.

/ninjafix

[divisortheory]

I've had the abnormal R0 thing going on for the past few weeks... I don't think it's ISP related because A) I play other games without any issues, and sometimes I have them going at the same time and never notice a thing.

Presumably those other games all have servers hosted in the same building as SE's FFXI servers?

And B) It only happens in certain areas.

What a coincidence! SE has different physical servers (and hence IP addresses) for different zones, and they may each use different routing for a packet to get from your machine to the server machine.

[Codernaut]

I've had the abnormal R0 thing going on for the past few weeks... I don't think it's ISP related because A) I play other games without any issues, and sometimes I have them going at the same time and never notice a thing.

Presumably those other games all have servers hosted in the same building as SE's FFXI servers?

And B) It only happens in certain areas.

What a coincidence! SE has different physical servers (and hence IP addresses) for different zones, and they may each use different routing for a packet to get from your machine to the server machine.

I agree that A and B were worthless arguments but the idea that SE isn't somehow involved with this issue is crazy.

It's either not SE's fault and they did something to uncover the problem, or it is their fault and they're being dicks about it.

It happened directly after a major maintenance... something they did (even if it's not their fault) caused this to start happening... or it's just the biggest coincidence ever.

[divisortheory]

I agree that A and B were worthless arguments but the idea that SE isn't somehow involved with this issue is crazy.

It's either not SE's fault and they did something to uncover the problem, or it is their fault and they're being dicks about it.

It happened directly after a major maintenance... something they did (even if it's not their fault) caused this to start happening... or it's just the biggest coincidence ever.

Oh I don't disagree that it was either a direct or indirect result of something they did, I was mostly just pointing out that, like you said, A and B were worthless arguments.

[Fluid]

It's either not SE's fault and they did something to uncover the problem, or it is their fault and they're being dicks about it.

It happened directly after a major maintenance... something they did (even if it's not their fault) caused this to start happening... or it's just the biggest coincidence ever.

It wouldn't seem too far-fetched to think that the increased traffic generated by a patch of this size (the largest since Zilart, I recall reading) could lead to a crash on one of these backbone servers people keep mentioning. Did SE directly cause the problem? Not per se... but it was still their obligation to find the cause and make sure the problem was solved.