Link Checker Report: RPC Nodes & Providers Status

Hey guys! This is a link checker report for the awesome-list-rpc-nodes-providers project. We've run a check on all the links in the repository to make sure they're working correctly. Below, you'll find a summary of the results and a detailed breakdown of any errors we encountered. Let's dive in!

Summary of Link Status

Here's a quick overview of the link statuses:

In total, we checked 516 links. A good chunk, 228, came back successful, which is awesome! We had a few timeouts, and unfortunately, 56 links are throwing errors. Let's break down those errors to get a clearer picture.

Detailed Error Analysis

Errors in README.md

It looks like the majority of the errors are happening in the README.md file. Let's take a closer look at the specific links that are causing trouble.

• https://chainstack.com/build-better-with-filecoin/: Failed: Network error (status code: 404)
  • This link is returning a 404, meaning the page isn't found.
• https://getblock.io/nodes/arbitrum/: Failed: Network error (status code: 404)
  • Another 404 error, this time for an Arbitrum node link.
• https://docs.fantom.foundation/node/how-to-run-a-validator-node: Failed: Network error (status code: 404)
  • Fantom documentation link also resulting in a 404.
• https://maticvigil.com/: Failed: Network error (status code: 400)
  • A 400 error here, which usually indicates a bad request.
• https://docs.fuse.io/general-1/how-to-run-network-nodes: Failed: Network error (status code: 404)
  • Another 404 related to Fuse nodes.
• https://chainstack.com/build-better-with-near/: Failed: Network error (status code: 404)
  • Chainstack again, this time a 404 for a NEAR-related page.
• https://www.coinbase.com/blog/coinbase-cloud-launches-solana-archival-nodes-to-empower-the-solana: Failed: Network error (status code: 403)
  • A 403 error from Coinbase, meaning access is forbidden.
• https://juno.api.onfinality.io/public: Failed: Network error (status code: ERR)
  • A generic network error for the Juno API.
• https://fantom.api.onfinality.io/public: Failed: Network error (status code: 400)
  • Another 400 error for a Fantom API endpoint.
• https://blastapi.io/public-api/moonriver: Failed: Network error (status code: 404)
  • A 404 for a Moonriver API.
• https://bsc-dataseed.binance.org/: Failed: Network error (status code: 404)
  • A 404 for a Binance Smart Chain dataseed.
• https://app.infura.io/register: Failed: Network error (status code: 403)
  • A 403 from Infura, likely due to access restrictions.
• https://avalanche.api.onfinality.io/public: Failed: Network error (status code: 401)
  • A 401 error for an Avalanche API, indicating unauthorized access.
• https://bsc-dataseed1.defibit.io/: Failed: Network error (status code: 404)
  • Another 404 for a Binance Smart Chain dataseed.
• https://infura.io/: Failed: Network error (status code: 403)
  • Another 403 from Infura.
• https://moonbeam.public.blastapi.io/: Failed: Network error (status code: 400)
  • A 400 error for a Moonbeam API.
• https://www.infura.io/solutions/archive-access: Failed: Network error (status code: 403)
  • Yet another 403 from Infura, this time for archive access.
• https://www.infura.io/platform/nft-api: Failed: Network error (status code: 403)
  • Infura's NFT API also returning a 403.
• https://harmony.api.onfinality.io/public: Failed: Network error (status code: ERR)
  • Generic network error for the Harmony API.
• https://solana-api.projectserum.com/: Timeout (status code: TIMEOUT)
  • A timeout when trying to reach the Solana API.
• https://fuse.api.onfinality.io/public: Failed: Network error (status code: ERR)
  • Generic network error for the Fuse API.
• https://www.infura.io/networks: Failed: Network error (status code: 403)
  • Another 403 from Infura, this time for their networks page.
• https://bsc-dataseed1.ninicoin.io/: Failed: Network error (status code: 404)
  • A 404 for a Binance Smart Chain dataseed.
• https://multinodes.xyz/: Timeout (status code: TIMEOUT)
  • Another timeout.
• https://ethereumnodelight.app.runonflux.io/: Failed: Network error (status code: 503)
  • A 503 error, meaning the service is unavailable.
• https://docs.avax.network/build/tutorials/nodes-and-staking/run-avalanche-node: Failed: Network error (status code: 404)
  • A 404 for Avalanche node documentation.
• https://main-light.eth.linkpool.io/: Failed: Network error (status code: ERR)
  • Generic network error for an Ethereum endpoint.
• https://api.mycryptoapi.com/eth: Failed: Network error (status code: 403)
  • A 403 from MyCryptoAPI.
• https://datahub.figment.io/: Failed: Network error (status code: ERR)
  • Generic network error for Figment DataHub.
• https://zmok.io/: Failed: Network error (status code: ERR)
  • Generic network error for zmok.io.
• https://node.exaion.com/: Failed: Network error (status code: 404)
  • A 404 for node.exaion.com.
• https://public.stackup.sh/api/v1/node/arbitrum-one: Failed: Network error (status code: ERR)
  • Generic network error for a StackUp Arbitrum node.
• https://boba.network/start-here/#8: Failed: Network error (status code: 404)
  • A 404 for a Boba Network link.

Common Error Types

From the errors, we can see a few common themes:

• 404 Errors: Many links are returning 404 errors, meaning the page doesn't exist at the given URL. This could be due to the page being moved, deleted, or the URL being incorrect.
• 403 Errors: Several links are returning 403 errors, indicating that access is forbidden. This might be due to IP restrictions, rate limiting, or the content being behind a paywall.
• Generic Network Errors (ERR): These errors are a bit vague and could indicate a variety of issues, such as DNS resolution problems, server downtime, or network connectivity issues.
• Timeouts: A few links are timing out, suggesting that the server is taking too long to respond.

Next Steps

It's crucial to address these errors to ensure the awesome-list-rpc-nodes-providers project remains a valuable resource. Here's what we can do:

1. Verify 404 Errors: Check if the resources have moved and update the links accordingly. If the resources are permanently gone, consider removing the links.
2. Investigate 403 Errors: Determine if the access restrictions are intentional or if there's a way to access the content (e.g., through an API key).
3. Troubleshoot Generic Network Errors: Try accessing the links from different networks to rule out local connectivity issues. If the issue persists, it might be a problem with the target server.
4. Monitor Timeouts: If timeouts are frequent, it could indicate performance issues with the target server. Consider alternative resources if the problem persists.

Full Output

For a complete view of the link checking process, you can check out the Full Github Actions output.

Let's work together to fix these links and keep this list awesome!