Edit: according to this, you're not even logging in to the same service. http://www.google.com/support/accounts/bin/static.py?page=gu... That's... not optimal.
Edit: according to this, you're not even logging in to the same service. http://www.google.com/support/accounts/bin/static.py?page=gu... That's... not optimal.
During this process, users who maintained secondary accounts were encouraged to merge them into their Apps account. I used to have two accounts, one for Apps services on my own domain, and another for things like Reader. I now only have one, my Apps account, because the accounts clashed and had to be merged.
So the doubly galling thing about this Google+ farrago is that a) it proves that the accounts transition did not in fact stop Apps accounts being second-class citizens, but also b) most of us no longer have our secondary accounts, because we merged them at Google's insistence.
Add to this several years of teeth-grinding annoyance at the incompatibilities between Google Apps and the rest of the Google world, and, well, that's why people are complaining. :-)
"Monthly Uptime Percentage" means total number of minutes in a calendar month minus the number of minutes of Downtime suffered in a calendar month, divided by the total number of minutes in a calendar month.
For average month of length 30.4 days (~43776 minutes in total) that means acceptable downtime of 437.something minutes or 7 hours of combined unavailability.
Minding all of that, there is also a term "Google Apps Covered Services", which is explained as:
"Google Apps Covered Services" means the Gmail, Google Calendar, Google Talk, Google Docs, Google Groups and Google Sites components of the Service. This does not include the Gmail Labs functionality, Google Apps - Postini Services, Gmail Voice or Video Chat components of the Service.
So, legally speaking, there is no uptime guarantee for Google+.
You're off by one power-of-10: 43776*(100%-99.9%) = 43.8 minutes of acceptable downtime.