# ProbeLab's Notable IPFS Performance Results - Week 07, 2026

**URL:** https://discuss.ipfs.tech/t/probelabs-notable-ipfs-performance-results-week-07-2026/20048
**Category:** Protocol
**Created:** [February 20, 2026, 12:52pm UTC](https://discuss.ipfs.tech/t/probelabs-notable-ipfs-performance-results-week-07-2026/20048 "2026-02-20T12:52:40Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![yiannis](https://avatars.discourse-cdn.com/v4/letter/y/e47774/32.png) [@yiannis](https://discuss.ipfs.tech/u/yiannis)
#### Post date: [February 20, 2026, 12:52pm UTC](https://discuss.ipfs.tech/t/probelabs-notable-ipfs-performance-results-week-07-2026/20048/1 "2026-02-20T12:52:40Z")

</div>

Here is ProbeLab’s update on the state of the IPFS network over the past few weeks. The intention of these reports is to direct efforts to parts of the protocol that need attention. Here’s the highlights:

- The number of Amino DHT Server nodes has stabilised at ~25k: [https://probelab.io/ipfs/#chart-ipfs-servers-vs-clients-ts](https://probelab.io/ipfs/#chart-ipfs-servers-vs-clients-ts) with the number of generally online server nodes having stabilised at ~4+k nodes, following also a declining pattern over the last few months: [https://probelab.io/ipfs/topology/#chart-availability-classified-ts](https://probelab.io/ipfs/topology/#chart-availability-classified-ts)

- **Kubo’s “Provide Duration” has decreased significantly** with the release of v0.39.0 from more than 13s to less than 1s! This improvement came as a result of **“Optimistic Provide”** - an optimisation proposal that was **originally proposed by the ProbeLab team** and in particular @dennis-tra ! See more details and what this means in detail at: [https://github.com/ipfs/kubo/releases/tag/v0.39.0](https://github.com/ipfs/kubo/releases/tag/v0.39.0) and the original ideation around it here: [https://discuss.libp2p.io/t/dht-optimistic-provide/1143](https://discuss.libp2p.io/t/dht-optimistic-provide/1143) (from 2021!).

- The Amino DHT Lookup performance is stable around 0.3s-0.4s, on average among all regions: [https://probelab.io/ipfs/dht/#chart-ipfs-dht-lookup-performance-ts](https://probelab.io/ipfs/dht/#chart-ipfs-dht-lookup-performance-ts) with Europe being by far the fastest, especially compared to Asia Pacific: [https://probelab.io/ipfs/dht/#chart-ipfs-dht-lookup-performance-cdf](https://probelab.io/ipfs/dht/#chart-ipfs-dht-lookup-performance-cdf)

- The IPNI performance is mostly stable and “green” with a few exceptions where CIDs are ingested with a delay of more than 5 mins (but less than 60mins) 15% of the time: [https://probelab.io/ipfs/ipni/cid.contact/#chart-ipni-uptime-bar](https://probelab.io/ipfs/ipni/cid.contact/#chart-ipni-uptime-bar).

- The number of daily requests to the [ipfs.io](http://ipfs.io) and [dweb.link](http://dweb.link) gateways remains relatively stable, hovering above 500M per day. ProbeLab has improved its tooling to distinguish between different service classes, i.e., instead of only Served and Blocked, we now also present the percentage of Badbits requests, which were previously grouped under Blocked. We also show the number of requests that were Redirected.

- The TTFB of Service Worker gateway has decreased substantially (by about 0.75s-1s) for CID requests that hit the cache of gateways from any of our probing locations: [https://probelab.io/ipfs/gateways/#chart-ipfs-service-worker-gateway-ttfb-ts](https://probelab.io/ipfs/gateways/#chart-ipfs-service-worker-gateway-ttfb-ts).