It is.
The rate of failures seems to have increased BUT we're also seeing a high incidence of busy errors (below).
When I'd checked our server logs previously, it was apparent that the owner and viewer headers were being defined properly - but the FetchPersonRequest was failing.
Server is too busy
==========================
THE X's below aren't in the original.
| Accept |
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 |
| Accept-Encoding |
gzip,deflate |
| Host |
xxxxx.com |
| Referer |
http://api.msappspace.com |
| User-Agent |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14 |
| X-pRequest |
40876056 |
| X-Opensocial-Owner-Id |
XXXXXXXXX |
| X-Opensocial-Viewer-Id |
XXXXXXXXX |
oops - actually the X's in X-Opensocial-Viewer-Id and X-Opensocial-Owner-Id and X-pRequest ARE in the original - the lowercase x's are mine.