Skip to content

fix: drop dead RPC providers + add wave 7 chain pages - #1793

Merged
Flotapponnier merged 1 commit into
devfrom
feat/wave7-chain-pages
Aug 7, 2026
Merged

fix: drop dead RPC providers + add wave 7 chain pages#1793
Flotapponnier merged 1 commit into
devfrom
feat/wave7-chain-pages

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

Summary

  • Add wave 7 chain hub pages (fantom, kusama, hydration, zetachain, haqq, etherlink, chiliz, wemix, songbird, etc-classic, telos, pulsechain, warden, oraichain, peaq)
  • Remove dead RPC providers across 14 chains: DNS failures, 404s, paid-plan blocks, persistent 500s
  • Suspend hydration bench (all 5 providers unreachable)
  • Fix seo_intro/faq text to reflect accurate provider counts

Providers removed

ChainProviderReason
songbirdftso-auDNS dead
zetachainblockpi, allthatnode404 / DNS dead (1 provider left: Thirdweb)
telostelos-official404 (drpc remains)
cantodrpc, publicnode, ankr404 / 403 (canto-official remains)
auroraankr403 API key required
kaiadrpcpaid plan only
xdcdrpcpaid plan only
trondrpcmethod not available
ethereumcloudflare, gatewayfmJSONRPC -32603 / 503 persistent
astarpublicnode, blastapi404 / DNS dead
moonriverunitedblocDNS dead
seidrpcpersistent 500
ronindrpcpersistent 500
hydrationall 5DNS dead or HTTP 400 → suspended
warden/chilizdrpc404 Not Found

After merge

Rebuild the rpc-capabilities harness on Railway so it stops probing removed endpoints. UNRESPONSIVE badges will clear within 24h once Prometheus data rolls off.

@Flotapponnier
Flotapponnier merged commit 3a18a3c into devAug 7, 2026
1 check failed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@Flotapponnier