This wasn't just today.Try not doing it on NA monday primetime, where the main attractions are EX upkeep and Coil?
Congestion on the busiest day of the week? Blasphemy!
Also- I pugged t1-4 today, only 2 people complained of rubberbanding, and they live in the same town.
In Florida.
Reset day congestion + extra hops, a catastrophe is not.


There is no excuse for SE not commenting on the situation. The issue is between SE and the T1 networks in Montreal, Cogent and Level 3 for most players. Not you or your ISP as it is outside your control and your ISP's network.
All the excuses here defending SE is selfish. It is SE's responsibility to resolve with the T1 networks in Montreal, period.
Some facts for my situation.
- I am within 350 miles of the server.
- My routing to the server is within 500 miles to the server.
- 12 hops to the server.
- No issues prior to 2.1, 20-30ms constant to server, zero packet loss.
- Since the issue started Cogent and Level3 are dropping packets, this is a greater problem than simple lag/latency.
- I pay for a 50/50 Internet Service.
- I pay my monthly fees.
Using a Proxy Service and not going through Cogent or Level3 networks brings my ping down to 40ms and zero packet loss.
Why should I have to pay for SE's issue with other T1 Companies by paying for a VPN/Proxy service?
They did. They changed PR from 0.3 to 0.1. That's acknowledging the problem and doing something about it. The current issue isn't exactly 100% on their end so what do you want them to say? "Ok so there's a problkem with Level3"???
Will that make you happy? I mean, all they do is say somethin and that isn't exactly going to fix the problem another company is having which means the complaints won't stop.
Level3 isn't a subsidiary of Square Enix so there's not much they can do because it's not exactly their problem, it's a problem with another company that SE has no control over.Why should I have to pay for SE's issue


There are many ppl here that have spent hrs researching their issues and using outside resources.
It is SE's issue as it affects the service they provide. It's the pipeline (Upstream) in and right outside their network: ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74].
Ormuco is SE's Server provider with Level 3 as one of their Upstreamers.
It is their issue to deal with the upstreamer, even if they have to pay for more allotted bandwidth. SE isn't special in this situation, other companies, not tied to T1's pay for allotted bandwidth to correct issues like this, its normal.
This isn't some post about crying over upcoming patch changes. It's a legitimate complaint affecting a lot of paying customers for over a month with zero response from its provider.



To further clarify, it is not an issue inside SE's network, but beyond the boundary, under ownership and management of Level 3.
SE's true responsibility (after the internal adjustments) is to continue to work with level 3 until they can isolate and resolve their routing issues.
Not much hands-on with that. And I expect that is what they have been doing ever since the Level 3 issue was reported.

Libel, Law suits, Slander, Defamation (oh my!)
Irrelevant. Location is not an indicator of a stable connection when the node experiencing problems is in Montreal (but before SE servers)
See above.
Inefficient route paths are not on SE to fix. Please contact your ISP and/or backbone
Coincidence. Or Ormuco had the path changes or backbones switched. Please contact Ormuco or Level3 to file a bug.
Indeed. Their hardware is likely failing or the node doesn't have the amount of switches to support the traffic.
Sounds like an ISP issue. COntact your ISP to bring it to their attention and either ask for a discount on your monthly service or change providers.
For a service that doesn't guarantee you stable connections. Read the ToS
BECAUSE. IT'S. NOT. SQUARE'S. FAULT. That you use a VPN and it fixes the issue proves it. If you had packet loss on the host servers, then yes, it would be on Square. You don't. You have packet loss on a node that is neither owned, operated, or maintained by Square Enix LTD. Square Enix Holdings, or Square Enix International. Everyone routing through that node is having problems. EVERYONE. You see it more because you rely on stable transfer. Grandma Jo doesn't notice when watching youtube because it doesn't rely on ping/jitter values.
That's what I've been saying the entire time?If you're dropping packets it's obviously not SE fault... I don't know wat more to say. I can generalise lag because most people can fix it through using VPN. Using a VPN means that it's your route to the SE server that is crap, NOT that the SE servers are lagging. If SE was having significant lag issues, everyone would be experiencing it and furthermore, VPN wouldn't help.
Changing ISP as a matter of fact does help by the way. Because another ISP may be using a more optimum route to their server than another.
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.

Reply With Quote


