Incidents reported on status page for qlane https://status.qlane.ai/ en https://status.qlane.ai/incident/975898 Fri, 24 Jul 2026 02:05:00 -0000 https://status.qlane.ai/incident/975898#2f1e210f0604ba1df74241d92064b6c705f4490491ef60b253062cb241d320d4 Maintenance completed https://status.qlane.ai/incident/975898 Fri, 24 Jul 2026 01:35:00 -0000 https://status.qlane.ai/incident/975898#90601951ebfdb4d0b7040412f3e2436f326411fe92e7914552726b06f3d6d05e We're performing scheduled maintenance on the qlane app. During this window eu.qlane.ai and us.qlane.ai will be briefly unavailable and test sessions won't start. No action is needed on your part — we'll post an update here as soon as everything is back. https://status.qlane.ai/ Wed, 22 Jul 2026 01:59:58 +0000 https://status.qlane.ai/#77b12187c44f2869bc98cb3d8ae65a6c79ea6a5a916090cac93c6848ce07b330 qlane.ai recovered https://status.qlane.ai/ Wed, 22 Jul 2026 01:57:33 +0000 https://status.qlane.ai/#77b12187c44f2869bc98cb3d8ae65a6c79ea6a5a916090cac93c6848ce07b330 qlane.ai went down https://status.qlane.ai/ Thu, 16 Jul 2026 10:09:53 +0000 https://status.qlane.ai/#660ee2bed141263020421781ae38124da1263cf4ddc67ff5ba85dbb2b5f1bb44 us.qlane.ai recovered https://status.qlane.ai/ Thu, 16 Jul 2026 10:08:48 +0000 https://status.qlane.ai/#c6bcda350bfec0115f4228ef8e4411e15b5162fac1636e35fec15dc670785f8f eu.qlane.ai recovered https://status.qlane.ai/ Thu, 16 Jul 2026 08:04:59 +0000 https://status.qlane.ai/#660ee2bed141263020421781ae38124da1263cf4ddc67ff5ba85dbb2b5f1bb44 us.qlane.ai went down https://status.qlane.ai/ Thu, 16 Jul 2026 08:04:02 +0000 https://status.qlane.ai/#c6bcda350bfec0115f4228ef8e4411e15b5162fac1636e35fec15dc670785f8f eu.qlane.ai went down https://status.qlane.ai/incident/941435 Thu, 02 Jul 2026 09:05:25 -0000 https://status.qlane.ai/incident/941435#b087d56ce51d331c397adfd9e4167fa4a87dc283d41e5caf1122dca8757221be Resolved: The upstream network provider issue affecting our US region (us.qlane.ai) has been mitigated. The US region has been serving normally since ~09:00 UTC, and we've confirmed sustained stability. All regions are now fully operational. Thanks for your patience. https://status.qlane.ai/ Thu, 02 Jul 2026 09:01:08 +0000 https://status.qlane.ai/#32a0939eae36efaabc4de8d368987c68943a55bf87b1aed016017d04cdcdb44e us.qlane.ai recovered https://status.qlane.ai/incident/941435 Thu, 02 Jul 2026 09:01:06 -0000 https://status.qlane.ai/incident/941435#eddba66b44b2535616be97a7d7cee29a5f86798ca20284a42ea6a7d34f9c801e Update: Our US region (us.qlane.ai) is coming back online and the application is responding normally again. Some US users may still see occasional errors or timeouts while the upstream network provider finishes stabilizing. We're monitoring closely and will confirm once it's fully back to normal. https://status.qlane.ai/incident/941435 Thu, 02 Jul 2026 08:58:36 -0000 https://status.qlane.ai/incident/941435#2b6008169aa3299a24a5653c7b1169dce2d6655b5a1955d8d443f11164738b9e We're aware of an issue making our US region (us.qlane.ai) unavailable for some users. It's caused by a connectivity problem at an upstream network provider affecting the US — not an issue with the application itself. Our EU region (eu.qlane.ai) and the main site (qlane.ai) are operating normally, so EU users are unaffected. Mitigation is underway with the provider, and we'll post updates here as the situation develops. https://status.qlane.ai/ Thu, 02 Jul 2026 08:37:07 +0000 https://status.qlane.ai/#32a0939eae36efaabc4de8d368987c68943a55bf87b1aed016017d04cdcdb44e us.qlane.ai went down https://status.qlane.ai/ Mon, 08 Jun 2026 15:42:14 +0000 https://status.qlane.ai/#434b54fe01b3553bccd9530420dfd4cd36fa4cbf3be17c1d3696c3a6107dce97 qlane.ai recovered https://status.qlane.ai/ Mon, 08 Jun 2026 15:39:24 +0000 https://status.qlane.ai/#434b54fe01b3553bccd9530420dfd4cd36fa4cbf3be17c1d3696c3a6107dce97 qlane.ai went down https://status.qlane.ai/ Sat, 06 Jun 2026 19:14:36 +0000 https://status.qlane.ai/#a8eeef57fec9f9105f920cc04eda4330f7357ddb17e6e2990c4cb5a8a0169504 eu.qlane.ai recovered https://status.qlane.ai/ Sat, 06 Jun 2026 19:06:18 +0000 https://status.qlane.ai/#a8eeef57fec9f9105f920cc04eda4330f7357ddb17e6e2990c4cb5a8a0169504 eu.qlane.ai went down https://status.qlane.ai/ Fri, 05 Jun 2026 19:33:11 +0000 https://status.qlane.ai/#526af28f1ed10d0f2b3db0de2604fc6a65aea37bfb42eb5f5a72d2a2e2517670 eu.qlane.ai recovered https://status.qlane.ai/ Fri, 05 Jun 2026 19:27:12 +0000 https://status.qlane.ai/#526af28f1ed10d0f2b3db0de2604fc6a65aea37bfb42eb5f5a72d2a2e2517670 eu.qlane.ai went down https://status.qlane.ai/incident/906464 Wed, 27 May 2026 12:14:19 -0000 https://status.qlane.ai/incident/906464#2f7c0f6fcca679d23ca247c45e7d34dea5ca60e3acc4713761230e36ca0e144b Service has fully recovered. The disruption was caused by a transient Cloudflare DNS resolution error affecting the US region for approximately 5 minutes (12:04–12:09 UTC). No data loss or user action required. https://status.qlane.ai/incident/906464 Wed, 27 May 2026 12:10:45 -0000 https://status.qlane.ai/incident/906464#34fa7528efdf43e1d4d54631b35a992f61fb8feded6a15271d7476d5edbf6584 Service has fully recovered. The Cloudflare origin DNS error (530) was transient and originated from Cloudflare's Sydney edge node. The underlying Railway application was never down — health checks, database, Redis, and all background workers remained operational throughout. Total disruption window was approximately 5 minutes (12:04–12:09 UTC). No user action required. https://status.qlane.ai/incident/906464 Wed, 27 May 2026 12:09:54 -0000 https://status.qlane.ai/incident/906464#d77493cc30ab2bff2ec77d318bad8fb897bf8da5a8dab6d1b1c4f3957f2da8ee We detected a brief disruption to us.qlane.ai at 12:04 UTC caused by a Cloudflare origin DNS resolution error (HTTP 530). The underlying application remained healthy throughout — database, Redis, and all worker processes were unaffected. The issue self-resolved within minutes. We are monitoring to confirm full stability. https://status.qlane.ai/ Wed, 27 May 2026 12:07:10 +0000 https://status.qlane.ai/#681387a771f77e0de4e42ec329d399c85a5e20a69f4187414034bc5f846c11b8 us.qlane.ai recovered https://status.qlane.ai/ Wed, 27 May 2026 12:04:31 +0000 https://status.qlane.ai/#681387a771f77e0de4e42ec329d399c85a5e20a69f4187414034bc5f846c11b8 us.qlane.ai went down https://status.qlane.ai/incident/900103 Wed, 20 May 2026 07:36:00 -0000 https://status.qlane.ai/incident/900103#35295148bd56117fdbbe89975637b38908ef1c214801dd4b32dab2ce2f1696da **Resolved — service fully restored** All QLane endpoints are healthy. The incident is resolved. The root cause was a major service disruption at our upstream hosting platform; QLane's own application code and data were unaffected. Thanks for your patience. https://status.qlane.ai/ Wed, 20 May 2026 07:34:07 +0000 https://status.qlane.ai/#b65de7d397e18c07ad2d00f2d9b57d6d55007a459b41a0cd9d205d897c6f41b8 us.qlane.ai recovered https://status.qlane.ai/incident/900103 Wed, 20 May 2026 02:28:40 -0000 https://status.qlane.ai/incident/900103#1908d210d1ae35e0389c4cd6ed9a35673b30599e303f2a9110c92ae497ce9baf **Monitoring — service partially restored, observing stability** Our hosting platform has restored service for EU and we are observing healthy responses. The US region is still in recovery. We're monitoring for stability across all regions and will mark this incident resolved once we've confirmed sustained recovery on all endpoints. QLane's application code and data were unaffected throughout. https://status.qlane.ai/ Wed, 20 May 2026 02:17:59 +0000 https://status.qlane.ai/#b55b9d57da8d16245e4d48582347cc48665123d10339540770d1f75624bf4192 qlane.ai recovered https://status.qlane.ai/ Wed, 20 May 2026 01:36:23 +0000 https://status.qlane.ai/#2401ea9ae216bb7f5a824f42c09ca1021a2612c60d3d79fc932628a8f6144e4d eu.qlane.ai recovered https://status.qlane.ai/incident/900103 Wed, 20 May 2026 00:32:00 -0000 https://status.qlane.ai/incident/900103#08f54543eaf954dbe5598c5a785b67e8cf672ef29c7253a4760cded447ca7602 **Still investigating — extended outage** Our hosting provider, [Railway](https://railway.com), is experiencing a major service disruption affecting their platform. Their engineering team is actively working with their own upstream infrastructure provider to restore service. You can follow their progress at https://status.railway.com — they have not provided an ETA. All QLane endpoints remain unavailable. QLane's application code and data are not affected by this outage. We'll post another update when service is restored. https://status.qlane.ai/incident/900103 Tue, 19 May 2026 22:35:06 -0000 https://status.qlane.ai/incident/900103#cf044c2595f2e13903b56826b0bd248ab8c620b5cf66ef7f0c04da4d7e8113e0 **Identified — upstream platform outage** The cause is a major service disruption affecting our hosting platform. The platform's engineering team is actively investigating. All QLane endpoints will remain unavailable while their team works on recovery. QLane's application code and data are not affected. We'll post another update as soon as service is restored. https://status.qlane.ai/incident/900103 Tue, 19 May 2026 22:30:59 -0000 https://status.qlane.ai/incident/900103#5f8be3015f46264c8899d15aee400eefdcce2af6f1d3dd1922fa06e3584b4fb0 We're aware that QLane endpoints (qlane.ai, eu.qlane.ai, us.qlane.ai, app.qlane.ai) are currently unreachable. We're investigating the root cause and will post an update once we have more information. No data has been lost. https://status.qlane.ai/ Tue, 19 May 2026 22:19:35 +0000 https://status.qlane.ai/#b65de7d397e18c07ad2d00f2d9b57d6d55007a459b41a0cd9d205d897c6f41b8 us.qlane.ai went down https://status.qlane.ai/ Tue, 19 May 2026 22:18:32 +0000 https://status.qlane.ai/#b55b9d57da8d16245e4d48582347cc48665123d10339540770d1f75624bf4192 qlane.ai went down https://status.qlane.ai/ Tue, 19 May 2026 22:18:11 +0000 https://status.qlane.ai/#2401ea9ae216bb7f5a824f42c09ca1021a2612c60d3d79fc932628a8f6144e4d eu.qlane.ai went down