Status
Status
Current Xpersona status posture: a reference model for room, data, API, billing, payout, and support incidents while production telemetry remains unconnected.
Telemetry feed
Not connected
Core systems
6 tracked
Current rows
Reference model
Desk expectation
Stop, verify, escalate
System rows
6| System | Benchmark |
|---|---|
| Trader portal | Xpersona plans to report homepage, dashboard, seat, billing, and review updates from one public status surface. |
| Trading workstation | Xpersona's options room is the operating center for account state, orders, and risk controls. |
| Market data | Real-time data access and add-on depth are explicit parts of the public product. |
| Webhook and API rail | Xpersona exposes a separate API lane and keeps hosted incidents distinct from member-local automation. |
| Payout and billing queue | Xpersona intends to treat payouts, resets, and rebills as explicit operating surfaces when those services are connected. |
| Support concierge | Xpersona currently provides self-service articles and stored Contact intake, not a staffed concierge system. |
Incidents
4Market-data degradation
Illustrative incident copy: identify which data lane is delayed, whether core quotes remain usable, and when the last monitored update occurred.
Webhook retries elevated
Illustrative incident copy: separate a hosted relay problem from member-local automation and tell users what evidence to preserve.
Member portal available
Illustrative incident copy: report unaffected services separately instead of implying that every Xpersona system shares one health state.
No live telemetry on this page
These rows are product examples, not a live incident log. Do not use them to decide whether an order path, market-data feed, or member service is currently healthy.
Timeline
4Operational
All public and member systems are serving normally. The page still shows the latest scheduled maintenance and the most recent resolved issue.
Monitoring
A nonfatal degradation exists in one lane such as advanced data, API relays, or payout processing, but the core room stays usable.
Investigating
The desk has enough evidence to acknowledge a problem publicly and is actively tracing it before asking traders to guess.
Resolved
The incident is closed, the timeline stays visible, and the desk makes clear what traders should verify before resuming normal behavior.
Policies
4When room behavior looks wrong, traders should stop fresh entries before they start troubleshooting.
A public status page should distinguish between full platform outages, degraded add-ons, and member-local automation problems.
Scheduled maintenance belongs on the same page as live incidents so traders learn one place to check first.
Status should link directly back to Help, Support, and the room evidence workflow instead of behaving like a dead-end notice board.