When we turned down the G+ API we injected synthetic errors in increasing fractions of requests a few days ahead of the actual turndown to alert users. I'm not sure if its the same case here, but it's possible that's what's happening.