We are now seeing service restored to normal usage. We believe this was a spike in content processing.

We believe the issue is caused by a spike in disk read delays on our database. We're working to identify the root cause.

We are seeing intermittent outages of the Mastodon website resulting in 502 errors being returned to users. Support are investigating.