User-facing application
The landing site, registration, login, client portal, administrator portal, and public documentation routes are deployed. Availability can still be affected by hosting, database, DNS, email, or application incidents.
SERVICE HEALTH
Platform Status
A structured description of the deployed services, scheduled dependencies, incident-severity model, and information a production status page should communicate.
DeployedWebsite and portals
ExternalMarket-widget dependency
ScheduledReward processor
Self-reportedCurrent service status
Manual review queues
Deposit, withdrawal, KYC, and support states depend on administrator review. A reachable page does not mean every pending request has been processed.
Reward distribution
Reward blocks depend on a separately configured CLI cron process. Scheduler health, last-run time, failure state, and reconciliation should be monitored independently from web uptime.
External dependencies
- Hosting and DNS
- Email delivery
- Blockchain networks and wallet services
- TradingView market-data widgets
- User email providers and devices
How incidents should be classified
- OperationalA limited feature is slow or unavailable.
- DegradedA major workflow is affected but safe alternatives remain.
- MajorAuthentication, financial records, or broad availability is affected.
- SecurityConfidentiality, integrity, or unauthorized access may be involved.
What an incident notice should contain
- Detection time and affected services
- User-visible impact
- Actions users should avoid
- Mitigation and recovery status
- Resolution time and follow-up work
EXPLORE THE PLATFORM
Open free accountSee the operating system from the inside.
Create a free account without a funding obligation and review the available controls.