Incidents | KJTDNET Incidents reported on status page for KJTDNET https://status.kjtd.net/ en Router (fermi) recovered https://status.kjtd.net/ Fri, 30 Jan 2026 20:20:10 +0000 https://status.kjtd.net/#576058df39041fc76ea799409cc1ab157b9192679af56ae8ea9b0aca7e3428be Router (fermi) recovered Router (fermi) went down https://status.kjtd.net/ Fri, 30 Jan 2026 20:17:39 +0000 https://status.kjtd.net/#576058df39041fc76ea799409cc1ab157b9192679af56ae8ea9b0aca7e3428be Router (fermi) went down JF (millihertz) recovered https://status.kjtd.net/ Sun, 18 Jan 2026 02:59:57 +0000 https://status.kjtd.net/#1ef69d59df169fdae2d1dc2ea9b1168842c7cda49a7fe8c82158cfd01f2ea8b3 JF (millihertz) recovered JF (millihertz) went down https://status.kjtd.net/ Sun, 18 Jan 2026 02:49:54 +0000 https://status.kjtd.net/#1ef69d59df169fdae2d1dc2ea9b1168842c7cda49a7fe8c82158cfd01f2ea8b3 JF (millihertz) went down JF (millihertz) recovered https://status.kjtd.net/ Thu, 15 Jan 2026 05:12:01 +0000 https://status.kjtd.net/#7897f6edb3554e1371770e08dc7cc1f363518bed86fc32db0df3334a5cf451b9 JF (millihertz) recovered JF (millihertz) went down https://status.kjtd.net/ Thu, 15 Jan 2026 05:10:47 +0000 https://status.kjtd.net/#7897f6edb3554e1371770e08dc7cc1f363518bed86fc32db0df3334a5cf451b9 JF (millihertz) went down JF (millihertz) recovered https://status.kjtd.net/ Thu, 15 Jan 2026 05:02:52 +0000 https://status.kjtd.net/#9a35b4440fda9d63927940c9fe898c0ba391567c23d5f4f96693f0ee072dc867 JF (millihertz) recovered JF (millihertz) went down https://status.kjtd.net/ Thu, 15 Jan 2026 04:50:58 +0000 https://status.kjtd.net/#9a35b4440fda9d63927940c9fe898c0ba391567c23d5f4f96693f0ee072dc867 JF (millihertz) went down JF (millihertz) recovered https://status.kjtd.net/ Thu, 15 Jan 2026 03:53:57 +0000 https://status.kjtd.net/#ddf8a8f7b6b36c7dba2d16d5ea08b7f5a25513f33f72662b167966e3b770ad1d JF (millihertz) recovered JF (millihertz) went down https://status.kjtd.net/ Thu, 15 Jan 2026 03:20:48 +0000 https://status.kjtd.net/#ddf8a8f7b6b36c7dba2d16d5ea08b7f5a25513f33f72662b167966e3b770ad1d JF (millihertz) went down JF (millihertz) recovered https://status.kjtd.net/ Thu, 15 Jan 2026 02:59:58 +0000 https://status.kjtd.net/#3721f1987e3c2c25121512f430508c12cd91f5ebc934ff2c276db4c37834601b JF (millihertz) recovered JF (millihertz) went down https://status.kjtd.net/ Thu, 15 Jan 2026 02:26:58 +0000 https://status.kjtd.net/#3721f1987e3c2c25121512f430508c12cd91f5ebc934ff2c276db4c37834601b JF (millihertz) went down JF (millihertz) recovered https://status.kjtd.net/ Wed, 14 Jan 2026 06:08:58 +0000 https://status.kjtd.net/#276dc863c1a60f9552f8eca0a09cc5c52e24b5e991c3eefb937bf73a64ef6d66 JF (millihertz) recovered JF (millihertz) went down https://status.kjtd.net/ Wed, 14 Jan 2026 06:05:58 +0000 https://status.kjtd.net/#276dc863c1a60f9552f8eca0a09cc5c52e24b5e991c3eefb937bf73a64ef6d66 JF (millihertz) went down Server (brandy) recovered https://status.kjtd.net/ Sun, 28 Dec 2025 03:52:03 +0000 https://status.kjtd.net/#f8bd904f49def4006cf8f6d93dc8d091eb9fab1c4f9c213bc0e184079e9e64e9 Server (brandy) recovered Server (brandy) went down https://status.kjtd.net/ Sun, 28 Dec 2025 03:49:02 +0000 https://status.kjtd.net/#f8bd904f49def4006cf8f6d93dc8d091eb9fab1c4f9c213bc0e184079e9e64e9 Server (brandy) went down Server (brandy) recovered https://status.kjtd.net/ Fri, 19 Dec 2025 23:22:01 +0000 https://status.kjtd.net/#87a4dde4c10cb6ddc98568dceb6914d877b723c0b7f0545edb113cdd789b6724 Server (brandy) recovered Server (brandy) went down https://status.kjtd.net/ Fri, 19 Dec 2025 19:10:24 +0000 https://status.kjtd.net/#87a4dde4c10cb6ddc98568dceb6914d877b723c0b7f0545edb113cdd789b6724 Server (brandy) went down