Contact
FREERPC.com is maintained by Tatum. For product questions, billing, or technical support for premium APIs, use the official Tatum channels below.
The public RPC gateway is best-effort infrastructure: check the status page during incidents, and use Discord when you need clarification on limits, supported networks, or integration patterns. Include chain name, network (mainnet or testnet), and a short example request when reporting unexpected errors so we can reproduce quickly.
For security-sensitive reports (for example suspected abuse of endpoints or credential leaks in sample code), prefer private channels described on tatum.io rather than posting secrets in public threads. See our privacy policy for how we handle any information you share when reporting an issue.
Response times vary by channel. Discord is best for how-to questions and peer discussion; the Tatum site routes you to documentation, sales, and account management; the status page is authoritative when an incident affects multiple regions or upstream providers. When you open a thread about a failing request, add the HTTP status, the approximate timestamp in UTC, and whether you were on mainnet or testnet. Those details cut triage time a lot.
None of this is a staffed help desk, so best-effort really does mean best-effort: response times vary, and they stretch further around a live incident when everyone is looking at the same logs. Beyond chain, network, and timestamp, the fastest reports also include the exact endpoint URL that was called and the raw error body the gateway returned, since a wallet’s own error message rarely shows the underlying JSON-RPC error.
If you already know what you need, you may not need to open a thread at all. Live incidents and planned maintenance are posted at status.tatum.io. Questions about what a specific method returns or which networks support archive reads are answered in full at docs.tatum.io. Everything else, from picking a chain to sizing a dedicated setup, fits the Discord community linked below better than a one-off message.
A handful of causes account for most contact threads, and are worth ruling out first. A 429 response means the free tier’s request-per-minute ceiling was hit, not that the gateway is unhealthy; back off and retry rather than opening a case. A connection that times out without ever returning an error is more often a corporate firewall or VPN blocking outbound HTTPS than anything on our side. A wallet that reports a transaction as failed while the RPC call itself returned a transaction hash successfully usually points to a contract-level revert on chain, which a block explorer will explain faster than we can from a URL alone. And a report that just says it stopped working, with no chain, network, or timestamp, is the hardest kind to act on, since the gateway answers for 67 chains and 198 interfaces at once. None of this replaces reporting a genuine outage. It just means the thread that does reach us is the one actually worth a person’s time to dig into.
If you are evaluating paid throughput, dedicated nodes, or custom SLAs, use the contact options on tatum.io so the right specialist can follow up. Mention expected requests per second, target chains, and whether you need archival data or standard full-node depth so we can recommend a realistic architecture.
Enterprise teams can also request private introductions to solutions engineering when you are comparing vendors or need a formal security questionnaire completed before procurement.
Before opening a new thread, a quick search in Discord often turns up the same question someone hit last week, since the same handful of networks and error codes account for most of what gets reported. And screenshots help less than they seem to: paste the actual request and response as text so someone can copy it straight into a terminal to reproduce it.