The issue was caused by a short upstream networking issue.
We are currently investigating this issue.
13:15 UTC - 10 January 2019