Incidents reported on status page for BrainUs https://status.brainus.lk/ https://d1lppblt9t2x15.cloudfront.net/logos/80355d254d4703216dbca16c6d7449cc.png https://status.brainus.lk/ en https://status.brainus.lk/incident/949197 Fri, 10 Jul 2026 00:00:28 -0000 https://status.brainus.lk/incident/949197#abea3185c2623a6605c78f0250b88d97cdc29c5b9b5e54da73d8201181cbc52d Maintenance completed https://status.brainus.lk/incident/949197 Thu, 09 Jul 2026 22:30:28 -0000 https://status.brainus.lk/incident/949197#4de11ec3506bd56d7e0f0ca66bbcdfe07d098c6c07593a669e304b0f248958de We're migrating our database to new infrastructure to improve performance and reliability During this window, you may briefly experience issues with chat conversations, quizzes, and loading past activity. No data will be lost, and no action is needed on your part. We expect the actual interruption to last only a few minutes within this window. https://status.brainus.lk/incident/940651 Wed, 01 Jul 2026 19:08:00 -0000 https://status.brainus.lk/incident/940651#8143ce595d6d712757a607f45ab076f48a93f8991c714f5780029e44d5389e31 We have identified the root cause of the Notion connection issue and confirmed it is entirely external. Our logs show a 2+ minute gap of zero activity on our servers after navigating to the authentication pages at mcp.notion.com, with no callback ever being received from their system. Since this issue is happening entirely on Notion's own MCP service, it is outside of our codebase's control. We are monitoring their service status and will update here as soon as their authentication pages are stable again. The main BrainUs AI chat remains fully operational. https://status.brainus.lk/incident/940651 Wed, 01 Jul 2026 15:01:00 -0000 https://status.brainus.lk/incident/940651#e978ff0db2b094f9816b9d4f2d65485c07d34b20f49dc70a4f49941d9d92e5a5 We're investigating an issue with our Notion integration that is preventing some users from successfully linking their workspaces to BrainUs AI. The problem occurs during the connection handshake phase, resulting in a timeout error when the system attempts to sync. Our main AI chat and core study tools remain fully operational. We're actively working to resolve the connection issue as quickly as possible and will share another update shortly. https://status.brainus.lk/ Wed, 17 Jun 2026 13:17:34 +0000 https://status.brainus.lk/#8029a6158d0fe3a4015af5712a3eb3a373a6e3c3572f7d4d80db672051d8e778 BrainUs Learn recovered https://status.brainus.lk/ Tue, 16 Jun 2026 19:37:35 +0000 https://status.brainus.lk/#8029a6158d0fe3a4015af5712a3eb3a373a6e3c3572f7d4d80db672051d8e778 BrainUs Learn went down https://status.brainus.lk/ Sat, 06 Jun 2026 08:32:14 +0000 https://status.brainus.lk/#ae27c30f25503f41b4f3ab8be0656f9b61912bd36e50331c672a626ccc4dbe51 Redis recovered https://status.brainus.lk/ Sat, 06 Jun 2026 08:28:08 +0000 https://status.brainus.lk/#ae27c30f25503f41b4f3ab8be0656f9b61912bd36e50331c672a626ccc4dbe51 Redis went down https://status.brainus.lk/incident/775377 Thu, 27 Nov 2025 16:16:00 -0000 https://status.brainus.lk/incident/775377#4b37ee682f604717abb60c591fa942dca6370c071f96312aa48f13fe230902c6 Chat is fully back to normal! We’ve fixed the Redis validation issue by making it tolerant of older messages with incomplete citations. All conversations are now loading and saving correctly, and caching is working as intended. https://status.brainus.lk/incident/775377 Thu, 27 Nov 2025 10:13:00 -0000 https://status.brainus.lk/incident/775377#189583e5d5fc22399fff7f7965d3055e35daf25c322b956024656a5e0cbcc59c We've pinpointed the cause of the chat outage: our new Redis caching system is rejecting older conversation messages that contain incomplete document citations, such as missing file names or IDs. This validation error is blocking the entire chat process, preventing users from sending or saving new messages https://status.brainus.lk/incident/775377 Thu, 27 Nov 2025 10:05:00 -0000 https://status.brainus.lk/incident/775377#ed5311c9408385f316f860487361c195d87e78816cfe5782ef59b9c5f551b4de We're investigating an issue with our chat system that is preventing users from sending messages. The problem occurs when the system tries to process conversations that reference certain documents. We're working to fix the problem as quickly as we can. We'll share another update shortly.