In our measurements over a 6-minute window covering all leaders and all slots, with 1-in-16 sampling, shreds arriving via the Turbine path won the arrival race 28.3% of the time. In other words, more than a quarter of all shreds reached our servers earlier through native Turbine propagation than through any Jito ShredStream path, including Frankfurt, Amsterdam, and the XDP fast-path. Those locally-won shreds are delivered to your server with sub-millisecond latency over our internal network instead of taking the longer route. This is why we recommend running LocalShred alongside ShredStream rather than as a replacement: the two sources complement each other, and taking the first arrival from either source gives you a strictly faster effective feed than either source alone.
