Incidents | qlane Incidents reported on status page for qlane https://status.qlane.ai/ en qlane.ai recovered https://status.qlane.ai/ Mon, 08 Jun 2026 15:42:14 +0000 https://status.qlane.ai/#434b54fe01b3553bccd9530420dfd4cd36fa4cbf3be17c1d3696c3a6107dce97 qlane.ai recovered qlane.ai went down https://status.qlane.ai/ Mon, 08 Jun 2026 15:39:24 +0000 https://status.qlane.ai/#434b54fe01b3553bccd9530420dfd4cd36fa4cbf3be17c1d3696c3a6107dce97 qlane.ai went down eu.qlane.ai recovered https://status.qlane.ai/ Sat, 06 Jun 2026 19:14:36 +0000 https://status.qlane.ai/#a8eeef57fec9f9105f920cc04eda4330f7357ddb17e6e2990c4cb5a8a0169504 eu.qlane.ai recovered eu.qlane.ai went down https://status.qlane.ai/ Sat, 06 Jun 2026 19:06:18 +0000 https://status.qlane.ai/#a8eeef57fec9f9105f920cc04eda4330f7357ddb17e6e2990c4cb5a8a0169504 eu.qlane.ai went down eu.qlane.ai recovered https://status.qlane.ai/ Fri, 05 Jun 2026 19:33:11 +0000 https://status.qlane.ai/#526af28f1ed10d0f2b3db0de2604fc6a65aea37bfb42eb5f5a72d2a2e2517670 eu.qlane.ai recovered eu.qlane.ai went down https://status.qlane.ai/ Fri, 05 Jun 2026 19:27:12 +0000 https://status.qlane.ai/#526af28f1ed10d0f2b3db0de2604fc6a65aea37bfb42eb5f5a72d2a2e2517670 eu.qlane.ai went down US region brief outage — Cloudflare origin DNS error (530) 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. US region brief outage — Cloudflare origin DNS error (530) 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. US region brief outage — Cloudflare origin DNS error (530) 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. us.qlane.ai recovered https://status.qlane.ai/ Wed, 27 May 2026 12:07:10 +0000 https://status.qlane.ai/#681387a771f77e0de4e42ec329d399c85a5e20a69f4187414034bc5f846c11b8 us.qlane.ai recovered us.qlane.ai went down https://status.qlane.ai/ Wed, 27 May 2026 12:04:31 +0000 https://status.qlane.ai/#681387a771f77e0de4e42ec329d399c85a5e20a69f4187414034bc5f846c11b8 us.qlane.ai went down Investigating — application unavailable across all regions 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. us.qlane.ai recovered https://status.qlane.ai/ Wed, 20 May 2026 07:34:07 +0000 https://status.qlane.ai/#b65de7d397e18c07ad2d00f2d9b57d6d55007a459b41a0cd9d205d897c6f41b8 us.qlane.ai recovered Investigating — application unavailable across all regions 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. qlane.ai recovered https://status.qlane.ai/ Wed, 20 May 2026 02:17:59 +0000 https://status.qlane.ai/#b55b9d57da8d16245e4d48582347cc48665123d10339540770d1f75624bf4192 qlane.ai recovered eu.qlane.ai recovered https://status.qlane.ai/ Wed, 20 May 2026 01:36:23 +0000 https://status.qlane.ai/#2401ea9ae216bb7f5a824f42c09ca1021a2612c60d3d79fc932628a8f6144e4d eu.qlane.ai recovered Investigating — application unavailable across all regions 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. Investigating — application unavailable across all regions 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. Investigating — application unavailable across all regions 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. us.qlane.ai went down https://status.qlane.ai/ Tue, 19 May 2026 22:19:35 +0000 https://status.qlane.ai/#b65de7d397e18c07ad2d00f2d9b57d6d55007a459b41a0cd9d205d897c6f41b8 us.qlane.ai went down 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 eu.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