Both Mastodon.social and Mastodon.cloud seem to be borked.

Admin@Mastodon.cloud said he was moving servers and updating to 1.6.1 so maybe it all went horribly wrong. Admin@Mastodon.social is the main mastodon developer which suggests the problem might be the new 1.6.1 release.

This makes me sad. Even though the Mastodon community doesn't really feel like it's really taken off just yet. We've become used to systems that just work so having two of the major instances just go off line is not good.
Shared publiclyView activity