Service Unavailable - Fail to connect

#121 Were you able to record the information requested above and send it to David?

#122 I have been sending him the info yes but nothing is getting done, this has been going on for over a month now. It is a bit frustrating to have my 10 students manually search the 50,000 posts to find anything. Please someone look into this.

#123 I just noticed Novack's post and thought I should correct it. Editing the host file does fix the problem for TDN as well. I think his post was made that day TDN itself was down. Using the IP or origin address works until you try clicking a link that someone posted that doesn't use one of those two. The host file workaround fixes it entirely.

#124 I finally gave up and edited the Host file too.

Haven't had any problems since. Note, I don't often go to TDN so I can't speak for that side.

#125 Doing what I can, which is basically logging and hoping.

#126 I don't have an IP address because I'm behind my ISP's NAT and there is nothing I can do to get around that. The only IP I can give you is my ISP's. that's the only one visible.

#127 @Scott, good info!

Note: all of those who posted their experience on the TDN side of the problem (including me) talked about the patching procedures NOT working on TDN on any case, so till now was correct to say it doesnt work. Actually, Im correcting the post to say something like "in some cases..."

#128 This is the first I've heard of TDN working for anyone with this problem, hosts file or not.

#129 TDN works for me with the an edited host file.

#130 Had the problem almost permanently, edited host file allowed me to access TDN.

#131 How do you get an edited host file?

#132 Scroll up the page a bit and follow the directions Jon Fernback posted.

#133 This really has been a problem long enough. I don't care if it's at Akamai or GG, this is the GG site and it really makes things seem even more amateurish for the site to be so unreliable.

#134 Are there any updates on this issue?

For me, I always seem to be able to connect to the garagegames.com homepage just fine. But when I try to access certain links, I get the error.

Even after connecting using http://216.116.32.49, I still get this error when trying to access certain pages, such as this page: http://216.116.32.49/docs/torque/general/scripting

#135 There was some debate on an alternative thread, the guys are still working to fix this, with help of some boys from the community.

#136 Just adding that I have the same troubles, for more references. Problem occurs with all browsers on an Intel iMac and intel macbook running both OS X, Windows XP via parallels, and Windows XP via bootcamp. I connect via comcast cable from Bristol, CT. These forums and all other effected areas are down approx 9 out of 10 times i try to access them.

#137 Send me the info:
0) Time and time zone it happened (convert to GMT for Akamai)
1) The Akamai error displayed on the screen (ex: Reference #6.7c7ffea5.1201635804.f491032)
2) Client IP address - use http://checkip.dyndns.org
3) the url that failed (ie http://www.garagegames.com/main/login) (or is it only on POST?
4) traceroute to www.garagegames.com
5) traceroute to a1.g.akamai.net
6) Their OS
7) Their Browser and version
8) if they try to login via origin-www.garagegames.com does it work?

#138 I'm sorry, but someone, somewhere should be fired for this. Are you aware of the amount of business you have probably lost because of this inexcusable website error that hasn't been fixed in over 5 months? Your CEO/CTO should be enraged at this amateur response to a problem that's hampering the availability of their business to make money.

I absolutely cannot have faith in a company that cannot fix a simple DNS issue.

End of story.

#139 You are correct--someone at Akamai should be fired for this, especially since the entire service they provide is based around providing 24/7 worldwide dynamic load distribution through DNS mapping and remote servers.

In case you didn't read much of the content in this post, GarageGames utilizes Akamai for all of our world wild content distribution. They are the ones responsible for DNS issues, unfortunately in this case.

#140 Still using the workaround here, too. Can't connect to the main site most of the time.

Maybe it's not *someone* at Akamai that needs to be fired - maybe you just need to fire Akamai? ;)
It's not like they are the only webhost on the planet.