Well, I would, if the issue hadn’t self-corrected again today.

It’s pretty much just what /u/irelephant posted here. There’s very little actual info present, just an HTTP status of 500 with a boilerplate nginx response page.

When it inevitably starts happening again, I’ll be sure and take some captures of the full request/response details.