This incident has been resolved.

Dashboard access appears to be recovering.
We are seeing the dashboard and Discord authentication working again for some users. We are monitoring the situation to confirm full recovery.
If you still cannot access your servers, please wait a few minutes and try again.

Root cause identified.
Discord has temporarily restricted our API access. This is an automatic, time-limited measure applied on Discord's side after our dashboard backend sent too many rejected requests in a short window. It is not a Discord outage, a misconfiguration, or a compromised account, and no data has been lost or exposed.
We have now stopped all outgoing calls to the Discord API from our infrastructure, and a fix has been deployed. This step is necessary: every request sent while the restriction is active extends its duration, which is why the incident lasted longer than it should have.
Estimated restoration: 13 September 2026, 11:46 CEST — <t:1789292809:R>
The restriction lifts automatically. It cannot be shortened, and any attempt to do so would only push it back further.
Still working: every bot feature inside Discord — moderation, tickets, logs, automod, notifications. Only the web dashboard and dashboard login are affected.
What you need to do: nothing. Access will be restored on its own. If your servers do not appear immediately afterwards, log out and log back in.
The deployed fix also means a future rate limit will degrade the dashboard instead of taking it offline.

The Moddy dashboard is currently unavailable.
Users are unable to log in to their accounts, and users who were already logged in can no longer access their servers.
The issue appears to be related to temporary rate limits encountered when communicating with the Discord API. We are currently investigating the situation.
Discord bot features remain available.