Incidents reported on status page for BobTheBot https://status.bobthebot.net/ https://d1lppblt9t2x15.cloudfront.net/logos/5355e02f7c3ae4a0d507e7b6b71779d7.png https://status.bobthebot.net/ en https://status.bobthebot.net/ Fri, 20 Feb 2026 18:28:44 +0000 https://status.bobthebot.net/#507feb0e53de505cf0f82f83771bdbdf756c21e20309d6f608050aa11e5595b0 Bob (Bot Service) recovered https://status.bobthebot.net/ Fri, 20 Feb 2026 18:20:05 +0000 https://status.bobthebot.net/#507feb0e53de505cf0f82f83771bdbdf756c21e20309d6f608050aa11e5595b0 Bob (Bot Service) went down https://status.bobthebot.net/ Thu, 19 Feb 2026 14:52:39 +0000 https://status.bobthebot.net/#19850b9387cbc6d025cf9422c670323727068b37056c72a34bc12dfe33f0886f Bob (Bot Service) recovered https://status.bobthebot.net/ Thu, 19 Feb 2026 14:44:11 +0000 https://status.bobthebot.net/#19850b9387cbc6d025cf9422c670323727068b37056c72a34bc12dfe33f0886f Bob (Bot Service) went down https://status.bobthebot.net/incident/827751 Wed, 18 Feb 2026 04:06:00 -0000 https://status.bobthebot.net/incident/827751#34899b5e7f41bfccb7a41807e2d51474a40aec01c872ed53e599cbfd89ad6751 **Date:** Feb 17, 2026 | **⏱ Duration:** 27 mins ### **🧭 Summary** Bob the Bot experienced a brief total service outage followed by a prolonged networking desync. While the bot’s internal functions (Discord Shards/Slash Commands) were manually restored and confirmed operational shortly after the start of the incident, Railway’s edge infrastructure continued to report 502 "Bad Gateway" errors for several minutes due to a persistent routing failure. ### **🛠️ Resolution** Service was restored internally through a recovery of the application process. Although logs confirmed the bot was "Ready" and processing commands at **9:43 PM**, the incident remained open as Railway's proxy failed to route traffic to the container's health-check port. The edge network eventually synchronized, and monitors recovered automatically. ### **🕑 Timeline** - **9:38 PM** – 🚨 **Incident started.** Total service failure detected; global 502 errors across all regions. - **9:43 PM** – 🤖 **Application Restored.** Internal logs confirm Shards 0-2 connected and Slash Commands registered. **Bot functionality fully recovered.** - **9:46 PM** – 🛠️ Incident acknowledged by Zach Goodson. Investigation confirmed a "ghost" networking issue as the bot was functional but the URL remained unreachable. - **10:04 PM** – 📶 **Infrastructure Recovery.** Railway's edge proxy successfully re-linked the public domain to the container. - **10:05 PM** – ✅ **Incident resolved.** **Root Cause:** **Application Interruption & Upstream Desync.** An initial disruption took the bot offline; however, a secondary infrastructure failure occurred where Railway's load balancer failed to recognize the healthy application (`upstreamAddress: ""`) for 21 minutes after the bot had successfully resumed operations and port binding. https://status.bobthebot.net/ Wed, 18 Feb 2026 04:04:39 +0000 https://status.bobthebot.net/#f1a774d3ad1a8280c13d0f60da707c44ed62f016e7915ee02b4c382db591b3b1 Bob (Bot Service) recovered https://status.bobthebot.net/ Wed, 18 Feb 2026 03:38:18 +0000 https://status.bobthebot.net/#f1a774d3ad1a8280c13d0f60da707c44ed62f016e7915ee02b4c382db591b3b1 Bob (Bot Service) went down https://status.bobthebot.net/incident/823566 Wed, 11 Feb 2026 21:16:00 -0000 https://status.bobthebot.net/incident/823566#2608b7ea1c70876f3a8986f51cf50c997aeafa14e9bc865c2cb2db3ab13f48d0 **Date:** Feb 11, 2026 | **⏱ Duration:** ~5 mins ### **🧭 Summary** Bob went offline briefly due to **Railway (cloud provider) infrastructure issues**, resulting in global 502 "Bad Gateway" errors. ### **🛠️ Resolution** A manual redeploy successfully restored service. This resulted in a successful redeployment hours before railway had officially resolved the issue. ### **🕑 Timeline** - **8:56 AM** – 🚨 502 errors detected globally. - **8:58 AM** – 🛠️ Manual redeploy; service restored. - **9:01 AM** – ✅ Incident resolved, but closely monitored. - **12:31 AM** - 🚇 Railway Officially resolved the issue on their end. **Root Cause:** Upstream infrastructure failure (Railway) https://blog.railway.com/p/incident-report-february-11-2026. https://status.bobthebot.net/ Wed, 11 Feb 2026 21:13:44 +0000 https://status.bobthebot.net/#6fc06a88c3210bf57fd27066a71ec3434d9bddf7f07d314eed276cde4a3f87a2 Bob (Bot Service) recovered https://status.bobthebot.net/ Wed, 11 Feb 2026 20:49:42 +0000 https://status.bobthebot.net/#6fc06a88c3210bf57fd27066a71ec3434d9bddf7f07d314eed276cde4a3f87a2 Bob (Bot Service) went down https://status.bobthebot.net/ Wed, 11 Feb 2026 16:28:45 +0000 https://status.bobthebot.net/#4c90ba86de1a578ff1d8604ea563dc8f6f69d7eee63c58b53258fd80513b4154 Bob (Bot Service) recovered https://status.bobthebot.net/ Wed, 11 Feb 2026 15:23:13 +0000 https://status.bobthebot.net/#4c90ba86de1a578ff1d8604ea563dc8f6f69d7eee63c58b53258fd80513b4154 Bob (Bot Service) went down https://status.bobthebot.net/ Wed, 11 Feb 2026 15:13:48 +0000 https://status.bobthebot.net/#91a3abd9239e33e0f391ac1dbbacacfc48b0004b523f4b92e26f96083e4b7610 Bob (Bot Service) recovered https://status.bobthebot.net/ Wed, 11 Feb 2026 15:10:52 +0000 https://status.bobthebot.net/#91a3abd9239e33e0f391ac1dbbacacfc48b0004b523f4b92e26f96083e4b7610 Bob (Bot Service) went down https://status.bobthebot.net/ Wed, 11 Feb 2026 14:58:38 +0000 https://status.bobthebot.net/#512c9e435aad439359bbb9a1d973a18a9377f9c24394205858569113e3f6109a Bob (Bot Service) recovered https://status.bobthebot.net/ Wed, 11 Feb 2026 14:56:10 +0000 https://status.bobthebot.net/#512c9e435aad439359bbb9a1d973a18a9377f9c24394205858569113e3f6109a Bob (Bot Service) went down https://status.bobthebot.net/ Tue, 03 Feb 2026 16:43:47 +0000 https://status.bobthebot.net/#7d313a9c5700b703058d2683f046f41278062a8d1615410d7b4d8eff9a4364d4 Bob (Bot Service) recovered https://status.bobthebot.net/ Tue, 03 Feb 2026 16:41:22 +0000 https://status.bobthebot.net/#7d313a9c5700b703058d2683f046f41278062a8d1615410d7b4d8eff9a4364d4 Bob (Bot Service) went down https://status.bobthebot.net/incident/823570 Fri, 21 Nov 2025 01:00:00 -0000 https://status.bobthebot.net/incident/823570#cba23495ccc71f8f57214d3d87bf2148737eccb39678c0a22c4bc3de12fa085c **Date:** Nov 20, 2025 | **⏱ Duration:** ~1 hour ### **🧭 Summary** For about an hour, Bob failed to respond to slash commands due to Discord rejecting global command updates. The bot itself was healthy 🟢, but Discord’s API returned a persistent `50035 Invalid Form Body → BASE_TYPE_REQUIRED` error during registration. ### **🧰 What We Tried** 1. 🔁 Re‑deployed containers and tokens (no change) 2. 🧹 Cleared and re‑registered global commands 3. 🧪 Verified code against the dev bot (worked fine there) 4. 🏠 Registered commands per‑guild – confirmed success ### **🧩 Root Cause** A corrupted record in Discord’s global command database for Bob’s production application ID prevented any bulk overwrite from completing correctly. This was a **Discord‑side issue**, not a code error. ⚠️ ### **🛠️ Resolution** Catching and safely ignoring the benign API exception allowed Bob to continue starting up and attach all interaction handlers normally. Once running, slash commands responded instantly again. ✨ Discord Support has been contacted to clear the bad record for a permanent fix. 📨 ### **🕑 Timeline** - **5:23 PM CST** – 🚨 First 502 monitor alert - **5:30‑6:30 PM** – 🔎 Multiple retries and redeploys; issue isolated to Discord API - **6:50 PM CST** – 🧩 Workaround deployed; bot fully operational - **6:52 PM CST** – ✅ Incident resolved **Bob is stable again across all 2,500 servers.** Root cause: **Discord API corruption**, successfully mitigated by code‑level handling while awaiting an official fix from Discord. Nonetheless, we apologize for the inconvenience.