Developers · Status
Whether it is you or us.
Component-level status so an integration problem can be diagnosed in one place rather than through a support queue.
Current state
Operational
All components below, read from the same source as /api/status. Last read Wed, 16 Sep 2026 18:26:20 GMT.
- Raptor TerminalTrading surface and workspaces.Operational
- Market DataSnapshot and streaming price feeds.Operational
- ExecutionOrder management and the risk engine.Operational
- Client PortalOnboarding, verification and funding.Operational
- CRM & Back OfficeClient records and operations.Operational
- API — RESTVersioned JSON endpoints.Operational
- API — WebSocketStreaming channels.Operational
- API — FIXInstitutional session connectivity.Operational
- WebhooksEvent delivery and replay.Operational
Machine-readable at /api/status.
- What it is
- A status page covering the platform surface, market data, execution, client portal, CRM and API transports.
- Who it is for
- Developers and operations teams integrating with or depending on Raptor.
- Why it matters
- The first question during an incident is always the same, and it deserves a public answer.
- How it connects
- Status reflects the same monitoring that pages the on-call engineer.
- What happens next
- If a component is degraded and you need detail, contact support.
Reporting a problem
If something is broken and status says otherwise, tell us — that is the more serious bug. developers@777raptor.com