I'm glad to hear this issue was transient. Thank you nevertheless for bringing this up.
If this error returns, I would suggest filing a new defect report on the
public issue tracker, linking back to this thread for context and attaching a
HAR capture of Developers Console network requests to possibly give insight to the source of the error.