<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Low-Latency-Rpc on BLAZED.sh Blog</title>
    <link>https://blazed.sh/blog/tags/low-latency-rpc/</link>
    <description>Recent content in Low-Latency-Rpc on BLAZED.sh Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 01 Aug 2026 14:00:00 +0000</lastBuildDate>
    <atom:link href="https://blazed.sh/blog/tags/low-latency-rpc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Ethereum RPC Latency in 2026: IPC vs WebSocket vs Remote Providers, Measured</title>
      <link>https://blazed.sh/blog/posts/ethereum-rpc-latency-benchmark/</link>
      <pubDate>Sat, 01 Aug 2026 14:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/ethereum-rpc-latency-benchmark/</guid>
      <description>&lt;p&gt;Every RPC provider sells latency and almost nobody publishes a distribution. You get a marketing average, occasionally a p95 on a status page, and never the methodology. We wrote a &lt;a href=&#34;https://blazed.sh/blog/posts/ipc-vs-http-websocket-ethereum-rpc&#34;&gt;transport comparison&lt;/a&gt; last June that leaned on illustrative ranges because we had not measured them ourselves, and that has bothered us since. So this post measures instead: nine public Ethereum endpoints, up to 300 samples each, percentiles rather than means, a race between three subscription feeds to see who learns about a new block first, and a separate benchmark of what a JSON-RPC round-trip costs when there is no network in the path at all.&lt;/p&gt;</description>
    </item>
    <item>
      <title>IPC vs HTTP vs WebSocket: The Fastest Way to Talk to an Ethereum Node</title>
      <link>https://blazed.sh/blog/posts/ipc-vs-http-websocket-ethereum-rpc/</link>
      <pubDate>Wed, 17 Jun 2026 14:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/ipc-vs-http-websocket-ethereum-rpc/</guid>
      <description>&lt;p&gt;Every Ethereum RPC call travels over a transport, and the transport you pick sets a floor on how fast that call can ever be. For a wallet showing a balance, the difference is invisible. For an arbitrage bot that reads a price and decides whether to act before the next block, it is the whole game. This post compares the three transports your node speaks, HTTP, WebSocket, and IPC, explains where their latency comes from, and gives you a benchmark you can run to see the gap on your own setup.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
