Bad routing, deal with it.
Bad routing, deal with it.
If whatever you're shooting doesn't die after you pump 8, 32 caliber, slugs into it, it's probably a dragon.
Playing another game isn't enough research. Run a traceroute.I live in Toronto, 300-400km from Montreal and lag like shit. I chalked it up to my connection and the ISP, but lone behold when I switch to any other game it does not lag. I don't want to point it at SE because it doesn't make sense, but then again it could be their ISP or datacenter causing it.
No, we shouldn't just deal with it. We should be showing our ISP's that they don't run the show here. Especially when they own the nodes that cause bad routing.
1. Traceroute is misleading a lot of nodes/hops deny ping requests.
2. If your ISP doesn't own the bad node, you have little to no hope that it will be fixed. You can pressure your ISP all you want, but your going to need a massive petition that is e-mailed to their CEO/VP(s) stating the problem and pointing out the other ISP's node. That way they feel pressured.
However, the odds of #2 happening are low, "deal with it." Vote with your wallet that verizon fios is screwing you guys over.
If whatever you're shooting doesn't die after you pump 8, 32 caliber, slugs into it, it's probably a dragon.
With the utter lack of competition the only way to vote with your wallet is to completely go without a decent internet connection in all other aspects of your life. It's all or nothing. This isn't a viable method for most people.
Most people with fios have more than enough choice. The fios they are getting iirc is fiber based meaning they live in a populated area with many other ISP.
If whatever you're shooting doesn't die after you pump 8, 32 caliber, slugs into it, it's probably a dragon.
I believe what I said still acknowledges that possibility.
Alter.net is owned by Verizon.1. Traceroute is misleading a lot of nodes/hops deny ping requests.
2. If your ISP doesn't own the bad node, you have little to no hope that it will be fixed. You can pressure your ISP all you want, but your going to need a massive petition that is e-mailed to their CEO/VP(s) stating the problem and pointing out the other ISP's node. That way they feel pressured.
However, the odds of #2 happening are low, "deal with it." Vote with your wallet that verizon fios is screwing you guys over.
Also, just dropping Verizon would mean 2 things for me:
1. Early termination fees. My "wallet" isn't big enough to handle that shit.
2. Comcast is my alternative. I love FFXIV, but I'd quit before doing that.
1. The majority of the rules to ignore ICMP ECHO requests only kick in when there is high congestion. The remaining ones do it as a flat rule. So, if you see a hop that responds at some times, but *'s out at others---guess what that is an indicator of?1. Traceroute is misleading a lot of nodes/hops deny ping requests.
2. If your ISP doesn't own the bad node, you have little to no hope that it will be fixed. You can pressure your ISP all you want, but your going to need a massive petition that is e-mailed to their CEO/VP(s) stating the problem and pointing out the other ISP's node. That way they feel pressured.
However, the odds of #2 happening are low, "deal with it." Vote with your wallet that verizon fios is screwing you guys over.
2. Just like you are a customer of your ISP, your ISP is a customer of their NSP. It is their responsibility to remedy such issues with their service...whether that means working with their contracted NSP to address their issues, or to switch you to another one of their NSP's. Unlike your llimited ISP options in your local markets, the major ISP's are required by regulation to maintain arrangements with no less than 3 NSP's for interconnectivity (at least, it is that way for the US). So.. they always have something they can do if the problem is on that third party's segments. Now, just how willing they are to either go to bat for you against the troublesome NSP or to switch you to one of their alternate providers is another story. However, they have to answer to the regulatory authority on these matters. In both the US and the UK (unsure about other nations) they are compelled by regulatory powers to have sufficient countermeasures in place to combat congested/failing routes (hence the requirement for no less than 3 partners for the exchanges here in the US, not sure about the UK's requirements to that end)--if they are not meeting that responsibility there is a regulatory authority to whom you can file a complaint. In the US, it may be a local board or a statewide office that you go to first (contact details or at least a means to get them must be included in your billing... again, it's a legal requirement), but ultimately you can call on the FCC (unfair practices and what not--they have remedies for many situations at the federal level). In the UK, they have some consumer advocacy thing going on there... don't know the details, but they got brought in once for an issue with FFXI a couple years back and had to put pressure on BT to clean up a problem with O2.
So.. yes.. traceroute is a very useful tool. Even if you are not able to detect the potential signs of trouble yourself, at the very least it provides the specific roadmap of your connectino so that the techs know what/where to look for problems. It is their job... one for which you are paying a subscription that supports their salary. Need to hold them accountable for it.
Last edited by Raist; 10-07-2014 at 01:37 AM.
|
![]() |
![]() |
![]() |
|
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.