The status page

status.qorionix.com (opens in a new tab) is a dedicated page: that address shows only the status page, nothing else. For a period it did not — a hostname-routing gap meant anyone who typed status.qorionix.com was served the ordinary marketing site instead, because nothing in the delivery layer looked at which hostname a request came in on. That is fixed. The address now serves its own minimal page: a small header, the status content, and a link back to qorionix.com — no site navigation, no marketing chrome.

The page refreshes on its own every 60 seconds. It shows the current state of each platform component and a list of past incidents. If the status feed itself cannot be reached, the page says so in plain words rather than showing a blank or stale screen.

Check this page before opening a support ticket about something that looks broken for your whole organisation at once — see How to get help, and what we need from you. If the page is clear and the problem is still there, that is useful information worth saying explicitly in your ticket.

Reporting a problem that the page does not explain

Record when the problem started, which action failed, and whether other people in your organisation can reproduce it. Include the affected page and any reference code shown by the console. A healthy component status does not establish that your account permissions, identity provider, network connection or individual connector are working. Those details help support distinguish a platform incident from a problem limited to your organisation.

If the status page cannot retrieve its feed, report that observation separately from the original failure. Do not interpret an unavailable feed as either a confirmed outage or confirmation that everything is healthy. Check again after the next refresh and keep the original failure time in your support request.