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/ Fri, 19 Dec 2025 16:13:59 +0000 https://status.netgoat.xyz/#f58c28df72ab38bb0ebf6d8dc91740a185f84a46f65d09741bda66ae1c680d58 MongoDB Instance recovered https://status.netgoat.xyz/ Fri, 19 Dec 2025 16:13:59 +0000 https://status.netgoat.xyz/#f58c28df72ab38bb0ebf6d8dc91740a185f84a46f65d09741bda66ae1c680d58 MongoDB Instance recovered https://status.netgoat.xyz/ Fri, 19 Dec 2025 16:12:02 +0000 https://status.netgoat.xyz/#f58c28df72ab38bb0ebf6d8dc91740a185f84a46f65d09741bda66ae1c680d58 MongoDB Instance went down https://status.netgoat.xyz/ Fri, 19 Dec 2025 16:12:02 +0000 https://status.netgoat.xyz/#f58c28df72ab38bb0ebf6d8dc91740a185f84a46f65d09741bda66ae1c680d58 MongoDB Instance went down https://status.netgoat.xyz/ Fri, 19 Dec 2025 05:08:28 +0000 https://status.netgoat.xyz/#d9a2616ad9a87da1615fa3e272f43a058bc6b1ee81666e51408df2ce5fbde479 MongoDB Instance recovered https://status.netgoat.xyz/ Fri, 19 Dec 2025 05:08:28 +0000 https://status.netgoat.xyz/#d9a2616ad9a87da1615fa3e272f43a058bc6b1ee81666e51408df2ce5fbde479 MongoDB Instance recovered https://status.netgoat.xyz/ Fri, 19 Dec 2025 05:02:50 +0000 https://status.netgoat.xyz/#d9a2616ad9a87da1615fa3e272f43a058bc6b1ee81666e51408df2ce5fbde479 MongoDB Instance went down https://status.netgoat.xyz/ Fri, 19 Dec 2025 05:02:50 +0000 https://status.netgoat.xyz/#d9a2616ad9a87da1615fa3e272f43a058bc6b1ee81666e51408df2ce5fbde479 MongoDB Instance went down https://status.netgoat.xyz/ Mon, 15 Dec 2025 10:28:57 +0000 https://status.netgoat.xyz/#38b413de6420f3486eadb067cc0f4def53a7b801f6a7bf3d212d4f8b573c3de1 MongoDB Instance recovered https://status.netgoat.xyz/ Mon, 15 Dec 2025 10:28:57 +0000 https://status.netgoat.xyz/#38b413de6420f3486eadb067cc0f4def53a7b801f6a7bf3d212d4f8b573c3de1 MongoDB Instance recovered https://status.netgoat.xyz/ Mon, 15 Dec 2025 10:26:55 +0000 https://status.netgoat.xyz/#38b413de6420f3486eadb067cc0f4def53a7b801f6a7bf3d212d4f8b573c3de1 MongoDB Instance went down https://status.netgoat.xyz/ Mon, 15 Dec 2025 10:26:55 +0000 https://status.netgoat.xyz/#38b413de6420f3486eadb067cc0f4def53a7b801f6a7bf3d212d4f8b573c3de1 MongoDB Instance went down https://status.netgoat.xyz/ Fri, 05 Dec 2025 18:26:19 +0000 https://status.netgoat.xyz/#de9714b8dc1c935deed038f83196adaa0cbfeceeed2d89f74a973391a7c5adb2 MongoDB Instance recovered https://status.netgoat.xyz/ Fri, 05 Dec 2025 18:26:19 +0000 https://status.netgoat.xyz/#de9714b8dc1c935deed038f83196adaa0cbfeceeed2d89f74a973391a7c5adb2 MongoDB Instance recovered https://status.netgoat.xyz/ Fri, 05 Dec 2025 18:24:15 +0000 https://status.netgoat.xyz/#de9714b8dc1c935deed038f83196adaa0cbfeceeed2d89f74a973391a7c5adb2 MongoDB Instance went down https://status.netgoat.xyz/ Fri, 05 Dec 2025 18:24:15 +0000 https://status.netgoat.xyz/#de9714b8dc1c935deed038f83196adaa0cbfeceeed2d89f74a973391a7c5adb2 MongoDB Instance went down https://status.netgoat.xyz/ Mon, 24 Nov 2025 09:35:29 +0000 https://status.netgoat.xyz/#73cab48abf6ae6c46a18577a6ead55c3c916e67767cf2b57d92a40d35c6c84ed MongoDB Instance recovered https://status.netgoat.xyz/ Mon, 24 Nov 2025 09:35:29 +0000 https://status.netgoat.xyz/#73cab48abf6ae6c46a18577a6ead55c3c916e67767cf2b57d92a40d35c6c84ed MongoDB Instance recovered https://status.netgoat.xyz/ Sat, 22 Nov 2025 19:14:08 +0000 https://status.netgoat.xyz/#73cab48abf6ae6c46a18577a6ead55c3c916e67767cf2b57d92a40d35c6c84ed MongoDB Instance went down https://status.netgoat.xyz/ Sat, 22 Nov 2025 19:14:08 +0000 https://status.netgoat.xyz/#73cab48abf6ae6c46a18577a6ead55c3c916e67767cf2b57d92a40d35c6c84ed MongoDB Instance went down https://status.netgoat.xyz/ Sat, 22 Nov 2025 18:53:14 +0000 https://status.netgoat.xyz/#f3786fcb9a3729dff02a414d58a25a124ba72fa57e3ffa241347c20dd62f249e MongoDB Instance recovered https://status.netgoat.xyz/ Sat, 22 Nov 2025 18:53:14 +0000 https://status.netgoat.xyz/#f3786fcb9a3729dff02a414d58a25a124ba72fa57e3ffa241347c20dd62f249e MongoDB Instance recovered https://status.netgoat.xyz/ Sat, 22 Nov 2025 18:47:34 +0000 https://status.netgoat.xyz/#f3786fcb9a3729dff02a414d58a25a124ba72fa57e3ffa241347c20dd62f249e MongoDB Instance went down https://status.netgoat.xyz/ Sat, 22 Nov 2025 18:47:34 +0000 https://status.netgoat.xyz/#f3786fcb9a3729dff02a414d58a25a124ba72fa57e3ffa241347c20dd62f249e MongoDB Instance went down https://status.netgoat.xyz/ Sat, 22 Nov 2025 17:08:17 +0000 https://status.netgoat.xyz/#ab1606a50766f3e9d6a7569e706892e19a21cb31316d78b84a01ff381f991b15 MongoDB Instance recovered https://status.netgoat.xyz/ Sat, 22 Nov 2025 17:08:17 +0000 https://status.netgoat.xyz/#ab1606a50766f3e9d6a7569e706892e19a21cb31316d78b84a01ff381f991b15 MongoDB Instance recovered https://status.netgoat.xyz/ Sat, 22 Nov 2025 17:00:08 +0000 https://status.netgoat.xyz/#ab1606a50766f3e9d6a7569e706892e19a21cb31316d78b84a01ff381f991b15 MongoDB Instance went down https://status.netgoat.xyz/ Sat, 22 Nov 2025 17:00:08 +0000 https://status.netgoat.xyz/#ab1606a50766f3e9d6a7569e706892e19a21cb31316d78b84a01ff381f991b15 MongoDB Instance went down https://status.netgoat.xyz/ Sat, 22 Nov 2025 16:11:25 +0000 https://status.netgoat.xyz/#8320001e44331bd9745ffddcf7f1934f562b487b181275beee09173a7ca24914 MongoDB Instance recovered https://status.netgoat.xyz/ Sat, 22 Nov 2025 16:11:25 +0000 https://status.netgoat.xyz/#8320001e44331bd9745ffddcf7f1934f562b487b181275beee09173a7ca24914 MongoDB Instance recovered https://status.netgoat.xyz/ Sat, 22 Nov 2025 15:54:09 +0000 https://status.netgoat.xyz/#8320001e44331bd9745ffddcf7f1934f562b487b181275beee09173a7ca24914 MongoDB Instance went down https://status.netgoat.xyz/ Sat, 22 Nov 2025 15:54:09 +0000 https://status.netgoat.xyz/#8320001e44331bd9745ffddcf7f1934f562b487b181275beee09173a7ca24914 MongoDB Instance went down https://status.netgoat.xyz/ Mon, 17 Nov 2025 10:48:19 +0000 https://status.netgoat.xyz/#85adb24dd2cb459f220ac125e6c51771483803cdcfef945f3fe640c959d4346a central.netgoat.xyz went down https://status.netgoat.xyz/ Mon, 17 Nov 2025 10:46:57 +0000 https://status.netgoat.xyz/#c2452cb4d91dc21f7742748204842cf8e3e9537466437b87b36962cbe0a36c9b Coder Instance went down https://status.netgoat.xyz/ Mon, 17 Nov 2025 10:46:08 +0000 https://status.netgoat.xyz/#2d3db6df5b35e4f625d48ef2caca27efe2a1c48d315e48b7b44133a38ca1eb72 gitea.netgoat.xyz went down https://status.netgoat.xyz/ Sat, 15 Nov 2025 21:03:32 +0000 https://status.netgoat.xyz/#05d06fe9a239ca2cd1f7575fdabc3a55dcdb1d74a66f71ff77424b4b1253aebb MongoDB Instance recovered https://status.netgoat.xyz/ Sat, 15 Nov 2025 21:03:32 +0000 https://status.netgoat.xyz/#05d06fe9a239ca2cd1f7575fdabc3a55dcdb1d74a66f71ff77424b4b1253aebb MongoDB Instance recovered https://status.netgoat.xyz/ Sat, 15 Nov 2025 21:01:25 +0000 https://status.netgoat.xyz/#05d06fe9a239ca2cd1f7575fdabc3a55dcdb1d74a66f71ff77424b4b1253aebb MongoDB Instance went down https://status.netgoat.xyz/ Sat, 15 Nov 2025 21:01:25 +0000 https://status.netgoat.xyz/#05d06fe9a239ca2cd1f7575fdabc3a55dcdb1d74a66f71ff77424b4b1253aebb MongoDB Instance went down https://status.netgoat.xyz/ Thu, 13 Nov 2025 16:21:01 +0000 https://status.netgoat.xyz/#880d17204c68e447a7a5daf5f86a2665b78b4a042d2628755eb1207c20d7b15a logdb.netgoat.xyz went down https://status.netgoat.xyz/ Thu, 13 Nov 2025 02:11:09 +0000 https://status.netgoat.xyz/#fa4001e6a0bdc73d0a72fc6940fa61b4004ce6db00db20685530d324886c68e4 MongoDB Instance recovered https://status.netgoat.xyz/ Thu, 13 Nov 2025 02:11:09 +0000 https://status.netgoat.xyz/#fa4001e6a0bdc73d0a72fc6940fa61b4004ce6db00db20685530d324886c68e4 MongoDB Instance recovered https://status.netgoat.xyz/ Thu, 13 Nov 2025 02:09:02 +0000 https://status.netgoat.xyz/#fa4001e6a0bdc73d0a72fc6940fa61b4004ce6db00db20685530d324886c68e4 MongoDB Instance went down https://status.netgoat.xyz/ Thu, 13 Nov 2025 02:09:02 +0000 https://status.netgoat.xyz/#fa4001e6a0bdc73d0a72fc6940fa61b4004ce6db00db20685530d324886c68e4 MongoDB Instance went down https://status.netgoat.xyz/ Wed, 05 Nov 2025 14:35:53 +0000 https://status.netgoat.xyz/#e92ff23e3af48a4b008bfec8e1ecb04fa9a2ba38db2c17dd752566ca4f0782e1 MongoDB Instance recovered https://status.netgoat.xyz/ Wed, 05 Nov 2025 14:35:53 +0000 https://status.netgoat.xyz/#e92ff23e3af48a4b008bfec8e1ecb04fa9a2ba38db2c17dd752566ca4f0782e1 MongoDB Instance recovered https://status.netgoat.xyz/ Wed, 05 Nov 2025 12:53:36 +0000 https://status.netgoat.xyz/#e92ff23e3af48a4b008bfec8e1ecb04fa9a2ba38db2c17dd752566ca4f0782e1 MongoDB Instance went down https://status.netgoat.xyz/ Wed, 05 Nov 2025 12:53:36 +0000 https://status.netgoat.xyz/#e92ff23e3af48a4b008bfec8e1ecb04fa9a2ba38db2c17dd752566ca4f0782e1 MongoDB Instance went down https://status.netgoat.xyz/ Fri, 31 Oct 2025 06:01:58 +0000 https://status.netgoat.xyz/#51cb1e948b97e9eeaa7bb51d1b0cb005a7ae4f61c44b07e9306a13202663305e central.netgoat.xyz recovered https://status.netgoat.xyz/ Fri, 31 Oct 2025 06:01:41 +0000 https://status.netgoat.xyz/#55cb50a040c9fa4c4ba1e61c0df936c3ab9e0be241b76d46d5ef06a14acdff6f MongoDB Instance recovered https://status.netgoat.xyz/ Fri, 31 Oct 2025 06:01:41 +0000 https://status.netgoat.xyz/#55cb50a040c9fa4c4ba1e61c0df936c3ab9e0be241b76d46d5ef06a14acdff6f MongoDB Instance recovered https://status.netgoat.xyz/ Thu, 30 Oct 2025 22:25:55 +0000 https://status.netgoat.xyz/#51cb1e948b97e9eeaa7bb51d1b0cb005a7ae4f61c44b07e9306a13202663305e central.netgoat.xyz went down https://status.netgoat.xyz/ Thu, 30 Oct 2025 12:49:41 +0000 https://status.netgoat.xyz/#55cb50a040c9fa4c4ba1e61c0df936c3ab9e0be241b76d46d5ef06a14acdff6f MongoDB Instance went down https://status.netgoat.xyz/ Thu, 30 Oct 2025 12:49:41 +0000 https://status.netgoat.xyz/#55cb50a040c9fa4c4ba1e61c0df936c3ab9e0be241b76d46d5ef06a14acdff6f MongoDB Instance went down https://status.netgoat.xyz/ Wed, 29 Oct 2025 10:39:54 +0000 https://status.netgoat.xyz/#e5d7d44416848698ec5756bb40867d0e18d35e5a4de11a3706b98a872c8d0ab1 MongoDB Instance recovered https://status.netgoat.xyz/ Wed, 29 Oct 2025 10:39:54 +0000 https://status.netgoat.xyz/#e5d7d44416848698ec5756bb40867d0e18d35e5a4de11a3706b98a872c8d0ab1 MongoDB Instance recovered https://status.netgoat.xyz/ Tue, 28 Oct 2025 16:06:13 +0000 https://status.netgoat.xyz/#e5d7d44416848698ec5756bb40867d0e18d35e5a4de11a3706b98a872c8d0ab1 MongoDB Instance went down https://status.netgoat.xyz/ Tue, 28 Oct 2025 16:06:13 +0000 https://status.netgoat.xyz/#e5d7d44416848698ec5756bb40867d0e18d35e5a4de11a3706b98a872c8d0ab1 MongoDB Instance went down https://status.netgoat.xyz/ Tue, 28 Oct 2025 09:54:07 +0000 https://status.netgoat.xyz/#7cb3debac2e2f639e6ef374657dc0e15cbcc21ba4b0e88e683ed1ec9d6717708 MongoDB Instance recovered https://status.netgoat.xyz/ Tue, 28 Oct 2025 09:54:07 +0000 https://status.netgoat.xyz/#7cb3debac2e2f639e6ef374657dc0e15cbcc21ba4b0e88e683ed1ec9d6717708 MongoDB Instance recovered https://status.netgoat.xyz/ Mon, 27 Oct 2025 19:44:31 +0000 https://status.netgoat.xyz/#7cb3debac2e2f639e6ef374657dc0e15cbcc21ba4b0e88e683ed1ec9d6717708 MongoDB Instance went down https://status.netgoat.xyz/ Mon, 27 Oct 2025 19:44:31 +0000 https://status.netgoat.xyz/#7cb3debac2e2f639e6ef374657dc0e15cbcc21ba4b0e88e683ed1ec9d6717708 MongoDB Instance went down https://status.netgoat.xyz/ Mon, 27 Oct 2025 06:02:22 +0000 https://status.netgoat.xyz/#b6d2df652d2b925824f0995cbca54ac53fcf747f5f2af8d7662315e845c97c5f MongoDB Instance recovered https://status.netgoat.xyz/ Mon, 27 Oct 2025 06:02:22 +0000 https://status.netgoat.xyz/#b6d2df652d2b925824f0995cbca54ac53fcf747f5f2af8d7662315e845c97c5f MongoDB Instance recovered https://status.netgoat.xyz/ Sun, 26 Oct 2025 15:20:23 +0000 https://status.netgoat.xyz/#b6d2df652d2b925824f0995cbca54ac53fcf747f5f2af8d7662315e845c97c5f MongoDB Instance went down https://status.netgoat.xyz/ Sun, 26 Oct 2025 15:20:23 +0000 https://status.netgoat.xyz/#b6d2df652d2b925824f0995cbca54ac53fcf747f5f2af8d7662315e845c97c5f MongoDB Instance went down https://status.netgoat.xyz/ Sat, 25 Oct 2025 16:02:07 +0000 https://status.netgoat.xyz/#ac8c4135f59483700d702da1c4adb2b4f3cd1a160875a7ebd7b4885d77239543 logdb.netgoat.xyz recovered https://status.netgoat.xyz/ Sat, 25 Oct 2025 16:00:09 +0000 https://status.netgoat.xyz/#ac8c4135f59483700d702da1c4adb2b4f3cd1a160875a7ebd7b4885d77239543 logdb.netgoat.xyz 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 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 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 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 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/ Tue, 21 Oct 2025 17:40:58 +0000 https://status.netgoat.xyz/#013a65c0a18efd8318ebd1a705721dffe6fc8246dd96297b39ff791135a4db4a logdb.netgoat.xyz recovered https://status.netgoat.xyz/ Tue, 21 Oct 2025 17:38:07 +0000 https://status.netgoat.xyz/#6cabea58b45b37d2598590e9ba5d6f925ebb673c133364aec1355a3ecc60d19f MongoDB Instance recovered https://status.netgoat.xyz/ Tue, 21 Oct 2025 17:38:07 +0000 https://status.netgoat.xyz/#6cabea58b45b37d2598590e9ba5d6f925ebb673c133364aec1355a3ecc60d19f MongoDB Instance recovered https://status.netgoat.xyz/ Tue, 21 Oct 2025 17:37:59 +0000 https://status.netgoat.xyz/#013a65c0a18efd8318ebd1a705721dffe6fc8246dd96297b39ff791135a4db4a logdb.netgoat.xyz went down 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: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: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#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: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: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 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 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 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 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 https://status.netgoat.xyz/ Tue, 21 Oct 2025 16:50:07 +0000 https://status.netgoat.xyz/#6cabea58b45b37d2598590e9ba5d6f925ebb673c133364aec1355a3ecc60d19f MongoDB Instance went down https://status.netgoat.xyz/ Tue, 21 Oct 2025 16:50:07 +0000 https://status.netgoat.xyz/#6cabea58b45b37d2598590e9ba5d6f925ebb673c133364aec1355a3ecc60d19f MongoDB Instance went down https://status.netgoat.xyz/ Mon, 20 Oct 2025 11:08:24 +0000 https://status.netgoat.xyz/#487c95f5c8f16f0c0d1d2bb46caa2484f5c2d5d95ea1acf15d6c362c49550d11 logdb.netgoat.xyz recovered https://status.netgoat.xyz/ Mon, 20 Oct 2025 11:06:27 +0000 https://status.netgoat.xyz/#487c95f5c8f16f0c0d1d2bb46caa2484f5c2d5d95ea1acf15d6c362c49550d11 logdb.netgoat.xyz went down