> ## Documentation Index
> Fetch the complete documentation index at: https://docs.goldsky.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot Boost

> Diagnose Boost cache misses, upstream errors, CORS failures, large batches, and organization verification issues.

## Common issues

| Symptom                                    | Likely cause                                                                | What to check                                                    |
| ------------------------------------------ | --------------------------------------------------------------------------- | ---------------------------------------------------------------- |
| `x-cache: MISS` on a fixed historical read | The data was not immediately available                                      | Retry once, then confirm the method and network are eligible     |
| Every request is a miss                    | The workload uses tags, state reads, writes, traces, or unsupported methods | Compare the request with [routing rules](/boost/how-it-works)    |
| JSON-RPC error for one network             | No active upstream is configured for that network                           | Open the network in the dashboard and activate an upstream       |
| Provider returns `401` or `403`            | Provider credential is missing, expired, or overridden                      | Check the upstream URL and configured headers                    |
| Browser preflight fails                    | The origin is not in **Allowed domains**                                    | Add the exact browser origin to the Boost endpoint               |
| A large batch never produces hits          | The array contains more than 100 items                                      | Split it into batches of 100 or fewer                            |
| WebSocket connection fails                 | Boost supports HTTPS only                                                   | Keep `wss://` and `eth_subscribe` pointed at your provider       |
| Provider IP allowlist rejects Boost        | Boost has no fixed egress IP list                                           | Authenticate with a URL or header credential, or contact support |

## Provider account connections

| Provider   | If connection or provisioning fails                                                                                                                                  |
| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| QuickNode  | Confirm the key has **Admin API** access and the account is on a paid plan                                                                                           |
| Alchemy    | Use an account access key with read-and-write **App Management** permission, not an app API key                                                                      |
| Chainstack | Use a Platform API key from Settings → API keys and check whether the plan's node limit has been reached                                                             |
| dRPC       | Use the **NodeCloud Keys API** token from Settings → API Tokens, then confirm the account has an active key without IP, origin, JWT, network, or method restrictions |

Boost reports unsupported or paid-only networks on the affected row. If the connected account cannot serve a network, add a custom HTTPS RPC URL for that network instead.

## Eligible requests keep missing

Confirm all of these conditions:

1. The network appears in the [supported network list](/boost/reference#supported-networks).
2. The method appears in [methods eligible for indexed data](/boost/how-it-works#methods-eligible-for-indexed-data).
3. Block parameters are concrete hexadecimal heights rather than tags such as `latest`.
4. `eth_getLogs` uses concrete `fromBlock` and `toBlock` values or a `blockHash`.
5. A batch has no more than 100 items.

An eligible request can still miss when Goldsky does not have that specific data. The request then forwards to your upstream.

## Organization verification

Boost requires a verified Goldsky organization.

A Goldsky organization is verified when at least one current Owner, Admin, or Editor has an email on a company domain. Generic email providers such as Gmail, Outlook, and Proton Mail do not qualify. Viewers do not count toward verification.

### If your organization is not verified

Add an Owner, Admin, or Editor with an email on your company's domain, then retry.

If your organization uses a shared domain you do not control, is still setting up company accounts, or believes a domain was misclassified, contact [support@goldsky.com](mailto:support@goldsky.com) or your shared Slack channel. Include the organization ID shown in the settings URL.

If verification is temporarily unavailable, retry and contact support if the problem persists.

## Getting help

Can't find what you're looking for? Reach out to us at [support@goldsky.com](mailto:support@goldsky.com) for help.


## Related topics

- [Boost reference](/boost/reference.md)
- [Set up Boost](/boost/quickstart.md)
- [Measure Boost traffic](/boost/observability.md)
- [Configure Boost upstreams](/boost/configuration.md)
- [Cut RPC costs with Boost](/boost.md)