I've been having the ping problems for about 2 weeks, and during that time, I learned that one friend on Comcast Business class about 10 miles away has no problems. Another friend on Comcast in Chicago (about 20 miles away), also has no problems. This led me to think that the problem may have to do with my particular IP address/subnet, and if I could change it, I might be able to fix it.
I think my last IP was 188.8.131.52. My second IP was 184.108.40.206. Both these IPs had the same problem, and likely exist in a 67.184.225/23 subnet (or something like that, my subnetting is a little rusty). Routing affects whole subnets, not IPs, so a new IP in the same subnet will not work.
The 3rd IP is now in the 24.12.31.xxx network and my routing is almost entirely fixed. Pings are normal, except to Chicago, where I ping 34 instead of the usual 12 (no big problem).
GETTING AN IP IN A DIFFERENT SUBNET FROM YOUR ISP CAN POTENTIALLY FIX YOUR ROUTING PROBLEM
HOW CAN I CHANGE MY IP?:
DSL: At least on AT&T, every time you reboot the modem, it usually get a new IP address. Check your IP addresses and check your pings. Hopefully you can find an IP in an unaffected DHCP pool.
CABLE: At least on Comcast, you get an IP lease that is based on your MAC address. Rebooting devices simply won't work. Most routers allow you to clone and manually provide a MAC address, so you will:
1. Have the router clone the MAC address of your computer, and reboot the router. If you've already cloned the MAC address, then start changing it. It uses HEX values, and each character can have a value of 0 through 9 or A through F, so just change one value each time and you should be good.
2. Power your cable modem off for a few seconds, then power it back on.
3. Make sure the router pulls a new IP address. Most routers will have an option for DHCP Release and DHCP renew, so execute those functions in that order, looking for a new IP when you renew.
4. Repeat the process, testing your ping with each new IP. Note that it will need to be in a different subnet, so you can tell quickly if there's a chance it will work or not. If the first three values are the same, such as 67.184.224, then it isn't going to work
WHY THIS MIGHT NOT WORK:
You may not be able to get an IP in a different subnet, or all the DHCP subnets your router has available are affected. If that's the case, I'm sorry and I hope it's fixed soon. id, please continue to work with Speakeasy on this. I think blocks of IPs are getting tagged with incorrect location information, and it's almost impossible for a user to talk to anyone at an ISP that has a clue to how routing works. Speakeasy at least has to have some contacts. This has been so painful.
PS If this helps, please RATE this thread OR sticky it.
PPS Show me some <3 and please acknowledge and FIX the vertexlight + postprocessing + colorcorrection bugs on Retribution, Almost Lost etc.