Checking your provider's status
Use Marketplace › Provide to follow each offering from verification to consumer traffic. Status applies to the offering: a problem with one network or capability does not tell you whether every other offering is working.
Follow qualification
After enabling an offering, open its status details to inspect the latest checks and their timestamps. Direct checks the service repeatedly before announcing it to consumers, so a successful upstream connection test does not make the offering immediately active.
| Status | Meaning | What to do |
|---|---|---|
| Checking | Initial verification is still running | Keep the node and client available; inspect any failed checks |
| Active | The offering has qualified and can be selected | Monitor request volume, errors, and response times |
| Unhealthy | Requests are failing or timing out | Check upstream reachability, node load, and synchronization |
| Integrity failed | Responses do not meet the advertised requirements | Inspect the failed capability or result and correct the cause |
| Paused | You have disabled the offering | Enable it when ready to resume checks and service |
Qualification is based on observed service over time, rather than a fixed waiting period. After fixing a failure, allow subsequent checks to establish recovery.
Resolve a failed check
Start with the failed request or capability shown in the offering's details. Repeat an equivalent request directly against the upstream from the machine running Direct.
| Symptom | Check |
|---|---|
| Connection refused or timeout | Node process, endpoint address, credentials, firewall, and load |
| Wrong chain | Upstream chain ID and the network selected for the offering |
| Historical uncle queries fail | Retained block/uncle history, including known pre-Merge uncle-containing blocks on Ethereum |
| Optional receipt or access-list checks fail | The affected method, required selectors, retained receipt data, and published budgets; ordinary baseline service can still qualify |
| Historical state missing | Mandatory recent-state coverage and detected archive-state capability |
| Historical blocks, transactions, receipts, or logs missing | Full chain history checks, retained data, and required lookup indexes |
| Trace or debug group fails | Required methods, tracers, options, and Direct’s tracing budgets; retained state or trace indexes when archive is also advertised |
| Stale blocks or inconsistent data | Node synchronization, peers, and any upstream caching layer |
Fix the node or correct the offering before returning it to service. A lower price cannot compensate for a failed integrity requirement. Qualifying providers explains what qualification establishes.
For tracing failures, repeat the specific failed method and options against your upstream. A working callTracer result does not establish prestateTracer support, and a recent trace does not establish historical coverage. Review the complete group requirements before re-advertising the capability.
Reference-block availability
If your offering is active but excluded from requests for the reference block, check that the node has reached that block and follows the expected chain. Inspect synchronization and recent block hashes before changing prices or capabilities.
Temporary routing exclusion does not by itself mean qualification has failed. Keeping providers eligible explains the distinction and the freshness policy.
Understand changes in traffic
An active offering can receive fewer requests when other providers offer a better price or response time. Compare recent latency, failures, and price before treating a drop in traffic as a connection problem.
Consumers also observe their own connections, so experience can differ by location and workload. Look at sustained behavior rather than one successful probe. Routing requests and handling failures explains how consumers choose among eligible offerings.
Change or pause an offering
Use the offering's settings to update its price, upstream, or capabilities. Changes to what it can serve need verification; inspect the resulting status before assuming the updated offering is available.
For maintenance, pause the offering before stopping the upstream. Consumers must recover interrupted requests or recreate subscriptions if their connections close. When the node is ready, enable the offering and follow its checks again.