Apologies for some of the recent “503” errors in Micro.blog. We’ve made some configuration tweaks today that should reduce or eliminate the problem.