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.

400

Bad Request

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

401

Unauthorized

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.

403

Forbidden

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

403

Forbidden - custom trace not found

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

404

Not Found

Incorrect URL or Incorrect method

413

Content Too Large

Body of the request is too large

413

Request Entity Too Large

eth_getLogs and eth_newFilter are limited to a 10,000 blocks range. We enforce a limit of 10,000 block ranges when requesting logs and events.

429

Too Many 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.

500

Internal Server Error

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

503

Service Unavailable

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
}

Endpoint Error Logs

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

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

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

What Gets Logged

RPC Errors
All failed requests including invalid methods, malformed parameters, execution errors, and network timeouts.

Failed Transaction Submissions
Send transaction requests that failed. Successful transactions are logged separately in the Transaction Logs tab.

Logging Limitations

Only RPC errors and failed transaction submissions are logged — successful read operations are not captured. 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