polygon-rpc.com Down or Returning Errors?
If your Polygon app, bot, or MetaMask wallet suddenly started failing with HTTP 429 Too Many Requests, connection resets, or 504 Gateway Timeouts, your application is pointing to a decommissioned URL.
Why polygon-rpc.com Stopped Working
Polygon Labs officially decommissioned polygon-rpc.com and rpc-mainnet.polygon.technology on July 31, 2026.
Legacy tutorials, SDK defaults, and GitHub repositories still default to the retired public endpoint URLs.
Public community fallback mirrors fail under traffic spikes with connection resets, timeouts, or HTTP 429 rate limits.
Cloudflare rate limit gates placed in front of legacy mirrors immediately cut off automated scripts and bots.
Recommended Active RPC Replacement URLs
Public Community Mirror (Chainlist Verified)
Public fallback mirror listed on Chainlist with zero tracking.
BlazingNode Production RPC
Sub-40ms P95 latency, 300 to 500 RPS peak burst headroom, zero CU multipliers with x-api-key header.
2-Minute Migration Checklist
Verify your application .env file: search for `polygon-rpc.com` or `polygon.technology` and replace them immediately.
Check chain ID configuration: Polygon PoS Mainnet is Chain ID 137 (`0x89`), Native currency is POL (formerly MATIC).
Use verified endpoints listed on Chainlist (Chain 137) rather than unmaintained community public endpoints.
For high-volume production apps, bots, and indexers, switch to private dedicated bare-metal RPC to avoid public rate-limit drops.
// Test your new connection:
curl -X POST "https://public.blazingnode.com" -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'