Status

status.qlyne.com shows whether each part of Qlyne is answering, with the last 90 days. It runs on a separate server from the one that serves Qlyne, so it stays up when Qlyne does not. Checks run every minute. The page follows your browser’s language, English or Portuguese, and ?lang=en or ?lang=pt picks one.

The four parts

Part	What it covers
Dashboard	Sign-in, settings and reports
API and connectors	What your connector talks to: rules, reports and the waiting room
Edge protection	The protected demo site and the proxy download
Website and docs	qlyne.com and this documentation

Each part says Operational or Outage, and an outage shows since when. A part is down when any of its checks failed in the last round. The banner at the top follows the worst part: “All systems operational” or “Some systems are experiencing issues”.

Reading the 90 days

Each part has one bar per day, today on the right:

• green: no failed check that day;
• amber: some checks failed, less than 5% of the day’s rounds;
• red: 5% of the rounds or more failed;
• grey: no data, the page was not checking yet.

Hover over a bar to see the day, its uptime and how many checks failed. The uptime percentage counts from the first day with data, which the page states (“since” and the date). The page went up on 18 October 2026, so until 90 days have passed the percentage covers fewer days, and a short history says little.

Incidents

When something goes wrong, an incident shows up under Incidents, with the affected parts, when it started and each update. Updates move through Investigating, Identified, Monitoring and Resolved. While an incident is open it says Ongoing, and the banner turns to “Incident in progress” even if every check is green. Incidents from the last 90 days stay on the page.

Incidents are written by hand, so a red bar can show up before its incident does.

For your tools

https://status.qlyne.com/status.json returns the same state as JSON: the overall status (ok, down, or unknown before the first round), each part with its days and uptime, and the incidents. Any page or script can read it.

When Qlyne is down

What happens to your site depends on how it connects:

• With the Qlyne proxy, the Cloudflare Worker or the Next.js middleware, the connector runs on your side. It keeps the last signed rules it received and goes on applying them for up to 72 hours. Without valid rules, it lets traffic through instead of blocking your visitors.
• With hosted, your traffic goes through Qlyne’s proxy. If Edge protection is down, your site may be unreachable too.

The dashboard being down stops changes to your rules and the reports, not the protection itself.

Limits

• There is no e-mail or RSS subscription yet. Check the page, or read status.json from your own monitor.
• The checks look at Qlyne’s own services, not at your site. To know whether your site answers, keep your own uptime monitor.