Looks like the underlying cause was an error from the Zendesk API. Does this happen every time you go to the page?
Checked this morning and it seems to have resolved itself, so I guess the Zendesk API is now behaving itself.
