'We believe it occurred after launch as a result of the API’s interaction with a subsequent Google+ code change.'

It is very hard to believe that they can't track when exactly the bug was introduced. All code changes are tracked in the source control.