This is intentional for the moment, we have an issue with the leagues population causing an inordinate amount of load on our SQL servers which I have yet to find time to investigate.
I just turned it on for Stack Overflow specifically, it's the SE 2.0 sites causing the SQL issue...Stack Overflow is fine.
We've been a little busy wit the failover to our redundant Datacenter the past 2 days getting the last bits of the network stood up (that you guys don't see). Tomorrow I'll try and track down the cause of the crazy reads on the league queries and deploy a fix. Apologies this has lingered a few days, but we have to triage a bit at the moment due to Sandy moving up our time tables drastically.