explorer
explorer copied to clipboard
explorer: Ping charts is misleading by RPC status
When RPC service has some issues, the ping status is misleading. The result can only reflect the user experience for the people who use the same RPC service with the ping chart but not the rest of users.
There were many " connect: connection refused " and "503-service-unavailable" errors contribute to high ping time in below chart .

If we can show RPC status in the chart, it helps users to know what causes those high bars.

How do we know this isn't actually an issue with the public RPCs?