I guess I've got a wee bit of addiction to checking this site but I managed to hold of on using a proxy to get around the ban to be able to figure out what the hell was going on :)
With that in mind though, how can I actually tell if I ever get banned?
Comment has been collapsed.
Thanks for the update, cg! My paranoia got the best of me just now... Good thing things have been sorted out now. Cheers :)
Comment has been collapsed.
And I thought I was banned because I've entered too many giveaways from LostSoulVL in a short period :)
He has a very big train - http://www.steamgifts.com/discussion/lxCEA/sgtools-longest-sgtools-train-with-xxx-different-cars-to-date
Comment has been collapsed.
Nevermind some downtimes - as long as SG comes back stronger, better and more awesome than before :)
Thank you for all your work cg and have a nice day!
Comment has been collapsed.
Thanks for the explanation and the upgrade, I was pretty worried for a while, lol.
EDIT: I decided not to blacklist you for this, at least for now... ;P
Comment has been collapsed.
16 Comments - Last post 41 minutes ago by hbarkas
47,159 Comments - Last post 1 hour ago by Calibr3
6 Comments - Last post 2 hours ago by lostsoul67
818 Comments - Last post 2 hours ago by Redpoison11
372 Comments - Last post 2 hours ago by Wok
166 Comments - Last post 5 hours ago by paco7533
19 Comments - Last post 11 hours ago by juryman00
2,544 Comments - Last post 1 minute ago by insideAfireball
846 Comments - Last post 7 minutes ago by TricksterImp
240 Comments - Last post 28 minutes ago by RhoninMagus
19 Comments - Last post 1 hour ago by Mikurden
75 Comments - Last post 1 hour ago by vigaristti
16 Comments - Last post 1 hour ago by cheeki7
62 Comments - Last post 1 hour ago by TheMuzo
If you were visiting the site in the past few hours, you likely noticed a temporary IP block and were unable to access the site. This was a bug related to the recent upgrades to our servers. If you were blocked, it was simply in error, and not your fault.
Our site temporarily blocks IP addresses if they're making too many invalid requests. If you view the attached image, you can see we introduced a load balancer today between the user and our web servers. This caused our database to start incorrectly logging the local IP address of our load balancer as the source of invalid requests, instead of the IP address of the user. When the invalid request limit was reached, the IP address of our load balancer, and all incoming traffic was blocked. The site has been updated in the past hour to fix the bug and to accurately resolve user IP addresses with our new load balancer in place, so everything should be working as expected once again. Sorry about the brief downtime.
Comment has been collapsed.