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/ Tue, 10 Mar 2026 09:24:33 +0000 https://status.qlynk.me/#191e6ac851c848eb99824eac360eac96545ebcb97c4dddde19dcead57bcec1e4 DEQLYNK AI recovered https://status.qlynk.me/ Tue, 10 Mar 2026 09:14:56 +0000 https://status.qlynk.me/#191e6ac851c848eb99824eac360eac96545ebcb97c4dddde19dcead57bcec1e4 DEQLYNK AI went down https://status.qlynk.me/ Tue, 24 Feb 2026 18:27:34 +0000 https://status.qlynk.me/#f2f2e4316837b19f879fead0f808bcaeede69aa02dd9db27812d3a46386ae002 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Tue, 24 Feb 2026 18:22:31 +0000 https://status.qlynk.me/#f2f2e4316837b19f879fead0f808bcaeede69aa02dd9db27812d3a46386ae002 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Sun, 15 Feb 2026 02:14:12 +0000 https://status.qlynk.me/#a194df23e021b2bf12fe4515c8ecd147e53f9e2e0ab5dd63b5b89d801681e6cd Discord Bot Main recovered https://status.qlynk.me/ Sun, 15 Feb 2026 02:12:11 +0000 https://status.qlynk.me/#a194df23e021b2bf12fe4515c8ecd147e53f9e2e0ab5dd63b5b89d801681e6cd Discord Bot Main went down https://status.qlynk.me/ Fri, 13 Feb 2026 20:41:20 +0000 https://status.qlynk.me/#4efe002b8aad32cbc3c031bf41456b469c138169c1696c78e2f1b519fc2b2dea Discord Bot Main recovered https://status.qlynk.me/ Fri, 13 Feb 2026 20:36:11 +0000 https://status.qlynk.me/#4efe002b8aad32cbc3c031bf41456b469c138169c1696c78e2f1b519fc2b2dea Discord Bot Main went down https://status.qlynk.me/ Fri, 13 Feb 2026 15:50:15 +0000 https://status.qlynk.me/#22ab8b9a15ddb6f44c6335ea41166f4b70e004eeb89956c263622bf621c3fc8f Discord Bot Main recovered https://status.qlynk.me/ Wed, 11 Feb 2026 12:29:16 +0000 https://status.qlynk.me/#22ab8b9a15ddb6f44c6335ea41166f4b70e004eeb89956c263622bf621c3fc8f Discord Bot Main went down https://status.qlynk.me/ Sun, 08 Feb 2026 11:25:28 +0000 https://status.qlynk.me/#d994b3bcf681f4f0b360832b92c2e3f25f6b0e00b9d824ee476e767fe8b60201 Our Backend Payment Verification recovered https://status.qlynk.me/ Sat, 07 Feb 2026 15:01:28 +0000 https://status.qlynk.me/#d994b3bcf681f4f0b360832b92c2e3f25f6b0e00b9d824ee476e767fe8b60201 Our Backend Payment Verification went down https://status.qlynk.me/ Sat, 07 Feb 2026 10:17:18 +0000 https://status.qlynk.me/#eed61f1a5fc58d609db2b93c9a24d2f1622fb2a778b4a50704ef365d5c3df1a6 Discord Bot Main recovered 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/ Fri, 06 Feb 2026 22:44:38 +0000 https://status.qlynk.me/#eed61f1a5fc58d609db2b93c9a24d2f1622fb2a778b4a50704ef365d5c3df1a6 Discord Bot Main went down https://status.qlynk.me/ Fri, 06 Feb 2026 22:38:43 +0000 https://status.qlynk.me/#0b15ac6f6d5143e5d5fdf00f38cf7c87ad929834c3aee3a145030611001ab1a1 Discord Bot Main recovered 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/ Fri, 06 Feb 2026 06:44:18 +0000 https://status.qlynk.me/#0b15ac6f6d5143e5d5fdf00f38cf7c87ad929834c3aee3a145030611001ab1a1 Discord Bot Main went down https://status.qlynk.me/ Tue, 20 Jan 2026 01:17:18 +0000 https://status.qlynk.me/#b0abd135cd80700303c0788df73cc39514245cf206ee961694c4d1137681de3f Payment Gatway recovered https://status.qlynk.me/ Tue, 20 Jan 2026 01:12:17 +0000 https://status.qlynk.me/#b0abd135cd80700303c0788df73cc39514245cf206ee961694c4d1137681de3f Payment Gatway went down https://status.qlynk.me/ Tue, 20 Jan 2026 00:47:12 +0000 https://status.qlynk.me/#958402d0212421c70df6ca8a0ccadcdf9926afd170996a29030d76bbce48d597 Discord Bot Main recovered https://status.qlynk.me/ Tue, 20 Jan 2026 00:45:19 +0000 https://status.qlynk.me/#958402d0212421c70df6ca8a0ccadcdf9926afd170996a29030d76bbce48d597 Discord Bot Main went down https://status.qlynk.me/ Thu, 15 Jan 2026 02:15:37 +0000 https://status.qlynk.me/#0f993a761d2380b85d3d8b2ca71517f6e84b44a6e70c760d222baaa453b52cb0 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Thu, 15 Jan 2026 02:00:54 +0000 https://status.qlynk.me/#0f993a761d2380b85d3d8b2ca71517f6e84b44a6e70c760d222baaa453b52cb0 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 22:54:42 +0000 https://status.qlynk.me/#cdd15c56919096cec9ca1da34a25e549fff79d429ceaf150438cf81f69cd7948 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 22:52:35 +0000 https://status.qlynk.me/#cdd15c56919096cec9ca1da34a25e549fff79d429ceaf150438cf81f69cd7948 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 19:42:41 +0000 https://status.qlynk.me/#9e22d717c7ca758dfd3a290e2403cf106d4c5a78eda0ed228d7d025ce1f71bed Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 19:40:38 +0000 https://status.qlynk.me/#9e22d717c7ca758dfd3a290e2403cf106d4c5a78eda0ed228d7d025ce1f71bed Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 19:24:31 +0000 https://status.qlynk.me/#4ea3449047770df5e155e971c1983c3c3578b0f373a8d8bfb782cdeff6313192 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 19:22:39 +0000 https://status.qlynk.me/#4ea3449047770df5e155e971c1983c3c3578b0f373a8d8bfb782cdeff6313192 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 19:12:31 +0000 https://status.qlynk.me/#1233ecbd7b2ee2785cc60761decae73e8fffa61d4a7f4067a190754eee625dce Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 19:04:01 +0000 https://status.qlynk.me/#1233ecbd7b2ee2785cc60761decae73e8fffa61d4a7f4067a190754eee625dce Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 18:57:44 +0000 https://status.qlynk.me/#da8377ab89b35a3210759aa4be52f1dce97e7d716eff006ab83548b9bfe47349 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 18:55:38 +0000 https://status.qlynk.me/#da8377ab89b35a3210759aa4be52f1dce97e7d716eff006ab83548b9bfe47349 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 18:36:35 +0000 https://status.qlynk.me/#efc2a51f3de4f40c28109dc0d83d1c3957ee682eae477f354973ab33d4e0bd7e Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 18:31:37 +0000 https://status.qlynk.me/#efc2a51f3de4f40c28109dc0d83d1c3957ee682eae477f354973ab33d4e0bd7e Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 17:51:35 +0000 https://status.qlynk.me/#89052413ccd385168b4f3d60a722caa4394ce58d8d25183fcfd0784e3546fbc4 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 17:48:57 +0000 https://status.qlynk.me/#89052413ccd385168b4f3d60a722caa4394ce58d8d25183fcfd0784e3546fbc4 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 17:36:32 +0000 https://status.qlynk.me/#2637da81f3314c146a946dc14c3e778f812c9afb222918f73f0c641554473c14 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 17:34:08 +0000 https://status.qlynk.me/#2637da81f3314c146a946dc14c3e778f812c9afb222918f73f0c641554473c14 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 17:06:37 +0000 https://status.qlynk.me/#3f389119511ad8d0c8f88387d37a8a37ea1ef7cce61dc721338721ce02889c6b Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 17:04:32 +0000 https://status.qlynk.me/#3f389119511ad8d0c8f88387d37a8a37ea1ef7cce61dc721338721ce02889c6b Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 14:18:41 +0000 https://status.qlynk.me/#7c10eb972186519576ee11e4d388f6278f0eced3dbb2b553374a1564ec1df86c Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 14:07:04 +0000 https://status.qlynk.me/#7c10eb972186519576ee11e4d388f6278f0eced3dbb2b553374a1564ec1df86c Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 13:45:42 +0000 https://status.qlynk.me/#f6171e96bcabecaf8bdd9c90febea4a057b8983dc2757f548612691634f7ce94 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 13:43:02 +0000 https://status.qlynk.me/#f6171e96bcabecaf8bdd9c90febea4a057b8983dc2757f548612691634f7ce94 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 13:15:37 +0000 https://status.qlynk.me/#4179a01eda4fad4681ae332151b43ffd89d491022dc365587afc74e8bfc22c0d Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 13:10:05 +0000 https://status.qlynk.me/#4179a01eda4fad4681ae332151b43ffd89d491022dc365587afc74e8bfc22c0d Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 11:54:43 +0000 https://status.qlynk.me/#58a43ddb9c4c50f8cfa55581635e64b0129c063cb2eb1f2921f0ff0a0e93b29a Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 11:49:03 +0000 https://status.qlynk.me/#58a43ddb9c4c50f8cfa55581635e64b0129c063cb2eb1f2921f0ff0a0e93b29a Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 11:09:42 +0000 https://status.qlynk.me/#aa6943f1d4bc5324c513c35a165ab99a9fc1fd3b3b7daf0f8d4e6724da4bb085 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 11:07:06 +0000 https://status.qlynk.me/#aa6943f1d4bc5324c513c35a165ab99a9fc1fd3b3b7daf0f8d4e6724da4bb085 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 10:39:40 +0000 https://status.qlynk.me/#3d1b36a605712422a36c84e9feece33335d1dd47b823cfe1c7325ac8af0f664c Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 10:34:34 +0000 https://status.qlynk.me/#3d1b36a605712422a36c84e9feece33335d1dd47b823cfe1c7325ac8af0f664c Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 10:06:47 +0000 https://status.qlynk.me/#60ef8480a55075f2dad752b7a051a6fdfd291e4a8bcc93f91708db8b9fc07d05 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 09:46:06 +0000 https://status.qlynk.me/#60ef8480a55075f2dad752b7a051a6fdfd291e4a8bcc93f91708db8b9fc07d05 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 07:54:36 +0000 https://status.qlynk.me/#8c9b002ce41692ad095632a9683fbad68da3ca42e68be8ee7469b41d39f1b3f6 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 07:46:03 +0000 https://status.qlynk.me/#8c9b002ce41692ad095632a9683fbad68da3ca42e68be8ee7469b41d39f1b3f6 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 06:09:41 +0000 https://status.qlynk.me/#92a3e4c02697350b545fd1618e0f666e06cf97945b59b1761ae0c0fa17b27158 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 06:07:03 +0000 https://status.qlynk.me/#92a3e4c02697350b545fd1618e0f666e06cf97945b59b1761ae0c0fa17b27158 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 05:45:36 +0000 https://status.qlynk.me/#62e051036163781f8a48a74b434ee6188d3534b3185db9d7cfc1258b4b700c48 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 05:31:05 +0000 https://status.qlynk.me/#62e051036163781f8a48a74b434ee6188d3534b3185db9d7cfc1258b4b700c48 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 05:00:39 +0000 https://status.qlynk.me/#5d379a2c73bc8775ba9b31013489339f0e179401747f5b2dd66d3aae1ebd773c Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 04:58:30 +0000 https://status.qlynk.me/#5d379a2c73bc8775ba9b31013489339f0e179401747f5b2dd66d3aae1ebd773c Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 04:51:36 +0000 https://status.qlynk.me/#abb4e44c54bb180ed54f8b1eaed7cfeadda7b4094261f46b34db02321b636c25 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 04:46:00 +0000 https://status.qlynk.me/#abb4e44c54bb180ed54f8b1eaed7cfeadda7b4094261f46b34db02321b636c25 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 03:21:43 +0000 https://status.qlynk.me/#d000d22634a7e0cfdb1f3f421320a4a17e741c9555866d0fbebf86b9daec73d9 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 03:15:59 +0000 https://status.qlynk.me/#d000d22634a7e0cfdb1f3f421320a4a17e741c9555866d0fbebf86b9daec73d9 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 02:39:37 +0000 https://status.qlynk.me/#584f44f801dfbb4baeb1db809ef261df0e5a97860baa7064b0078be741c9bfc5 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 02:28:28 +0000 https://status.qlynk.me/#584f44f801dfbb4baeb1db809ef261df0e5a97860baa7064b0078be741c9bfc5 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Wed, 14 Jan 2026 01:24:36 +0000 https://status.qlynk.me/#4e0dc6e5adc238c9bc6ee438d9dc13a023ee8bbee353f6bba4b3d7c28e657bf7 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Wed, 14 Jan 2026 01:22:34 +0000 https://status.qlynk.me/#4e0dc6e5adc238c9bc6ee438d9dc13a023ee8bbee353f6bba4b3d7c28e657bf7 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Tue, 13 Jan 2026 22:24:35 +0000 https://status.qlynk.me/#95cdf1b98178bb527505cad0059c9f740f1f755c86fa75e248c3d0015252a552 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Tue, 13 Jan 2026 22:10:04 +0000 https://status.qlynk.me/#95cdf1b98178bb527505cad0059c9f740f1f755c86fa75e248c3d0015252a552 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Tue, 13 Jan 2026 21:39:32 +0000 https://status.qlynk.me/#68c2c472baa252b387f27adfc3f75e43328ee9e84368c24f275977b3356081cb Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Tue, 13 Jan 2026 21:25:36 +0000 https://status.qlynk.me/#68c2c472baa252b387f27adfc3f75e43328ee9e84368c24f275977b3356081cb Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Tue, 13 Jan 2026 18:06:40 +0000 https://status.qlynk.me/#5a1199f4806342f8f64f2d28e5d10725b2f711aa4855bb906dfd37795dfb6158 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Tue, 13 Jan 2026 18:04:25 +0000 https://status.qlynk.me/#5a1199f4806342f8f64f2d28e5d10725b2f711aa4855bb906dfd37795dfb6158 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Tue, 13 Jan 2026 17:36:27 +0000 https://status.qlynk.me/#7d26133f63303d2b2bd2842edc7822fc8da5b4461c8bb2534bbd386fd402e319 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Tue, 13 Jan 2026 17:28:35 +0000 https://status.qlynk.me/#7d26133f63303d2b2bd2842edc7822fc8da5b4461c8bb2534bbd386fd402e319 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Tue, 13 Jan 2026 17:00:42 +0000 https://status.qlynk.me/#a7313aad67ca7c128fc73038a645cd8370353dde0b8a158a321c60e7fb601173 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Tue, 13 Jan 2026 16:55:38 +0000 https://status.qlynk.me/#a7313aad67ca7c128fc73038a645cd8370353dde0b8a158a321c60e7fb601173 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Tue, 13 Jan 2026 16:18:40 +0000 https://status.qlynk.me/#dd3a80c29d56fdb154ef3b486eb3762752de7f1fc1bd7a5d4c13379ae763957d Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Tue, 13 Jan 2026 16:16:43 +0000 https://status.qlynk.me/#dd3a80c29d56fdb154ef3b486eb3762752de7f1fc1bd7a5d4c13379ae763957d Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Tue, 13 Jan 2026 15:42:35 +0000 https://status.qlynk.me/#80c195461fb341386133b294596d91e8dc68e2b251f38bd07ad0933b7c3b5063 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Tue, 13 Jan 2026 15:31:38 +0000 https://status.qlynk.me/#80c195461fb341386133b294596d91e8dc68e2b251f38bd07ad0933b7c3b5063 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Tue, 13 Jan 2026 15:15:33 +0000 https://status.qlynk.me/#46385081c475c08539d31f64bcb862677822ef4b82f6af66012813b4efd3886a Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Tue, 13 Jan 2026 15:10:04 +0000 https://status.qlynk.me/#46385081c475c08539d31f64bcb862677822ef4b82f6af66012813b4efd3886a Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Tue, 13 Jan 2026 13:36:28 +0000 https://status.qlynk.me/#7e942e3423a25d15c3447fa44cab2bcfb5a62b65e7656f00cbac53f6d0bdd4a4 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Tue, 13 Jan 2026 13:10:12 +0000 https://status.qlynk.me/#7e942e3423a25d15c3447fa44cab2bcfb5a62b65e7656f00cbac53f6d0bdd4a4 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Tue, 13 Jan 2026 13:03:50 +0000 https://status.qlynk.me/#074ac26daba9525e9e3989321c8d36f304e32de1397286c90d61bd45c2998cd1 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Tue, 13 Jan 2026 12:58:38 +0000 https://status.qlynk.me/#074ac26daba9525e9e3989321c8d36f304e32de1397286c90d61bd45c2998cd1 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Tue, 13 Jan 2026 12:30:39 +0000 https://status.qlynk.me/#22aea9457e5362f671a7c4a843858222a27d2d619e50273112005eadcd9e6104 Our Third Party Qr Code Scanner recovered https://status.qlynk.me/ Tue, 13 Jan 2026 12:27:57 +0000 https://status.qlynk.me/#22aea9457e5362f671a7c4a843858222a27d2d619e50273112005eadcd9e6104 Our Third Party Qr Code Scanner went down https://status.qlynk.me/ Sun, 11 Jan 2026 07:05:15 +0000 https://status.qlynk.me/#e0553fccc6c78ac90ca745f29817721a36ca9d2d043fc0e0fd82e7a9c047ceac Discord Bot Main recovered https://status.qlynk.me/ Sun, 11 Jan 2026 06:57:51 +0000 https://status.qlynk.me/#e0553fccc6c78ac90ca745f29817721a36ca9d2d043fc0e0fd82e7a9c047ceac Discord Bot Main went down 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/ Mon, 05 Jan 2026 14:17:18 +0000 https://status.qlynk.me/#271da50ddd216e8686800f27f9f57a365d0111446b32a1c1727730334121b02c Discord Bot Main recovered https://status.qlynk.me/ Mon, 05 Jan 2026 14:15:18 +0000 https://status.qlynk.me/#271da50ddd216e8686800f27f9f57a365d0111446b32a1c1727730334121b02c Discord Bot Main went down 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/797506 Sun, 04 Jan 2026 18:01:42 -0000 https://status.qlynk.me/incident/797506#7864287702c01ecd5268273d28c9f81ed58f7374dc83ba999ad8e5c5a9d3fce3 Maintenance completed 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/797506 Sun, 04 Jan 2026 18:01:42 -0000 https://status.qlynk.me/incident/797506#7864287702c01ecd5268273d28c9f81ed58f7374dc83ba999ad8e5c5a9d3fce3 Maintenance completed 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/ Sat, 03 Jan 2026 10:11:47 +0000 https://status.qlynk.me/#6a160527f5aa45cc63adc25dfa292df1f3a7a9ab0234abdd818e6518b35ecbd3 Our Url Shortning Api recovered https://status.qlynk.me/ Sat, 03 Jan 2026 10:11:39 +0000 https://status.qlynk.me/#b16010d9292df835b32909e4c27b62745ce1836052fecc97557ecca914f76ccb Our Backend Payment Verification recovered https://status.qlynk.me/ Sat, 03 Jan 2026 10:11:22 +0000 https://status.qlynk.me/#1e1c4874d8ea708d7f5537b5a02a21d600e10cb9092cdb8ae496b68d9823eb82 Our Backend Server recovered https://status.qlynk.me/ Sat, 03 Jan 2026 10:11:13 +0000 https://status.qlynk.me/#1282ef7efbb6d8c3dda6af9b6adcfd5617887bc216f29c8604bf543e34783595 Website Status recovered 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: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: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: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: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: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: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/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/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/ Sat, 03 Jan 2026 10:03:51 +0000 https://status.qlynk.me/#1282ef7efbb6d8c3dda6af9b6adcfd5617887bc216f29c8604bf543e34783595 Website Status went down https://status.qlynk.me/ Sat, 03 Jan 2026 10:00:27 +0000 https://status.qlynk.me/#8cf95d05e5336d36a18583f0aa79f8dc0b1485ee5db33045df1014ae46a5360e Website Status recovered https://status.qlynk.me/ Sat, 03 Jan 2026 09:59:50 +0000 https://status.qlynk.me/#1e1c4874d8ea708d7f5537b5a02a21d600e10cb9092cdb8ae496b68d9823eb82 Our Backend Server went down https://status.qlynk.me/ Sat, 03 Jan 2026 09:59:46 +0000 https://status.qlynk.me/#6a160527f5aa45cc63adc25dfa292df1f3a7a9ab0234abdd818e6518b35ecbd3 Our Url Shortning Api went down https://status.qlynk.me/ Sat, 03 Jan 2026 09:59:44 +0000 https://status.qlynk.me/#8cf95d05e5336d36a18583f0aa79f8dc0b1485ee5db33045df1014ae46a5360e Website Status went down https://status.qlynk.me/ Sat, 03 Jan 2026 09:59:36 +0000 https://status.qlynk.me/#b16010d9292df835b32909e4c27b62745ce1836052fecc97557ecca914f76ccb Our Backend Payment Verification went down 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:29:00 -0000 https://status.qlynk.me/incident/797561#1c98aa270260ad9c88b1683594a5555c4112f2bed132b3e00aef6038c6dbf83b Qr Code Resolved 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:29:00 -0000 https://status.qlynk.me/incident/797561#1c98aa270260ad9c88b1683594a5555c4112f2bed132b3e00aef6038c6dbf83b Qr Code Resolved 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: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/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/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/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/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/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/ Fri, 02 Jan 2026 18:25:15 +0000 https://status.qlynk.me/#ec7e8785fc1e4b818fba892352e09d12109801a2b602b3592de4cd6fd377f806 Discord Bot Main recovered https://status.qlynk.me/ Fri, 02 Jan 2026 17:47:07 +0000 https://status.qlynk.me/#ec7e8785fc1e4b818fba892352e09d12109801a2b602b3592de4cd6fd377f806 Discord Bot Main went down https://status.qlynk.me/ Fri, 02 Jan 2026 17:41:26 +0000 https://status.qlynk.me/#3b9a434d70538ad92c51205cf2061e3f12a65d2b08a5865d511d65d077e286e0 Payment Gatway recovered https://status.qlynk.me/ Fri, 02 Jan 2026 17:38:09 +0000 https://status.qlynk.me/#3b9a434d70538ad92c51205cf2061e3f12a65d2b08a5865d511d65d077e286e0 Payment Gatway went down 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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