Details
Incidents — System incidents, outages, and critical events
Track and manage system incidents
Polymarket CLOB V2 Websocket Lag
Book updates delayed >15s — triggering RISK_BOOK_STALE_15S on multiple strategies
Impact
Book feed lag causing 9 demo-wired bots to emit RISK_BOOK_STALE_15S · Envelopes rejecting at elevated rate
Affected Components
DASH_CHIP_STALEBOOKGUARD · DASH_CHIP_MAKERTIGHT · DASH_CHIP_SMARTROUTER
Incident Timeline
2026-04-29 15:15:00 UTC
Partial recovery — book feed lag reduced to <5s. Monitoring in progress. RISK_BOOK_STALE_15S rejection rate dropping.
2026-04-29 14:45:00 UTC
Infrastructure team identified cause: Polymarket WS endpoint rate-limiting connections from our IP range. Mitigation underway — connection pool rotation.
2026-04-29 14:30:00 UTC
Alert fired on elevated RISK_BOOK_STALE_15S reason codes across all 9 demo-wired bots. Envelopes queuing but not executing.
2026-04-29 14:23:00 UTC
CLOB V2 websocket feed degraded — book updates delayed >15s. INC-001 opened. EXEC_ROUTE_CTFV2_TIMEOUT observed on 3 orders.
EIP-712 v2 Signing Timeout on exec.smartrouter
Intermittent signing delays >500ms — 3 orders failed with EXEC_BUILDERCODE_MISSING
Why this matters
Incidents are named after V2 infrastructure components, not operator names. Every timeline entry references a reason code so the audit trail is machine-readable. demo-wired ≠ production-live.