Incidents reported on status page for proxs https://status.proxs.us/ en https://status.proxs.us/ Sun, 08 Feb 2026 20:46:53 +0000 https://status.proxs.us/#8e69b629bdd011564a0530242e19a5eaa095e8d07dc684605bc83bafcdcdaf09 proxs.us recovered https://status.proxs.us/ Sat, 07 Feb 2026 06:50:10 +0000 https://status.proxs.us/#8e69b629bdd011564a0530242e19a5eaa095e8d07dc684605bc83bafcdcdaf09 proxs.us went down https://status.proxs.us/ Sat, 07 Feb 2026 06:32:19 +0000 https://status.proxs.us/#a3256e1310cff4a4259354fdb4caa93e049849a4f207d6fe4149069d1d97bce7 proxs.us recovered https://status.proxs.us/ Sat, 07 Feb 2026 06:29:16 +0000 https://status.proxs.us/#a3256e1310cff4a4259354fdb4caa93e049849a4f207d6fe4149069d1d97bce7 proxs.us went down https://status.proxs.us/ Sat, 07 Feb 2026 06:07:51 +0000 https://status.proxs.us/#01a4acdc28bd5b2e4ea7d07cabafde58d7335f50ef68550f33640a3a288d3282 proxs.us recovered https://status.proxs.us/ Sat, 07 Feb 2026 05:31:54 +0000 https://status.proxs.us/#01a4acdc28bd5b2e4ea7d07cabafde58d7335f50ef68550f33640a3a288d3282 proxs.us went down https://status.proxs.us/ Sat, 07 Feb 2026 04:04:57 +0000 https://status.proxs.us/#c1e4e5b2dbd24702725a3394ec5ccd83cb130cb34303546a914fc66d8d6896a2 proxs.us recovered https://status.proxs.us/ Sat, 07 Feb 2026 03:59:13 +0000 https://status.proxs.us/#c1e4e5b2dbd24702725a3394ec5ccd83cb130cb34303546a914fc66d8d6896a2 proxs.us went down https://status.proxs.us/ Sat, 07 Feb 2026 02:37:54 +0000 https://status.proxs.us/#3888c4b4ca3afc0905ffa1dfc7c3048e9035d112be5dee4b82018963163d9ed5 proxs.us recovered https://status.proxs.us/ Sat, 07 Feb 2026 02:11:09 +0000 https://status.proxs.us/#3888c4b4ca3afc0905ffa1dfc7c3048e9035d112be5dee4b82018963163d9ed5 proxs.us went down https://status.proxs.us/ Sat, 07 Feb 2026 01:49:51 +0000 https://status.proxs.us/#02bc6d9529e2ca3ea1dc1d7719ea2dae2687042d2cd02ec469be617185a0b685 proxs.us recovered https://status.proxs.us/ Sat, 07 Feb 2026 01:46:59 +0000 https://status.proxs.us/#02bc6d9529e2ca3ea1dc1d7719ea2dae2687042d2cd02ec469be617185a0b685 proxs.us went down https://status.proxs.us/ Sat, 07 Feb 2026 01:14:26 +0000 https://status.proxs.us/#2b57cd5229d4cbaed09e202fdc15036f299cab7782fc310e41a52ce1bc1974f7 proxs.us recovered https://status.proxs.us/ Sat, 07 Feb 2026 01:11:14 +0000 https://status.proxs.us/#2b57cd5229d4cbaed09e202fdc15036f299cab7782fc310e41a52ce1bc1974f7 proxs.us went down https://status.proxs.us/ Sat, 07 Feb 2026 00:50:20 +0000 https://status.proxs.us/#d29626613f3045e803fa9b55553bbced9683caff9fffc2e083d0d47a41539c04 proxs.us recovered https://status.proxs.us/ Fri, 06 Feb 2026 18:43:54 +0000 https://status.proxs.us/#d29626613f3045e803fa9b55553bbced9683caff9fffc2e083d0d47a41539c04 proxs.us went down https://status.proxs.us/ Fri, 06 Feb 2026 14:19:52 +0000 https://status.proxs.us/#4e949835192e3af27a18e507b1d8fb5ff0b13c4d6b646cafa0d057ff024485cc proxs.us recovered https://status.proxs.us/ Fri, 06 Feb 2026 14:17:32 +0000 https://status.proxs.us/#4e949835192e3af27a18e507b1d8fb5ff0b13c4d6b646cafa0d057ff024485cc proxs.us went down https://status.proxs.us/incident/721583 Wed, 10 Sep 2025 21:28:00 -0000 https://status.proxs.us/incident/721583#0b242e094b0a30eb3556b3c1b82a7d35eb597fc9ec2b20e25cbf46b342bb04c0 Was fixed around 6AM https://status.proxs.us/incident/721583 Wed, 10 Sep 2025 04:19:00 -0000 https://status.proxs.us/incident/721583#55246511872e71da0f88617c807e69ce4ef0132d9d8080afed98aff5e6b27350 the bloody drive corrupted. i hope to have this patched, cloned, and fixed by morning! https://status.proxs.us/incident/612749 Wed, 02 Jul 2025 13:30:00 -0000 https://status.proxs.us/incident/612749#16a574db2c814f47fcdbbfdac0e117087190ec928d63721b175de7fbddc2af19 Maintenance completed https://status.proxs.us/incident/612749 Wed, 02 Jul 2025 05:30:00 -0000 https://status.proxs.us/incident/612749#fc5f18631b289d8f5115f9892ddd1f3a8a055d7ca16c39d6fe4a78b236401f4b Cooldown, Server Room 2 Hot. Will return normal function at ~8:30 A.M. CDT