When something looks wrong with Relm Pro, the first place to check is our status page. It shows real-time system health and any active incidents.
Where to find it
/status — bookmark it.
The status page covers:
- Web app (relm.ai) — the main UI.
- Excel add-in — the taskpane web bundle and APIs.
- Deep Research — the agent platform.
- Document indexing — the OCR + embedding pipeline.
- Chat / AI — the chat panel runtime.
- Authentication — sign-in and session management.
Each component has a status pill: Operational, Degraded, Outage, or Maintenance.
What "Degraded" vs "Outage" means
- Degraded — the component works but slower or with elevated error rates. Most users experience some impact.
- Outage — the component isn't working. Most users can't use the affected features.
- Maintenance — planned downtime, announced ahead of time.
Active incidents
If there's an active incident, the page shows:
- A short title.
- Affected components.
- A timestamped log of updates.
- Estimated time to restoration when we have one.
We update the log every 15–30 minutes during active incidents.
Past incidents
The status page archives past incidents with their full timeline and post-mortem (when published). Useful if you're trying to understand whether a behavior you saw last Tuesday was related to a known issue.
Subscribing to notifications
Click Subscribe on the status page. Options:
- Email — notifications when incidents start, update, and resolve.
- SMS — for critical-priority incidents only.
- Webhook — POST notifications to a URL of your choice (works with most chat platforms).
- RSS — for incident-tracking systems.
Subscriptions are scoped per component, so you can subscribe only to "Excel add-in" if that's what your team cares about.
When the status page itself is down
The status page is hosted independently of relm.ai and rarely goes down with the main service. If you can't reach the status page either, that's an unusual circumstance; check our X (formerly Twitter) account @relmai for updates.
Reporting a bug while there's an active incident
If you're experiencing an issue and an active incident is posted that matches your symptoms, you don't need to report — we know. Wait for resolution.
If your issue doesn't match any active incident and persists, report it as a bug.