CuteMarkets
System Status
Real-time health of the CuteMarkets API infrastructure.
Checking system status…
Services
API Endpoint
Query system health programmatically; no authentication required.
curl https://api.cutemarkets.com/v1/status/Returns status, services (each with status and latency_ms), and a request_id.
Interpreting status
Which API workflows each service can affect
Status checks are operational signals, not market-data advice. If a production workflow fails, check the affected service, capture the endpoint path, request ID, timestamp, and response code, then contact support with that context.
API gateway
If the gateway is degraded, authentication, request routing, or endpoint availability can be affected across chains, contracts, quotes, trades, and snapshots.
Database
Database issues can affect historical lookups, listed contracts, expiration discovery, and data-heavy queries that require stored market data.
Cache
Cache degradation can increase latency for repeated dashboard, chain, and snapshot workflows without necessarily indicating data loss.
When to contact support
Contact support when a status indicator is degraded and your request is failing, or when the page reports operational services but one endpoint is returning unexpected errors. Include the endpoint path, timestamp, HTTP status code, request ID, and whether the request involved chains, contracts, expirations, quotes, trades, aggregates, snapshots, account setup, billing, onboarding, support investigation, or incident review context.
For intermittent failures, capture two or three examples with timestamps rather than retrying silently; that makes it easier to separate network issues from endpoint-specific behavior.