Incidents reported on status page for SupItsTom https://status.supitstom.net/ https://d1lppblt9t2x15.cloudfront.net/logos/d0582db350c7c0e079e5f0c7d8b348a0.png https://status.supitstom.net/ en https://status.supitstom.net/ Sun, 14 Dec 2025 15:25:08 +0000 https://status.supitstom.net/#ea44f2a90c05d995cdf5798eee5d4eb8215e9923fb3da19af2c427c2380249cd Teapot Live recovered https://status.supitstom.net/ Sun, 14 Dec 2025 15:22:02 +0000 https://status.supitstom.net/#ea44f2a90c05d995cdf5798eee5d4eb8215e9923fb3da19af2c427c2380249cd Teapot Live went down https://status.supitstom.net/ Wed, 05 Nov 2025 17:59:55 +0000 https://status.supitstom.net/#c7da8ede36e9b4a61c1b678524f878755011a50bf11a057e4509fa94f65d0fbd Teapot Live recovered https://status.supitstom.net/ Tue, 04 Nov 2025 16:15:22 +0000 https://status.supitstom.net/#c7da8ede36e9b4a61c1b678524f878755011a50bf11a057e4509fa94f65d0fbd Teapot Live went down https://status.supitstom.net/ Sun, 19 Oct 2025 02:30:45 +0000 https://status.supitstom.net/#55ecdd98af9389ab1d0c39fb3677712008b9271d944ae4b781b85c21da04da95 Teapot Live recovered https://status.supitstom.net/ Sun, 19 Oct 2025 02:27:43 +0000 https://status.supitstom.net/#55ecdd98af9389ab1d0c39fb3677712008b9271d944ae4b781b85c21da04da95 Teapot Live went down https://status.supitstom.net/ Sun, 19 Oct 2025 01:32:28 +0000 https://status.supitstom.net/#3ecddd396c250af769a599a2415452b09df98c5c7cd943a1e88fcb0577ee4d44 Teapot Live recovered https://status.supitstom.net/ Sun, 19 Oct 2025 01:29:28 +0000 https://status.supitstom.net/#3ecddd396c250af769a599a2415452b09df98c5c7cd943a1e88fcb0577ee4d44 Teapot Live went down https://status.supitstom.net/ Tue, 07 Oct 2025 03:44:33 +0000 https://status.supitstom.net/#fb3e69444ffe41c2ed8fbdbec91e49f9cb2d3a7f8b89eada318bf25af2e98d65 Teapot Live recovered https://status.supitstom.net/ Tue, 07 Oct 2025 03:41:35 +0000 https://status.supitstom.net/#fb3e69444ffe41c2ed8fbdbec91e49f9cb2d3a7f8b89eada318bf25af2e98d65 Teapot Live went down https://status.supitstom.net/ Tue, 07 Oct 2025 03:38:32 +0000 https://status.supitstom.net/#f4cf974fee00988f8d75bbdb33ef752bd0ced1dfc33782e315e97af446a5d4a8 Teapot Live recovered https://status.supitstom.net/ Tue, 07 Oct 2025 03:35:33 +0000 https://status.supitstom.net/#f4cf974fee00988f8d75bbdb33ef752bd0ced1dfc33782e315e97af446a5d4a8 Teapot Live went down https://status.supitstom.net/ Sun, 05 Oct 2025 21:52:14 +0000 https://status.supitstom.net/#5841acc1657b63317e3241610b5e8392a37f1b95db9d67bfda333920d0fc2238 Teapot Live recovered https://status.supitstom.net/ Sun, 05 Oct 2025 21:46:13 +0000 https://status.supitstom.net/#5841acc1657b63317e3241610b5e8392a37f1b95db9d67bfda333920d0fc2238 Teapot Live went down https://status.supitstom.net/ Tue, 23 Sep 2025 15:04:46 +0000 https://status.supitstom.net/#08539a80729ef36b8e594a6c84d21f6c471949adee88751637f4153f5142d2eb Teapot Live recovered https://status.supitstom.net/ Tue, 23 Sep 2025 14:58:48 +0000 https://status.supitstom.net/#08539a80729ef36b8e594a6c84d21f6c471949adee88751637f4153f5142d2eb Teapot Live went down https://status.supitstom.net/ Mon, 22 Sep 2025 11:17:17 +0000 https://status.supitstom.net/#26f61dc338406078a118426f7d1509b771b3f3867b2be53b86f10d4569cbc1cb Teapot Live recovered https://status.supitstom.net/ Mon, 22 Sep 2025 11:14:17 +0000 https://status.supitstom.net/#26f61dc338406078a118426f7d1509b771b3f3867b2be53b86f10d4569cbc1cb Teapot Live went down https://status.supitstom.net/ Sat, 20 Sep 2025 17:59:24 +0000 https://status.supitstom.net/#1d1337fa99fb058728b8f2813361143e0c0885aec78a9e527223bdfc11458c75 Teapot Live recovered https://status.supitstom.net/ Sat, 20 Sep 2025 17:50:25 +0000 https://status.supitstom.net/#1d1337fa99fb058728b8f2813361143e0c0885aec78a9e527223bdfc11458c75 Teapot Live went down https://status.supitstom.net/incident/543228 Mon, 14 Apr 2025 22:13:00 -0000 https://status.supitstom.net/incident/543228#887590688e62817119f9cf4e18d44655d59cee5fa6c7861ba69e0ac68a4d2d41 # Post Morem --- Teapot Bot was down and would not reply to commands due to a domain name change (TeapotLive.net -> XboxStealth.net). This was causing the api to fail checks and return errors because it was not the right domain. This issue has been fixed. https://status.supitstom.net/incident/543228 Mon, 14 Apr 2025 22:13:00 -0000 https://status.supitstom.net/incident/543228#3970f4e6eaab408d312207bd1a824ed7ff73dd3fe7d9606964a0a13e040f65c1 Hotfix deployed successfully, seems to be working fine now. Will keep monitoring but all systems are currently operational again. Post mortem will be posted soon. https://status.supitstom.net/incident/543228 Mon, 14 Apr 2025 22:11:00 -0000 https://status.supitstom.net/incident/543228#58a6f9d4ba66f3a72f457b7d0e64e55302357edb89812b843308e0cbf62125b5 Issue Idenfified. Hotfix deployed. https://status.supitstom.net/incident/543228 Mon, 14 Apr 2025 22:04:00 -0000 https://status.supitstom.net/incident/543228#dada4a56511122f7a1a8205165776c38bc38aedfcaabe1912e4600aa9df2945c Hotfix still did not work... :( Running API tests now... https://status.supitstom.net/incident/543228 Mon, 14 Apr 2025 22:03:00 -0000 https://status.supitstom.net/incident/543228#c3a54d92429040e18a34aa48bd75cbd8472535d51081d2e5214ce870151f3da4 Deploying hotfix #2. This hotfix uses an older wrangler configuration. Hopefully this one works. https://status.supitstom.net/incident/543228 Mon, 14 Apr 2025 22:02:00 -0000 https://status.supitstom.net/incident/543228#70481d734d5c16ba8f8857e400ec1b092ff858053de1d7473ae364b2359e0bf4 Hotfix did not work, attempting to rollback to a different wrangler config instead... https://status.supitstom.net/incident/543228 Mon, 14 Apr 2025 22:00:00 -0000 https://status.supitstom.net/incident/543228#46b2df933aae7f19f7859087984308123e2efceae55e4e361490011d53a0b20c Hotfix deployed, will be monitoring... --- Uploaded bot-teapot (8.18 sec) Deployed bot-teapot triggers (1.34 sec) Current Version ID: 33e5db6c-1c1a-4a96-a685-ac2b251cfbc0 https://status.supitstom.net/incident/543228 Mon, 14 Apr 2025 21:57:00 -0000 https://status.supitstom.net/incident/543228#acad1771965d3eea2a3f8e5e84e6c43fab2784178cb52647b51b7281c777921a Identified possible cause, creating and deploying a fix when possible. https://status.supitstom.net/incident/543228 Mon, 14 Apr 2025 21:47:00 -0000 https://status.supitstom.net/incident/543228#c6be14f578ec9de91d1ef4f0071bd1e48ee84ad44db72a90931a81845bbdd100 Bot code has been rolled back to a previous deployment. --- Version: 5a147d5e-9a6d-4290-b38a-3e1dc37ad71d Originally deployed: 11 days ago https://status.supitstom.net/incident/543228 Thu, 10 Apr 2025 17:02:00 -0000 https://status.supitstom.net/incident/543228#1ccf9bc49adfb2d3bec69dc569c70024a0c55b007533cab5ec0ee14c56293164 Teapot Discord Bot is currently throwing errors when trying to use commands. A fallback notice has been placed there while the issue is fixed. https://status.supitstom.net/incident/495884 Tue, 14 Jan 2025 22:15:00 -0000 https://status.supitstom.net/incident/495884#e4f428a62f31197fab3266621f8ba9f1350567edf1c59cc8c83ded23e3691061 A fix has been deployed and seems to be working fine now. https://status.supitstom.net/incident/495884 Tue, 14 Jan 2025 22:05:00 -0000 https://status.supitstom.net/incident/495884#9250bd6ae06980faf33f57f9048faa7c630bff09d3d467065789ffd46c5de4f2 Serenity Tool is currently down due to an update on the API. Working to resolve this and will clear this once complete.