@raymondcamden @rem @Netlify Not at all, Raymond. There was certainly an issue. It looks like the Infrastructure and Supports teams sprang into action to resolve the issue quickly, but we still aim to minimise anything like this. Thanks for reporting.
https://twitter.com/netlifystatus/status/958738412000894976