During the incident window, all bans, kicks, mutes, and warnings would be processed, however, the modlog would not properly create.

This incident was caused by several factors, a Discord incident which seemed to be the root cause as well as problem at our database layer causing modlog creation queries to fail. We have resolved the database error and are working to ensure it does not happen again.

Our response to this issue was delayed due to our logs being flooded with Discord’s API returning HTTP 503 (service unavailable). We are implementing policy changes to ensure we do not have delayed responses to issues like this again.

All impacted customers can reach out to our support team if they require we manually add modlogs to their server’s database.