Relm API + MCP.

Status & incidents

Status page & subscribing to incidents

Where to check if Relm Pro is having an outage, and how to be notified next time it does.

Relm TeamUpdated 3 min read
On this page

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:

  • Dashboard — the web app and user interface.
  • API — the backend services behind the app.
  • AI Research Engine — Deep Search and property analysis agents.
  • Financial Analysis — pro-forma generation and financial modeling.
  • Chat Assistant — the AI chat analyst.
  • Document Intelligence — document upload, OCR, and indexing.
  • Authentication — sign-in and user management.
  • Payments — billing and subscription management.

Each service shows a status — Operational, Degraded, Partial Outage, Major Outage, or Under Maintenance — plus an uptime bar for the last 90 days.

What the statuses mean

  • Degraded — the service works but slower or with elevated error rates. Most users experience some impact.
  • Partial Outage / Major Outage — the service isn't working for some or all users. Affected features may be unavailable.
  • Under Maintenance — planned downtime, announced ahead of time.

Active incidents

If there's an active incident, the page shows:

  • A short title and its current state — Investigating, Identified, Monitoring, or Resolved.
  • A timestamped log of updates (times are in UTC).
  • Estimated time to restoration when we have one.

The affected services also show a non-green status in the list.

We update the log about every 30 minutes during active incidents.

Past incidents

The status page lists incidents from the last 90 days with their full timeline of updates. Useful if you're trying to understand whether a behavior you saw last Tuesday was related to a known issue.

Subscribing to notifications

Under "Get notified when something changes," pick how you want to hear about incidents:

  • Email — a message when an incident starts and when it's resolved.
  • Slack — the same alerts, posted into a Slack channel. You'll paste an incoming-webhook link from Slack.
  • Webhook — the same alerts, sent automatically to a web address your team provides, so your own tools can react.
  • RSS — a feed for feed readers and incident-tracking systems.
  • JSON API — the current status in machine-readable form, for your own dashboards.

Subscriptions cover every service — you can't limit them to a single one.

When the status page itself is down

The status page runs on relm.ai, so a major outage can take it down along with the app. If you can't reach it, check our X (formerly Twitter) account @relm_ai for updates, or email support@relm.ai.

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.

What's next

Was this article helpful?

Still need help?

Our team usually responds within one business day. Tell us what you're trying to do and we'll get you unstuck.

Relm Pro Help Center