Yeah, I was deploying to Heroku when this roots error occurred. This screwed up the deploy (as it crashed in the middle) and just 500'ed on every page load. And

Yeah, I was deploying to Heroku when this roots error occurred. This screwed up the deploy (as it crashed in the middle) and just 500'ed on every page load. And meant every DNS request in my deploy chain that relied on *.notable.ac resolving ended up caching negative results. Luckily it's back up now :)