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

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.

403Forbidden

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

403Forbidden - custom trace not found

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

413Request 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.

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

500Internal Server Error

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

503Service 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
}

Starknet RPC Error Codes

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

1Failed to receive transactionRPC

Sequencer rejected the transaction during validation. Verify transaction format and required fields

10No trace availableRPC

Trace data not available for the transaction. Verify the transaction hash is correct and exists on the network

20Contract not foundRPC

The specified contract address does not exist on the network

21Invalid message selectorRPC

Function selector does not exist in the contract ABI

22Invalid call dataRPC

Calldata is malformed or contains invalid parameters. Verify parameter types and encoding

24Block not foundRPC

The requested block does not exist. Check block number/hash or wait for sync

26Invalid block hashRPC

Block hash format is invalid. Ensure it's a valid hexadecimal string with correct length

27Invalid transaction indexRPC

Transaction index is out of range for this block

28Class hash not foundRPC

The specified class hash has not been declared on the network

29Transaction hash not foundRPC

No transaction found with the provided hash

31Page size too bigRPC

Page size exceeds the maximum allowed limit.

32No blocksRPC

No blocks available in the specified range

33Invalid continuation tokenRPC

The continuation token is invalid or has expired

34Too many keys in filterRPC

Filter contains more keys than the maximum allowed

40Contract errorRPC

An error occurred during contract execution

41Transaction execution errorRPC

Transaction failed to execute. Check contract logic and resource limits

51Class already declaredRPC

Class already exists on the network. Duplicate declarations are not allowed

52Invalid transaction nonceRPC

Invalid nonce for the account. Use the correct sequential nonce value

53Insufficient max feeRPC

Max fee too low. Increase the fee to cover transaction costs

54Insufficient account balanceRPC

Account balance too low. Ensure sufficient funds to cover the transaction fee

55Validation failureRPC

Account validation failed. Check your signature and account contract logic

56Compilation failedRPC

Contract compilation failed. Fix Cairo code syntax and compilation errors

57Contract class size is too largeRPC

Contract class too large. Reduce the contract size to fit within network limits

58Non accountRPC

Sender is not an account contract. Only account contracts can send transactions

59Duplicate transactionRPC

Transaction already exists in mempool. Avoid submitting duplicate transactions

60Compiled class hash mismatchRPC

The compiled class hash does not match the declared hash

61Unsupported transaction versionRPC

Transaction version not supported. Use a compatible transaction version

62Unsupported contract class versionRPC

Contract class version not supported. Use a compatible Cairo compiler version

63Unexpected errorRPC

Unexpected server error occurred. Submit a ticket if the issue persists

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

Starknet RPC Error Code Example

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

{
  "error": {
    "code": 20,
    "message": "Contract not found"
  },
  "id": 1,
  "jsonrpc": "2.0"
}

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.

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