right around the time this thread was made there was a huge lagspike for me as well and I'm not american, so I highly doubt it was tied to US ISPs and more likely a server hiccup on SE's end that didn't affect everyone
right around the time this thread was made there was a huge lagspike for me as well and I'm not american, so I highly doubt it was tied to US ISPs and more likely a server hiccup on SE's end that didn't affect everyone





Internet is NOT point to point. It goes through many hops. If your connection routes through the hop that was having the issue, you get lag.
What country you are from doesn't matter. How traffic gets routed does.
What you just said is the equivalent of saying "yeah, there was a traffic jam in Texas, and I'm heading to California along the southern US, but since I'm from Brazil, it doesn't effect me. It must be California's fault"
no, I'm said that it wasn't exclusively a comcast thing as people thought it was at the beginning of the thread and also never not once said that the issue is on SE's end, just that it was likely, as it was beforeInternet is NOT point to point. It goes through many hops. If your connection routes through the hop that was having the issue, you get lag.
What country you are from doesn't matter. How traffic gets routed does.
What you just said is the equivalent of saying "yeah, there was a traffic jam in Texas, and I'm heading to California along the southern US, but since I'm from Brazil, it doesn't effect me. It must be California's fault"
but go off queen!





It can be a comcast issue even for people who dont have comcast as their ISP, if their ISP uses comcasts lines at some point. Not all ISPs own the full length of their connections, and even then, they have to connect outside the ISP at some point. This is likely where the bad node is, which is why it effects people not on comcast, and people who have comcast.
And yes, you did in fact say "its most likely an issue on SE's servers that didn't effect everyone"
I'm simply trying to correct misconceptions on how people connect to things over the internet, as many don't seem to understand how it all works, and SE takes the brunt of the blame for things completely out of their control most of the time.
Very very few instances exist these days where the servers themselves are the issue, and we get updates on those when they happen via the lodestone.
Last edited by Valkyrie_Lenneth; 04-11-2021 at 06:57 AM.
I did not, I said more likelyIt can be a comcast issue even for people who dont have comcast as their ISP, if their ISP uses comcasts lines at some point. Not all ISPs own the full length of their connections, and even then, they have to connect outside the ISP at some point. This is likely where the bad node is, which is why it effects people not on comcast, and people who have comcast.
And yes, you did in fact say "its most likely an issue on SE's servers that didn't effect everyone"




|
|
![]() |
![]() |
![]() |
|
|
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


