Incidents reported on status page for Netgoat https://status.netgoat.xyz/ https://d1lppblt9t2x15.cloudfront.net/logos/2d9cef7729f9400f3c1b23e2313bdfd9.png https://status.netgoat.xyz/ en https://status.netgoat.xyz/ Sat, 07 Feb 2026 02:17:17 +0000 https://status.netgoat.xyz/#fbff69e625dc7dcf8600c42912c7cfe22733681f8de352c117188d00a559c77e Main Homepage went down https://status.netgoat.xyz/incident/748521 Wed, 22 Oct 2025 05:00:00 -0000 https://status.netgoat.xyz/incident/748521#25fb69007c29f6517030519448462555b53c3647087ded594e8e26317fcff52f We are investigating at this moment, but it seems that the MongoDB server is online on the panel? https://status.netgoat.xyz/incident/748521 Tue, 21 Oct 2025 17:10:00 -0000 https://status.netgoat.xyz/incident/748521#63b0cf4e34e94c0b19d28dd49beb9d0bb908667083fe933a355181a342f13cd1 microservice's restarted and should be functional https://status.netgoat.xyz/incident/748521 Tue, 21 Oct 2025 17:10:00 -0000 https://status.netgoat.xyz/incident/748521#f6b76b5284b6eaa3c67552cbfdbf3b2e088c5f2ecc173e8fa72cb02eeb525cfb **Issue:** MongoDB in the Pterodactyl container crashed after long uptime. Logs indicated a fatal error in full-time diagnostic data capture (FTDC) when writing to `/home/container/mongodb/diagnostic.data/metrics.interim.temp`, causing the process to terminate while the container still reported "online". **Cause:** FTDC attempted to write diagnostic data to a filesystem that doesn’t fully support it (common in containerized environments). Lack of root access prevented proper recovery, triggering the crash. **Resolution:** - Disabled FTDC in `mongod.conf`: ```yaml setParameter: diagnosticDataCollectionEnabled: false` ``` https://status.netgoat.xyz/incident/748521 Tue, 21 Oct 2025 17:07:00 -0000 https://status.netgoat.xyz/incident/748521#b51e68031f206589c2ff7bc64a9e12aced94353c3e35d1b117063dc8cf9f39c1 MongoDB is unavailiable at the moment, blog's may fail to load