Quicknode provides Error Logs for your RPC endpoints. Easily identify and resolve issues by viewing detailed error information directly from your dashboard.

HTTP Error Codes

Let's look at the common HTTP errors you can encounter, what they mean and what you can do to prevent them.

400Bad Request

Incorrect HTTP request type (e.g. using GET instead of POST) or invalid characters

401Unauthorized

One or more security requirements not met such as incorrect token auth, IP not in whitelist, invalid JWT, etc

403Forbidden

Endpoint disabled (one reason could be a past due payment)

403Forbidden — custom trace not found in allowed custom traces

Custom trace code not whitelisted; submit a ticket to go through the approval process

404Not Found

Incorrect URL or incorrect method

413Content Too Large

Body of the request is too large

429Too Many Requests

The requests per second (RPS) of your requests are higher than your plan allows; see support docs for details

500Internal Server Error

Submit a ticket for the support team to investigate as soon as possible

503Service Unavailable

Submit a ticket for the support team to investigate as soon as possible

HTTP Error Code Example

{
  "jsonrpc": "2.0",
  "error": {
    "code": 429,
    "message": "The requests per second (RPS) of your requests are higher than your plan allows."
  },
  "id": 1
}

Solana RPC Error Codes

When working with Solana, understanding its API error codes is essential for effective troubleshooting and smooth application operation.

-32002Transaction simulation failed / preflight check errorRPC

The transaction being sent has errors; double check params, signatures, and message

-32002Blockhash not foundRPC

The blockhash sent is not known by the validator yet; implement a retry mechanism

-32003Transaction signature verification failureRPC

One or more signatures are invalid; verify private/public keys and signatures

-32004Block not available for slotRPC

Timeout or block not retrievable; use a retry mechanism

-32005Node is unhealthy / behind by slotsRPC

Node is behind the tip; retry with backoff or try another endpoint

-32007Slot was skipped or missing due to snapshot jumpRPC

Requested block does not exist; verify the slot in a block explorer

-32009Slot was skipped or missing in long-term storageRPC

The requested slot is missing from long-term storage; see support FAQ for details

-32010Key excluded from account secondary indexesRPC

Unexpected payload or incorrect data for the method; ensure request body matches validator expectations

-32013Transaction signature length mismatchRPC

Signature length is not as expected; re-encode or rebuild the transaction

-32014Block status not yet availableRPC

Block is pending or not yet synced; retry later

-32015Transaction version not supportedRPC

Use "maxSupportedTransactionVersion": 0 or upgrade client to support versioned transactions

-32016Minimum context slot not reachedRPC

The required context slot is too far in the future; lower the minimum context slot or retry later

-32602Invalid paramsRPC

Flags/params are invalid; double check method parameters against Solana docs

-32007Per-second request limit reachedQuicknode

You have exceeded your plan's per-second request limit. Reduce the number of calls per second or upgrade your plan at https://dashboard.quicknode.com/billing/plan.

-32008Per-minute request limit reachedQuicknode

You have exceeded your plan's per-minute request limit. Reduce the number of calls per minute or upgrade your plan at https://dashboard.quicknode.com/billing/plan.

-32011Method rate limit reachedQuicknode

You have exceeded a method-specific rate limit configured for the endpoint. Reduce calls to the method or adjust the method rate-limit rule.

-32604Unsupported request methodQuicknode

The request method is empty, missing, or unsupported. Provide a supported JSON-RPC method name.

-32611Request rejected by filter settingsQuicknode

The request was rejected by an endpoint security filter, such as a method allowlist or blocklist. Review the endpoint's request filter settings.

Solana RPC Error Code Example

{
  "jsonrpc": "2.0",
  "error": {
    "code": -32602,
    "message": "Invalid param: Invalid"
  },
  "id": 1
}

Endpoint

Quicknode provides logs for your RPC endpoints to help you diagnose issues. You can view logs directly in your Quicknode dashboard by navigating to:

1. Endpoints in the sidebar
2. Selecting your endpoint
3. Opening the Logs tab

You can filter logs by time window, response type, method, and network.

What Gets Logged

Endpoint Requests
Requests made to your endpoint, including the HTTP status, request method, RPC method or path, and timestamp.

Error Details
When available, failed requests include error details such as RPC error codes, request and response bodies, and links to related documentation.

Logging Limitations

Log availability can vary by method, response type, network, and plan. To maintain optimal endpoint performance, logging operates on a best-effort basis. Some logs may be dropped during high-traffic periods to preserve low latency.

Retention and Access

Build and Scale plans include dashboard access with standard log retention. Enterprise plans provide extended retention periods and programmatic API access for log retrieval.

If you're experiencing other error codes, please let us know by submitting a ticket. We're more than happy to assist