> For the complete documentation index, see [llms.txt](https://nytshift.gitbook.io/nytshift-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nytshift.gitbook.io/nytshift-docs/market-data-and-providers/provider-divergence.md).

# Robinhood Chain provider divergence

1. Keep affected network, price and portfolio contexts unavailable. Do not race providers or select the more favorable value.
2. Capture the typed `PROVIDER_DIVERGENCE` state from `/api/rhc/providers` with provider labels, chain IDs, block heights, HTTP error/p95 windows, WSS state and observation time. Correlate it with `/api/rhc/providers/incidents?limit=50`; the durable record contains only coarse roles, reason codes, thresholds and timestamps. Never record credentials, sensitive headers or complete wallet histories.
3. Check each provider independently for chain ID `4663`, block progress, status incidents, throttling and stale caches.
4. Remove a provider from service only through reviewed server configuration; request data cannot supply a replacement URL.
5. Confirm both WSS transports have verified chain ID 4663, acknowledged `newHeads` and delivered fresh heads. A configured URL alone is not recovery evidence.
6. Restore production readiness only after chain identity matches, block divergence remains within policy and the uninterrupted stabilization window completes.
7. Review any affected cached context. A fallback can restore availability but cannot loosen address, round, freshness, sequencer or pause validation.
8. Confirm the active divergence/failover alerts emitted one `alert-resolved` transition. If history health is unavailable, preserve `rhc-provider-observability-v1.json`, stop the runtime and follow the local store recovery procedure instead of deleting it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://nytshift.gitbook.io/nytshift-docs/market-data-and-providers/provider-divergence.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.