Status Page and Incident Visibility

Where to find it

Open status.rivolq.com. The page is public, so your team can bookmark it even if they cannot sign in. It separates a local workspace issue from a broader platform incident.

What it shows

The top banner summarizes platform health and can show operational, maintenance, degraded, partial outage, or major outage, along with when status was last checked from live component checks and the public incident ledger. If the status feed cannot load, the page says status is temporarily unavailable; refresh before relying on it.

The component list shows named systems and their state, helping you narrow a report like Rivolq feels slow to a specific component. Active incidents show title, severity, affected components, summary, start time, and current status, with updates in the incident card. A history section covers public incidents from the recent 90-day window.

How to use it

1. 01Check status.rivolq.com before assuming a local configuration problem.
2. 02Compare the affected component with what your users see.
3. 03Avoid duplicate support tickets during an active incident unless you have new impact details.
4. 04If status is operational but your workspace still fails, capture the page, time, user, route, browser, and error details before contacting support.

The status page is not your audit log, activity feed, or entitlement page.