# Yet Another Fun One **URL:** \ **Category:** Product Support\ **Created:** [September 11, 2022, 3:21am UTC](https://meta.discourse.org/t/yet-another-fun-one/238664 "2022-09-11T03:21:06Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![fuse](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fuse/32/221005_2.png) [@fuse](https://meta.discourse.org/u/fuse)\ **Post date:** [September 11, 2022, 3:21am UTC](https://meta.discourse.org/t/yet-another-fun-one/238664/1 "2022-09-11T03:21:06Z")
Opening a fun can of worms. Thanks in advance. I received a notification 8:47pm local time that my Discourse site was not reachable. My server was getting hammered (load average was running anywhere from 8 on the low side to 15 on the high side), discourse was running, and there was nothing I could easily discern as an issue. I ran discourse doctor, not problem. I ended up having to reboot the compute instance, which did not solve the problem. Ultimately I stopped the instance for over 30 minutes before restarting. Problem gone. Keep in mind my discourse site is really, really small - about 20 active users. I can’t prove there was some sort of DDoS activity, the symptoms sure line up with that possibility. Below is a log snippet. I am sure folks want to keep known bugs that are security risks obfuscated. Do the logs below match any known indicators of compromise? Any and all thoughts appreciated. Thank you! ![discourse 20220910](https://global.discourse-cdn.com/meta/original/4X/f/2/1/f21fa67a059ead5774904fd2de75016a95b49d48.jpeg) --- _[View the full topic](https://meta.discourse.org/t/yet-another-fun-one/238664)._