Server #bb833b5b gets stopped by “abuse detection” on every start

“Abuse detection” usually means the free server monitor saw average CPU above roughly 15% for a sustained period —not a single spike. The check can run periodically, which may explain the consistent timing. A stop for this reason doesn’t by itself mean the server was flagged for a policy review. 1. Check Client → Notifications for the stop reason. 2. Avoid running on every start if possible; install dependencies beforehand, then start the app and watch the CPU chart. 3. Make sure there’s only one Discord bot in the server. Check for repeated installs, restart loops, or other CPU heavy startup tasks. If it still stops while genuinely idle, share the notification text and console output from Start until it stops, with secrets removed. Why was my server stopped?

bb833b5b is still stopped even when idle. I removed npm install from startup (renamed package.json) and only one bot process runs (selfbot disabled). Console shows my processes at under 5% CPU at startup and about 0% idle (I log CPU every 30s), yet stops always land at second :55 or :56 of a minute. Could staff check what the monitor measured for this server?

Your 30 second log samples can miss short CPU spikes, and may not reflect the monitor’s averaging window or all processes in the container. The consistent stop time suggests a periodic check, but doesn’t tell us what it measured. For a server specific review, use Contact us on Discord from the server page and include the exact stop notification, approximate start/stop times, node name, and support tag. Don’t share tokens or other secrets.