[Dev response requested] Unplayable lag since the hotfixes

[Sylve]

You both have the same problem on the same ISP. Maybe you should call up your ISP and find out whats going on?

[Tupsi]

You both have the same problem on the same ISP. Maybe you should call up your ISP and find out whats going on?

You would think so. I don't have "unplayable lag" at all and I'm certainly not on Verizon Fios. Got a FC member also on Fios that's having issues, so I think it's safe to say it's currently an ISP issue that SE can't actually fix (as they don't run the ISP.)

[ReplicaX]

You would think so. I don't have "unplayable lag" at all and I'm certainly not on Verizon Fios. Got a FC member also on Fios that's having issues, so I think it's safe to say it's currently an ISP issue that SE can't actually fix (as they don't run the ISP.)

Assumptions, assumptions, assumptions...

SE had their own ISP network maintenance. Looking at my netlog from the 25th and 26th and being a Verizon FiOS customer, the issue isn't even coming from Verizon for me. I get all my packet loss from Ormuco nodes, which is SE's ISP in Montreal.

Thus it would be SE's problem in my case, not my ISP.

[ispano]

Assumptions, assumptions, assumptions...

SE had their own ISP network maintenance. Looking at my netlog from the 25th and 26th and being a Verizon FiOS customer, the issue isn't even coming from Verizon for me. I get all my packet loss from Ormuco nodes, which is SE's ISP in Montreal.

Thus it would be SE's problem in my case, not my ISP.

Then how come the majority, if not all the people with the issue are Verizon customers? There was another online game I played, i've forgotten what it was now, but we had many people with issues and it all boiled down to Verizon there as well. Not saying it IS them, but if it indeed wasn't Verizon, why is only Verizon seemingly having the issue?

[Tupsi]

Assumptions, assumptions, assumptions...

Yes, because the countless "I'm using Verizon and seem to have issues" on here as well as other forum communities is just..assuming it's verizon - I mean, clearly there's no common factor in people with "unplayable lag" lately.

Fyi, if it's SE's ISP that would mean everyone playing XIV ARR to this date would have unplayable lag, no exceptions. There's problems over in that side of the country which means hops by certain ISPs are affected - Verizon clearly being one of them. I'm not on Verizon and I'm not having this issue, however people in my FC on Verizon internet/Fios are having this issue...yes, assumptions..assumptions...

Then how come the majority, if not all the people with the issue are Verizon customers? There was another online game I played, i've forgotten what it was now, but we had many people with issues and it all boiled down to Verizon there as well. Not saying it IS them, but if it indeed wasn't Verizon, why is only Verizon seemingly having the issue?

People really hate to admit when it can be their problem, which is why people get charged $200-500 for taking in a PC/Laptop etc to a shop and turns out it's only a configuration issue. Like..honestly lol, browsing around it's pointing to something with Verizon currently, SE's servers may not be perfect but everyone would be unable to play no matter your ISP if it was purely on SE's end.

[ReplicaX]

Yes, because the countless "I'm using Verizon and seem to have issues" on here as well as other forum communities is just..assuming it's verizon - I mean, clearly there's no common factor in people with "unplayable lag" lately.

Verizon issues not confined to a specific area, but across the USA. All having different routing, except the destination > Ormuco.

12/25/2013 6:44 AM
[Maintenance] Notice of Network Maintenance (Dec. 26)
At the following time, network maintenance will be performed by the internet service provider for the North American/European data center.

Looks like an assumption by you to me.

[Tupsi]

Verizon issues not confined to a specific area, but across the USA. All having different routing, except the destination > Ormuco.



Looks like an assumption by you to me.

Yep, it's not "confirmed" yet the common factor seems to be Verizon - Why is it not affecting everyone that conects to an NA/EU Datacenter then? You're making an assumption by stating it can't actually be verizon, despite there being quite a lot of people using verizon that's having unplayable lag.

It's ok though, it can never be a problem outside of SE, we get that. This reminds me when a large portion of Comcast users couldn't properly stay connected to FFXI for a few weeks yet no one immediately thought it could be SE's ISP, funny how that works.

Incase you were wondering, it was indeed Comcast having issues connecting to Hawaii and Japan at the time.

[ReplicaX]

Yep, it's not "confirmed" yet the common factor seems to be Verizon.

Or Ormuco can have equipment issues/upgrades or changes from rerouting that can effect only certain connection types. This isn't uncommon at all in the gaming or network world.

As I stated previously, it's confirmed on my end, for me. Via my own net logs and a Verizon tandem/routing op. That Ormuco was causing all my packet loss and not Verizon or any other company's network for my route.

My assumption is at least based on findings. The fact that most FiOS customers had no issues until the recent hotfix/server changes and all of the sudden Ormuco performed network maintenance last night when the complaints came flying in.

[ReplicaX]

It's ok though, it can never be a problem outside of SE, we get that. This reminds me when a large portion of Comcast users couldn't properly stay connected to FFXI for a few weeks yet no one immediately thought it could be SE's ISP, funny how that works.

Where did I state this? Tupsi, if you stopped being so defensive and didn't automatically label me as a SE hater/complainer. Maybe you would realize I didn't come into this thread to bash you and/or SE. I provided my findings to help other ppl with the same issue and ISP. Not misdirect them as network issues in general have many variables. Not just SE, the DC's ISP, client's own hardware and ISP, and everything in between as well.

[DSanchez]

Assumptions, assumptions, assumptions...

SE had their own ISP network maintenance. Looking at my netlog from the 25th and 26th and being a Verizon FiOS customer, the issue isn't even coming from Verizon for me. I get all my packet loss from Ormuco nodes, which is SE's ISP in Montreal.

Thus it would be SE's problem in my case, not my ISP.

You are correct. The problem lies with SE's upstream provider for their datacenter, not the user-end.