Incidents reported on status page for Quicklink https://status.qlynk.me/ https://d1lppblt9t2x15.cloudfront.net/logos/1c821315c00380275c0f801cbb7dbb30.jpeg https://status.qlynk.me/ en https://status.qlynk.me/ Thu, 04 Jun 2026 11:51:17 +0000 https://status.qlynk.me/#00ab19f74a60363ac9850e0762e628f0438c7df011dec3a86072b0488a81300f Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Thu, 04 Jun 2026 11:50:15 +0000 https://status.qlynk.me/#00ab19f74a60363ac9850e0762e628f0438c7df011dec3a86072b0488a81300f Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Tue, 02 Jun 2026 07:02:08 +0000 https://status.qlynk.me/#0b625f966d828e0552f640c9eb6cd215a97be17e80217fdec87d6f07952d632b Qlynk Node Server recovered https://status.qlynk.me/ Tue, 02 Jun 2026 06:59:39 +0000 https://status.qlynk.me/#09eec5f6ab96b7fd3a9dbc78fd9590da763b0048c85c3645ed88491c85ed6863 QLYNK Nobe Server Api recovered https://status.qlynk.me/ Tue, 02 Jun 2026 06:47:08 +0000 https://status.qlynk.me/#0b625f966d828e0552f640c9eb6cd215a97be17e80217fdec87d6f07952d632b Qlynk Node Server went down https://status.qlynk.me/ Tue, 02 Jun 2026 06:41:41 +0000 https://status.qlynk.me/#09eec5f6ab96b7fd3a9dbc78fd9590da763b0048c85c3645ed88491c85ed6863 QLYNK Nobe Server Api went down https://status.qlynk.me/ Tue, 02 Jun 2026 06:29:10 +0000 https://status.qlynk.me/#487914e1d01a3f4fca137ad1f4a97b5198693d7379e8dd289f74adb7c8cfa18a Qlynk Node Server recovered https://status.qlynk.me/ Tue, 02 Jun 2026 06:27:05 +0000 https://status.qlynk.me/#d3ed3ced04e52c7f733047c52f32b3f39f4ec2fcaebf528b1872f03a3cc88646 QLYNK Nobe Server Api recovered https://status.qlynk.me/ Tue, 02 Jun 2026 06:02:48 +0000 https://status.qlynk.me/#d3ed3ced04e52c7f733047c52f32b3f39f4ec2fcaebf528b1872f03a3cc88646 QLYNK Nobe Server Api went down https://status.qlynk.me/ Tue, 02 Jun 2026 05:56:36 +0000 https://status.qlynk.me/#1f727bc6b85d56e782560399da1361285b3f39cacd34c5fdaee7d23e643c42dc QLYNK Nobe Server Api recovered https://status.qlynk.me/ Tue, 02 Jun 2026 05:50:48 +0000 https://status.qlynk.me/#1f727bc6b85d56e782560399da1361285b3f39cacd34c5fdaee7d23e643c42dc QLYNK Nobe Server Api went down https://status.qlynk.me/ Tue, 02 Jun 2026 05:41:24 +0000 https://status.qlynk.me/#487914e1d01a3f4fca137ad1f4a97b5198693d7379e8dd289f74adb7c8cfa18a Qlynk Node Server went down https://status.qlynk.me/ Tue, 02 Jun 2026 05:20:08 +0000 https://status.qlynk.me/#2cb1bb9c6f4d4658eb90dfed360c5d2f6d8dab576caf05064579a64a75180f11 Qlynk Node Server recovered https://status.qlynk.me/ Tue, 02 Jun 2026 04:59:07 +0000 https://status.qlynk.me/#2cb1bb9c6f4d4658eb90dfed360c5d2f6d8dab576caf05064579a64a75180f11 Qlynk Node Server went down https://status.qlynk.me/ Tue, 02 Jun 2026 01:56:16 +0000 https://status.qlynk.me/#1fec70c047947994af15aa42ce6aca42b4b21beec999ee9e2e2730ba3cbc96a3 Qlynk Node Server recovered https://status.qlynk.me/ Tue, 02 Jun 2026 01:53:09 +0000 https://status.qlynk.me/#1fec70c047947994af15aa42ce6aca42b4b21beec999ee9e2e2730ba3cbc96a3 Qlynk Node Server went down https://status.qlynk.me/ Mon, 01 Jun 2026 09:59:34 +0000 https://status.qlynk.me/#24c8396a1fd14126510059c467053211dba67777332c72b63e2ee265c8e53848 Portfolio Website Status recovered https://status.qlynk.me/ Mon, 01 Jun 2026 09:56:33 +0000 https://status.qlynk.me/#24c8396a1fd14126510059c467053211dba67777332c72b63e2ee265c8e53848 Portfolio Website Status went down https://status.qlynk.me/ Thu, 14 May 2026 17:41:24 +0000 https://status.qlynk.me/#23dc0419682623c152cf47ef612075aa61bf85813c5a82208250c28d2b6cf352 Discord Bot Main recovered https://status.qlynk.me/ Thu, 14 May 2026 17:32:22 +0000 https://status.qlynk.me/#23dc0419682623c152cf47ef612075aa61bf85813c5a82208250c28d2b6cf352 Discord Bot Main went down https://status.qlynk.me/ Fri, 24 Apr 2026 18:32:11 +0000 https://status.qlynk.me/#578cad85f8f154c5789b6eafb8bacdcf871c3c42742f55028c23701cfe8bfa55 Discord Bot Main recovered https://status.qlynk.me/ Fri, 24 Apr 2026 18:30:20 +0000 https://status.qlynk.me/#578cad85f8f154c5789b6eafb8bacdcf871c3c42742f55028c23701cfe8bfa55 Discord Bot Main went down https://status.qlynk.me/ Tue, 14 Apr 2026 16:38:21 +0000 https://status.qlynk.me/#43abeca7dc12d327f0e05a59ad717206f749389b1271ceab860f530ccd000547 Qlynk Node Server recovered https://status.qlynk.me/ Tue, 14 Apr 2026 16:35:09 +0000 https://status.qlynk.me/#43abeca7dc12d327f0e05a59ad717206f749389b1271ceab860f530ccd000547 Qlynk Node Server went down https://status.qlynk.me/ Tue, 14 Apr 2026 16:02:16 +0000 https://status.qlynk.me/#063ee3d405f78664c408276fa030d41b6099bec3127863698e08ece6c894bbae Qlynk Node Server recovered https://status.qlynk.me/ Tue, 14 Apr 2026 15:56:06 +0000 https://status.qlynk.me/#063ee3d405f78664c408276fa030d41b6099bec3127863698e08ece6c894bbae Qlynk Node Server went down https://status.qlynk.me/ Tue, 14 Apr 2026 15:17:22 +0000 https://status.qlynk.me/#0be431f3b3b6ecaaffbc7fc2619e529c11e585bb08b9c4ebfd7b4323e0ef97ef Qlynk Node Server recovered https://status.qlynk.me/ Tue, 14 Apr 2026 15:11:19 +0000 https://status.qlynk.me/#0be431f3b3b6ecaaffbc7fc2619e529c11e585bb08b9c4ebfd7b4323e0ef97ef Qlynk Node Server went down https://status.qlynk.me/ Tue, 14 Apr 2026 15:05:13 +0000 https://status.qlynk.me/#660420ad6d6bd1cb543e2b7bc21e1ae3d6c74f53e972e8627fc1140861967887 Qlynk Node Server recovered https://status.qlynk.me/ Tue, 14 Apr 2026 14:59:29 +0000 https://status.qlynk.me/#660420ad6d6bd1cb543e2b7bc21e1ae3d6c74f53e972e8627fc1140861967887 Qlynk Node Server went down https://status.qlynk.me/ Tue, 14 Apr 2026 14:56:08 +0000 https://status.qlynk.me/#ef4a3c6a7cf47433d13127cf471507cb3aa97f22b28b74c04cb44769b26609e1 Qlynk Node Server recovered https://status.qlynk.me/ Tue, 14 Apr 2026 14:53:07 +0000 https://status.qlynk.me/#ef4a3c6a7cf47433d13127cf471507cb3aa97f22b28b74c04cb44769b26609e1 Qlynk Node Server went down https://status.qlynk.me/ Tue, 14 Apr 2026 12:27:22 +0000 https://status.qlynk.me/#9c48ced3aff65374f12825f02b49f221f590e6ab4b40997f1bb93bc40100e57f Qlynk Node Server recovered https://status.qlynk.me/ Tue, 14 Apr 2026 08:38:08 +0000 https://status.qlynk.me/#9c48ced3aff65374f12825f02b49f221f590e6ab4b40997f1bb93bc40100e57f Qlynk Node Server went down https://status.qlynk.me/ Sun, 12 Apr 2026 14:08:13 +0000 https://status.qlynk.me/#fe8b7d1f4f45225d50f928824920ab47dfda95679a8f38ec79516c75474d9ebd Qlynk Node Server recovered https://status.qlynk.me/ Sun, 12 Apr 2026 14:06:12 +0000 https://status.qlynk.me/#fe8b7d1f4f45225d50f928824920ab47dfda95679a8f38ec79516c75474d9ebd Qlynk Node Server went down https://status.qlynk.me/ Sun, 12 Apr 2026 06:08:17 +0000 https://status.qlynk.me/#69706f8605dc46aa56ecbcfeaba8b6bfb594655c5d810f8db796caf5b44f5494 Qlynk Node Server recovered https://status.qlynk.me/ Sun, 12 Apr 2026 06:06:16 +0000 https://status.qlynk.me/#69706f8605dc46aa56ecbcfeaba8b6bfb594655c5d810f8db796caf5b44f5494 Qlynk Node Server went down https://status.qlynk.me/ Sun, 12 Apr 2026 04:17:16 +0000 https://status.qlynk.me/#ea338f707bf6500432acdffd3b8e1121965a16c5b4d2d240d13d828cd2765c01 Qlynk Node Server recovered https://status.qlynk.me/ Sun, 12 Apr 2026 04:15:08 +0000 https://status.qlynk.me/#ea338f707bf6500432acdffd3b8e1121965a16c5b4d2d240d13d828cd2765c01 Qlynk Node Server went down https://status.qlynk.me/ Sat, 11 Apr 2026 21:53:11 +0000 https://status.qlynk.me/#acdd044a4a971fd20f174f98f855d4a4f698f4fed2f03c4d2f5ed83fbf5d958b Qlynk Node Server recovered https://status.qlynk.me/ Sat, 11 Apr 2026 21:51:13 +0000 https://status.qlynk.me/#acdd044a4a971fd20f174f98f855d4a4f698f4fed2f03c4d2f5ed83fbf5d958b Qlynk Node Server went down https://status.qlynk.me/ Sat, 11 Apr 2026 16:53:15 +0000 https://status.qlynk.me/#eb5b615d3e1efe1ff7a77cad3c7fb57b553e822466922cb84c3826963926eeb2 Qlynk Node Server recovered https://status.qlynk.me/ Sat, 11 Apr 2026 16:51:06 +0000 https://status.qlynk.me/#eb5b615d3e1efe1ff7a77cad3c7fb57b553e822466922cb84c3826963926eeb2 Qlynk Node Server went down https://status.qlynk.me/ Fri, 10 Apr 2026 09:41:09 +0000 https://status.qlynk.me/#60cad0c61c4656ae040c6be76656b142d10f31a244a35333e3916764c69bbc25 Qlynk Node Server recovered https://status.qlynk.me/ Fri, 10 Apr 2026 09:35:22 +0000 https://status.qlynk.me/#60cad0c61c4656ae040c6be76656b142d10f31a244a35333e3916764c69bbc25 Qlynk Node Server went down https://status.qlynk.me/ Thu, 09 Apr 2026 16:59:11 +0000 https://status.qlynk.me/#3b695201ac16b51564dd2e23a4203bd8d01db06b211d92ab19b72d99a49cf7ec Discord Bot Main recovered https://status.qlynk.me/ Thu, 09 Apr 2026 16:53:12 +0000 https://status.qlynk.me/#3b695201ac16b51564dd2e23a4203bd8d01db06b211d92ab19b72d99a49cf7ec Discord Bot Main went down https://status.qlynk.me/ Sat, 04 Apr 2026 13:29:14 +0000 https://status.qlynk.me/#de0771482320f25730469fb5501f953e38e54145dd461f065a71875bcfa6d2a8 Qlynk Node Server recovered https://status.qlynk.me/ Sat, 04 Apr 2026 13:26:16 +0000 https://status.qlynk.me/#de0771482320f25730469fb5501f953e38e54145dd461f065a71875bcfa6d2a8 Qlynk Node Server went down https://status.qlynk.me/ Thu, 02 Apr 2026 17:32:15 +0000 https://status.qlynk.me/#066055c3071a0d1b1eb9d9745d74fab2a8aebecae2ab2dd65565c15e832d4517 Qlynk Node Server recovered https://status.qlynk.me/ Thu, 02 Apr 2026 16:56:14 +0000 https://status.qlynk.me/#066055c3071a0d1b1eb9d9745d74fab2a8aebecae2ab2dd65565c15e832d4517 Qlynk Node Server went down https://status.qlynk.me/ Wed, 01 Apr 2026 11:50:09 +0000 https://status.qlynk.me/#57adb0969fdebfb7fecdcaa65001424c36c74de89fb5975f3c40da28ebad0e7b Qlynk Node Server recovered https://status.qlynk.me/ Wed, 01 Apr 2026 11:35:12 +0000 https://status.qlynk.me/#57adb0969fdebfb7fecdcaa65001424c36c74de89fb5975f3c40da28ebad0e7b Qlynk Node Server went down https://status.qlynk.me/ Wed, 01 Apr 2026 10:53:12 +0000 https://status.qlynk.me/#c5a70b59d10ceef9fe280fa1d3505bb7bbf240b69c59821daeb039b0fc41195b Qlynk Node Server recovered https://status.qlynk.me/ Wed, 01 Apr 2026 10:50:14 +0000 https://status.qlynk.me/#c5a70b59d10ceef9fe280fa1d3505bb7bbf240b69c59821daeb039b0fc41195b Qlynk Node Server went down https://status.qlynk.me/ Tue, 31 Mar 2026 17:08:11 +0000 https://status.qlynk.me/#5c03ac74e18f9d7089b6e0c0bd440b545e3dfa3182cb6fa200dc28482af6d534 Qlynk Node Server recovered https://status.qlynk.me/ Tue, 31 Mar 2026 16:59:16 +0000 https://status.qlynk.me/#5c03ac74e18f9d7089b6e0c0bd440b545e3dfa3182cb6fa200dc28482af6d534 Qlynk Node Server went down https://status.qlynk.me/ Mon, 30 Mar 2026 22:45:34 +0000 https://status.qlynk.me/#4aedfb913fc50c7a69a394c2570b4479b2bdc181c3efee977b68a77314ff15b7 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Mon, 30 Mar 2026 22:42:29 +0000 https://status.qlynk.me/#4aedfb913fc50c7a69a394c2570b4479b2bdc181c3efee977b68a77314ff15b7 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Mon, 30 Mar 2026 15:56:05 +0000 https://status.qlynk.me/#d8620f69ecadd2fc4365607af557067eb56dcee059c9fee6d074793faf4b5101 Qlynk Node Server recovered https://status.qlynk.me/ Mon, 30 Mar 2026 15:44:19 +0000 https://status.qlynk.me/#d8620f69ecadd2fc4365607af557067eb56dcee059c9fee6d074793faf4b5101 Qlynk Node Server went down https://status.qlynk.me/ Mon, 30 Mar 2026 15:29:11 +0000 https://status.qlynk.me/#af0e6249f767aeb5c02f40a17ceb63ef2f971070552ae168634e470752654164 Qlynk Node Server recovered https://status.qlynk.me/ Mon, 30 Mar 2026 15:20:09 +0000 https://status.qlynk.me/#af0e6249f767aeb5c02f40a17ceb63ef2f971070552ae168634e470752654164 Qlynk Node Server went down https://status.qlynk.me/ Wed, 25 Mar 2026 08:24:53 +0000 https://status.qlynk.me/#1eb9054413dcf33f111f53e6b437dd66feed9a3d10fbbdb8cfa885b3973b1dcd Qlynk Node Server recovered https://status.qlynk.me/ Sun, 22 Mar 2026 15:23:13 +0000 https://status.qlynk.me/#1eb9054413dcf33f111f53e6b437dd66feed9a3d10fbbdb8cfa885b3973b1dcd Qlynk Node Server went down https://status.qlynk.me/ Tue, 17 Mar 2026 21:32:14 +0000 https://status.qlynk.me/#73ea77d19afdec140031015c624792db0d0b9714e02836845a8a053b8eb1eb81 Qlynk Node Server recovered https://status.qlynk.me/ Tue, 17 Mar 2026 21:27:15 +0000 https://status.qlynk.me/#73ea77d19afdec140031015c624792db0d0b9714e02836845a8a053b8eb1eb81 Qlynk Node Server went down https://status.qlynk.me/incident/850440 Tue, 17 Mar 2026 13:12:59 -0000 https://status.qlynk.me/incident/850440#8e7a21c668b92870353b9e2d6dfc25521470f76a6cf2e53b6e6abb0a0809a793 We think that my Jee Exam and 12th class will start son so i want to stop and postpone the all product coding till jee advance exam so before start 12th class i need to stable every product and it will done in som days! thanks for your presence! https://status.qlynk.me/incident/850437 Tue, 17 Mar 2026 13:10:49 -0000 https://status.qlynk.me/incident/850437#06f6434c50773b0c4e4366aba1e5b370f49aba32203a45abaed4be61ad87c353 Now we will update our llm model and make 7million to 21million parameter with new interface and full changed everything with advance thing https://status.qlynk.me/incident/819756 Sat, 07 Feb 2026 10:16:00 -0000 https://status.qlynk.me/incident/819756#fc44ec61cf4a6d23692142fd85258498d0c42d28f3264f340149985ba7e08c2d All Errors, Rate Limit Fixed, Now you can use Our Bot! https://status.qlynk.me/incident/819756 Fri, 06 Feb 2026 08:26:00 -0000 https://status.qlynk.me/incident/819756#369ce27a6d5a7a45d21c19074bfe5dd76ee4befb239470f43c63c6f1163d1763 ### Update: Fixes Deployed, Upstream Cooldown in Effect All planned fixes have been successfully deployed. During restart, the Discord bot is currently encountering an upstream rate-limit cooldown. This is expected behavior following earlier request spikes and is not related to the new code changes. #### Current situation - Code deployment: ✅ Completed - Server health: ✅ Stable - Bot login: ⏳ Delayed due to upstream rate limiting #### What we’re doing - The service has been paused to allow the cooldown window to fully reset - No further restart attempts will be made during this period - A single clean restart will be performed once the cooldown expires #### What’s next - Wait for the upstream cooldown to clear - Restart the bot once - Monitor stability and slash command availability - Mark the incident as resolved after confirmation Thank you for your patience. This step ensures a clean and stable recovery. https://status.qlynk.me/incident/819756 Fri, 06 Feb 2026 08:26:00 -0000 https://status.qlynk.me/incident/819756#12f975cc2801f8d7e8e5c662dd15a570fdcb9a7c6d171845d074aa4bf2c7bbd4 Fixes have been deployed successfully. The Discord bot is temporarily delayed from restarting due to upstream rate-limit cooldown. https://status.qlynk.me/incident/819756 Fri, 06 Feb 2026 08:20:00 -0000 https://status.qlynk.me/incident/819756#7a1309e899ada3d7b91b44a1c955516ebf0ce3f32da202e01ba8e79594ffc70b ### Update: Deployment in Progress The required fixes have been successfully deployed, and the Discord bot is currently restarting as part of a controlled recovery process. #### What’s happening now - The server is restarting to apply the latest fixes - Command synchronization and rate-limit safeguards are being initialized - No user action is required at this time #### What was fixed - Slash command synchronization optimized to run only once on startup - Duplicate and per-module sync calls removed - Rate-limit handling and cooldowns added - Background and presence update frequency reduced #### Current status - Deployment: **In progress** - Bot availability: **Temporarily offline** - Monitoring will begin immediately after startup #### What’s next - Verify slash commands (`/`) are visible and responsive - Monitor logs and API usage for stability - Mark the incident as **Resolved** once confirmed stable Thank you for your patience while we complete this final step. https://status.qlynk.me/incident/819756 Fri, 06 Feb 2026 08:20:00 -0000 https://status.qlynk.me/incident/819756#d7b543b158247e549eed86fa63ce7c8d0e786ecde2de458a1c9ef0aae1c356e0 Fixes have been deployed and the Discord bot is currently restarting. Monitoring will begin shortly after startup. https://status.qlynk.me/incident/819756 Fri, 06 Feb 2026 08:13:00 -0000 https://status.qlynk.me/incident/819756#fa13325673d53524c9e6ed081c75b283537dc2ad614fd1f8c4c00a611d8cf861 ### Update: Mitigation Completed, Restart Pending We have successfully identified the root cause of the Discord bot downtime and completed the required fixes. #### What happened The issue was caused by excessive startup and command synchronization requests, which triggered upstream rate limiting. This resulted in slash commands (`/`) not appearing or responding as expected. #### What we have done - Optimized command synchronization to run only once on startup - Removed duplicate and per-module sync calls - Added strict rate-limit handling and cooldowns - Reduced background and presence update frequency - Temporarily suspended the service to allow upstream limits to reset #### Current status The fixes have been pushed successfully. The bot is currently offline as part of a controlled mitigation process. #### What’s next - The server will be restarted shortly - The service will be monitored closely after restart - Once stability is confirmed, the incident will be marked as resolved We appreciate your patience while we ensure long-term stability and reliability. https://status.qlynk.me/incident/819756 Fri, 06 Feb 2026 08:08:00 -0000 https://status.qlynk.me/incident/819756#64a2817d528bcc0929363cd99ffbba62cfb37edf0c1deb8b5e39d65951816cee The root cause has been identified and fixes have been deployed. The Discord bot is currently offline for stabilization and will be restarted shortly. https://status.qlynk.me/incident/819756 Fri, 06 Feb 2026 07:50:00 -0000 https://status.qlynk.me/incident/819756#10d2b0bc2a38e6294e4cb92d1568d1fea50848464848dd3f3e8198fd11a205de ## Incident Report: Temporary Discord Bot Downtime **Incident Start:** Feb 05, 01:07 PM IST **Current Status:** Mitigated (Fix in Progress) **Affected Service:** Discord Bot Main **Severity:** Minor → Degraded Service --- ### 📌 Summary Our Discord bot experienced a temporary downtime due to upstream rate limiting, which resulted in slash commands (`/`) becoming unavailable or unresponsive for a short period of time. This issue was **not related to a security breach or data loss**, but rather to an internal synchronization process that unintentionally exceeded request thresholds enforced by the upstream provider. --- ### 👥 User Impact During the incident window: - Slash commands may not have appeared when typing `/` - Some commands may have failed to respond - Bot functionality was partially or fully unavailable No user data, credentials, or integrations were affected. --- ### 🔍 Root Cause Analysis The root cause was identified as an **internal command synchronization and startup logic issue**, which caused: - Repeated API requests during bot initialization or reconnect events - Excessive command sync attempts in a short time window This behavior triggered **temporary upstream rate limiting**, leading to service disruption. --- ### 🛠️ Mitigation & Fix (In Progress) To safely resolve the issue, the following steps are being implemented: - The bot service has been **temporarily taken offline** to prevent further upstream requests - Rate-limit handling logic is being strengthened to strictly respect API limits - Slash command synchronization logic is being optimized to: - Run only once on startup - Avoid duplicate or repeated syncs - Cooldowns are being added to prevent request spikes - Background tasks and startup routines are being reviewed to eliminate unnecessary calls --- ### ⏱️ Estimated Resolution Time - **Code fixes:** In progress - **Testing & validation:** ~30–60 minutes - **Service restoration:** Shortly after validation completes The service will be brought back online only after confirming stability and compliance with rate limits. --- ### 📊 Current Status - Bot service: **Offline (Mitigation Mode)** - Monitoring: **Active** - Next update: Once service is stable and restored --- ### 🙏 Closing Note We appreciate your patience while we improve the reliability and stability of our Discord bot. Transparency and long-term stability are our top priorities. Further updates will be posted here as progress continues. https://status.qlynk.me/incident/819756 Fri, 06 Feb 2026 07:37:00 -0000 https://status.qlynk.me/incident/819756#b77382111aa1fc38786b15e702e0b3a2c010ae659bcf51ca574f3872de79e7af Status: Investigating → Mitigated Summary: Our Discord Bot experienced a temporary downtime due to upstream rate limiting, which caused slash commands to become temporarily unavailable. Impact: Users may have experienced missing or unresponsive slash commands during this period. Root Cause: An internal synchronization process triggered excessive requests, leading to temporary rate limiting by the upstream service. Resolution: The bot has been taken offline temporarily while rate-limit handling and command synchronization logic are being optimized. Current Status: Mitigation in progress. Service restoration expected shortly. We appreciate your patience. https://status.qlynk.me/incident/799443 Tue, 06 Jan 2026 14:19:00 -0000 https://status.qlynk.me/incident/799443#8501c3fba63085c32dbbb063cbc2747a86be433781bf61771f755a1a88517670 Thanks https://status.qlynk.me/incident/799443 Tue, 06 Jan 2026 14:18:00 -0000 https://status.qlynk.me/incident/799443#807a43bbfa371ad23a65f5a42928559fb634cb7898d28c8a8e0a52447d822a6f we notice an down on discord bot status, dont worry its an bug we fixed it https://status.qlynk.me/incident/799443 Tue, 06 Jan 2026 14:18:00 -0000 https://status.qlynk.me/incident/799443#a24b9fa4c29b219da471e9e9724b575ee66ecd6658c098c9f76e4e02c3f5a3f6 we notice an down on discord bot status, dont worry its an bug we fixed it https://status.qlynk.me/incident/797506 Sun, 04 Jan 2026 18:01:42 -0000 https://status.qlynk.me/incident/797506#7864287702c01ecd5268273d28c9f81ed58f7374dc83ba999ad8e5c5a9d3fce3 Maintenance completed https://status.qlynk.me/incident/797835 Sat, 03 Jan 2026 10:11:00 -0000 https://status.qlynk.me/incident/797835#50713230cf4406a9fdc6a3f64ded0d6eb4329be88e5d649d5db3141155a21e24 all done, fixed everything, now you can use our service, thanks for your patience :) https://status.qlynk.me/incident/797835 Sat, 03 Jan 2026 10:09:00 -0000 https://status.qlynk.me/incident/797835#7865bf273d0f6afc506b859cc751fde56df77777571f4312aa73603fcfacbe3e oh its an minor issue, we fixed it, time need for getting the update all over the world https://status.qlynk.me/incident/797835 Sat, 03 Jan 2026 10:07:00 -0000 https://status.qlynk.me/incident/797835#d0434f983947d2046b3a347fb0c7880686654994e8eb74831dc9382f504ec311 we need some time to fix it, sorry for that! https://status.qlynk.me/incident/797835 Sat, 03 Jan 2026 10:04:00 -0000 https://status.qlynk.me/incident/797835#516ca2c02891ab2763cb55c1870d362ddeb8959ce93b1026beb20d905cb6249a The all quicklink domain should be down for sometime due to an internal our side problem, we will fix it as soon as possible, dont worry! https://status.qlynk.me/incident/797561 Fri, 02 Jan 2026 18:29:00 -0000 https://status.qlynk.me/incident/797561#1c98aa270260ad9c88b1683594a5555c4112f2bed132b3e00aef6038c6dbf83b Qr Code Resolved https://status.qlynk.me/incident/797561 Fri, 02 Jan 2026 18:27:00 -0000 https://status.qlynk.me/incident/797561#37eed03e405624ead019f0c226a11200734f01d1190d8f13f8aed9ff9a332f30 But... the third Party qr code api have some problem but our own qr code is too much and the qr code ap will be resolve soon! https://status.qlynk.me/incident/797506 Thu, 01 Jan 2026 15:38:00 -0000 https://status.qlynk.me/incident/797506#4e12641e22486e3102248f4b1f0f7c5c2a5795d9fac4d57a8a861d1b9251b33a We will add many things like 2fa update, otp system and many surprises coming soon