Those of you who have AT&T for your ISP have noticed the inability to connect to CP since Wed evening. I have received around 30 complaints so far, all from AT&T customers only. There is a bad route between AT&T and CigarPass.
I have had the data center where the CP server is housed fully evaluate everything, and even had the server moved to a different node. The issues still persist. I have done everything I can from a server standpoint, and it's in AT&T's court to resolve. Unfortuntely AT&T is unwilling to investigate, and claims it's an issue with something outside of their network.
A quick Google search for "AT&T routing issues" or "AT&T 502 bad gateway" sure pulls tons of results about the many issues AT&T has with their network.
Two solutions:
1. I move the server to an entirely new data center / host. I am very hesitant to doing this, as why should I sever ties with a company I've been doing business with for 7+ years, and they have outstanding customer service? I have a hard time doing something like that, only to get around the bad route in AT&T's network.
2. I setup a CDN and see if that resolves the issue. So, I'm going to reroute all DNS/traffic through CloudFlare for now and see if that helps. DNS should propogate over the next 4 hours.
I encourage you to call AT&T and file a complaint if that's your ISP and you can't connect. I can only control the server and DNS, I have zero control over the routers between AT&T and the server.
I have had the data center where the CP server is housed fully evaluate everything, and even had the server moved to a different node. The issues still persist. I have done everything I can from a server standpoint, and it's in AT&T's court to resolve. Unfortuntely AT&T is unwilling to investigate, and claims it's an issue with something outside of their network.
A quick Google search for "AT&T routing issues" or "AT&T 502 bad gateway" sure pulls tons of results about the many issues AT&T has with their network.
Two solutions:
1. I move the server to an entirely new data center / host. I am very hesitant to doing this, as why should I sever ties with a company I've been doing business with for 7+ years, and they have outstanding customer service? I have a hard time doing something like that, only to get around the bad route in AT&T's network.
2. I setup a CDN and see if that resolves the issue. So, I'm going to reroute all DNS/traffic through CloudFlare for now and see if that helps. DNS should propogate over the next 4 hours.
I encourage you to call AT&T and file a complaint if that's your ISP and you can't connect. I can only control the server and DNS, I have zero control over the routers between AT&T and the server.