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.

#

Incorrect HTTP Request type (e.g. using GET instead of POST) or Invalid Characters

#

This can happen when one or multiple security requirements are not met such as incorrect Token Auth, IP not in the whitelist, invalid JWT, etc.

#

Endpoint Disabled (One of the reasons for this could be a past due payment)

#

Custom trace code not whitelisted (Submit a ticket to go through the approval process)

#

Incorrect URL or Incorrect method

#

Body of the request is too large

#

Some methods may have limits to prevent overly large requests.

#

The requests per second (RPS) of your requests are higher than your plan allows. Learn more about the 429 errors in our support documentation.

#

Submit a ticket for the support team to take a look at the errors asap

#

Submit a ticket for the support team to take a look at the errors asap

HTTP Error Code Example

The code snippet below is an example of Error Code 429.

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

Quicknode RPC Error Codes

These error codes are returned by Quicknode's infrastructure (for example, rate limiting) and can appear on any chain regardless of the underlying node client.

Quicknode#

The endpoint exceeded its configured or plan-level per-second request allowance.

Diagnose and resolve

Why it happens

• The aggregate request rate crossed the per-second limit.

How to identify it

• Confirm Quicknode RPC code -32007 and correlate the timestamp with request-rate metrics.

How to resolve it

• Throttle the caller, cap concurrency, and spread burst traffic over time.
• Increase the applicable limit or plan capacity when the sustained request rate requires it.

Quicknode#

The endpoint exceeded its configured or plan-level per-minute request allowance.

Diagnose and resolve

Why it happens

• The aggregate request count crossed the rolling per-minute limit.

How to identify it

• Confirm Quicknode RPC code -32008 and compare the timestamp with request metrics over a full minute.

How to resolve it

• Queue or throttle requests so bursts remain below the per-minute allowance.
• Increase the applicable limit or plan capacity when the sustained request volume requires it.

Quicknode#

A method-specific rate-limit rule rejected the request.

Diagnose and resolve

Why it happens

• Calls to the named RPC method exceeded its configured limit.

How to identify it

• Confirm Quicknode RPC code -32011, then use Endpoint Logs to identify the method and matching rate-limit rule.

How to resolve it

• Reduce or cache calls to that method, or update the method rule if the traffic is expected.

Quicknode#

The request is missing required JSON-RPC envelope fields or has an invalid structure.

Diagnose and resolve

Why it happens

• The JSON-RPC envelope is incomplete—missing jsonrpc, method, or id fields.
• The request was routed to an internal parser that expects a different format.
• The method field is empty or missing.

How to identify it

• Confirm source Quicknode and code -32604; do not confuse it with standard JSON-RPC -32601 (method not found).
• Check if the error message mentions missing fields like jsonrpc, id, or type.

How to resolve it

• Include the complete JSON-RPC 2.0 envelope: jsonrpc, method, params, and id fields.
• Ensure jsonrpc is set to "2.0", method is a non-empty string, and id is present.

Quicknode#

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

Diagnose and resolve

Why it happens

• A method or request filter configured on the endpoint denied the request.

How to identify it

• Confirm source Quicknode and code -32611, then match the method and caller with the endpoint security rules.

How to resolve it

• Allow the request only if it is intended; otherwise keep the filter in place and correct the caller.

Quicknode#

The request exceeded a rate limit. This code may appear for method-specific or connection-based limits.

Diagnose and resolve

Why it happens

• The request rate for a specific method or connection exceeded the configured limit.

How to identify it

• Confirm source Quicknode and code -32029. Check the error message for retry timing.

How to resolve it

• Wait for the indicated retry period before sending another request.
• Reduce request frequency or implement exponential backoff.

Endpoint Logs

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.

Diagnose an Error From Its Log

Use the matching log entry to compare the request and response before changing your integration.

1. Filter to the smallest time window, method, and network that contain the failed request.
2. Check the HTTP status first. If the response body contains a JSON-RPC error object, record its code, message, and data separately.
3. Compare the logged request method and parameters with the method reference. For implementation-defined RPC codes, the message and data are required to identify the cause.
4. Keep the timestamp and request ID when escalating an issue, but redact endpoint tokens, authorization headers, private keys, and signed payloads that should not be shared.

Retention and Access

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

For service availability or active incidents, check the Quicknode Status Page.

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