Probable fetchOHLCV returns 503/500 — upstream API flakiness

[realfishsam]

Summary

The Probable /public/api/v1/prices-history endpoint is returning 503 (22 occurrences) and 500 (2 occurrences) errors over the last 24h, causing 100% failure rate on fetchOHLCV for the Probable venue.

Details

• Endpoint: GET /public/api/v1/prices-history
• Error mapping: error-mapper.ts correctly translates upstream 503/500 → ExchangeNotAvailable
• Impact: All 24 probable/fetchOHLCV requests in the last 24h failed
• Compliance tests: Already skip gracefully on upstream server errors

Observed in production (hosted-pmxt)

/probable/fetchOHLCV | 24 requests | 100% error rate | 22×503, 2×500

Suggested action

• Monitor whether this is transient or persistent
• If persistent, consider surfacing a clearer user-facing message (e.g., "Probable OHLCV data temporarily unavailable") rather than passing through the raw 503
• Optionally add a circuit breaker or cached fallback for known-flaky endpoints