Guides
SupportStatusSign UpLogin

RPC - Troubleshooting RPC requests and Tatum

Suggest Edits

Tatum provides access to multiple blockchain networks through RPC (Remote Procedure Call) nodes, empowering developers and businesses to seamlessly interact within blockchain ecosystems. Our commitment is ensuring nodes are continuously up-to-date, highly available, and optimized for smooth blockchain integration and reliable performance.

Understanding RPC Response Times and Performance

RPC response times vary based on multiple factors, including blockchain network status, request complexity, and resource demands:

  • Lightweight Requests: Queries like simple EVM balance checks or basic transaction lookups usually respond swiftly due to minimal computational overhead.
  • Complex Requests: More intensive operations such as debug or trace calls can experience longer response times, often taking several seconds. These calls involve detailed blockchain data processing and extensive historical data retrieval, thus requiring significant node resources.

Important Limitations of Tatum's Control

While we strive to provide optimal service quality, it's important to understand certain limitations outside of our control:

  • Blockchain Source Code:
    Tatum does not own or influence the blockchain source code. Blockchains operate according to their independent protocols and version updates maintained by their dedicated development communities.
  • Blockchain Network Behavior:
    Issues like network congestion, unexpected transaction delays, or sudden protocol changes reflect the inherent decentralized nature of blockchain networks, and Tatum has no direct influence or control over such events.

Scope of Tatum's Troubleshooting

Our support approach prioritizes infrastructure-specific issues while clearly defining boundaries for non-infrastructure concerns:

Here's a breakdown of what this means:

  • Infrastructure-Related Issues:
    If problems occur with Tatum infrastructure, such as node downtime, connectivity disruptions, or significant performance degradation, our support team is ready and equipped to troubleshoot and resolve these concerns promptly.
  • Non-Infrastructure-Related Issues:
    Issues caused by blockchain-specific behaviors, including invalid transactions, network errors, protocol-level changes, or blockchain network congestion, are outside the scope of Tatum support.

📘

Note

For specifics on troubleshooting RPC requests, we recommend reaching out to Chain Consortium's Developer docs and leveraging their community resources.

Relevant Blockchain GitHub Resources

Internal Node Health Checks and Known Limitations

Tatum implements internal health checks designed to monitor RPC node status relative to blockchain tip progression. Nodes are permitted to lag slightly behind (typically up to 60–120 seconds). Beyond this threshold, our system flags the node as unhealthy to temporarily reduce load and allow node synchronization with the network tip.

This lag is expected behaviour and a known limitation designed to optimize overall node health and operational stability.

Updated 1 day ago