qlane Outage History

qlane is up right now

qlane had 2 outages in the last 2 years totaling 9h 8m of downtime, averaging 0.1 incidents per month.

There were 2 qlane outages since May 19, 2026 totaling 9h 8m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.qlane.ai

Major September 18, 2026

Sign-in unavailable

Detected by Pingoru
Sep 18, 2026, 10:57 PM UTC
Resolved
Sep 18, 2026, 11:00 PM UTC
Duration
3m
Affected: EU region (Sign-in (eu.qlane.ai))US region (Sign-in (us.qlane.ai))
Timeline · 2 updates
  1. investigating Sep 18, 2026, 10:57 PM UTC

    Sign-in and sign-up are currently failing due to an outage at our third-party identity provider. The app itself is operating normally, and users who are already signed in are not affected — existing sessions continue to work. We are monitoring and will update when the provider restores service.

  2. resolved Sep 18, 2026, 11:00 PM UTC

    Resolved. Our identity provider restored service and sign-in and sign-up are working normally again in both regions, confirmed by direct checks. The disruption lasted about 18 minutes. Users who were already signed in were not affected at any point, and no data was affected. If you were unable to sign in during the disruption, please try again.

Read the full incident report →

Major May 19, 2026

Investigating — application unavailable across all regions

Detected by Pingoru
May 19, 2026, 10:30 PM UTC
Resolved
May 20, 2026, 07:36 AM UTC
Duration
9h 5m
Affected: Website & docs (Website (qlane.ai))
Timeline · 2 updates
  1. investigating May 19, 2026, 10:30 PM UTC

    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.

  2. resolved May 20, 2026, 07:36 AM UTC

    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.

Read the full incident report →