# ProbeLab’s Notable IPFS Performance Results - Week 36, 2026

**URL:** <https://discuss.ipfs.tech/t/probelab-s-notable-ipfs-performance-results-week-36-2026/20346>\
**Category:** Protocol\
**Tags:** dht, http-gateway, kubo, ipni\
**Created:** [September 8, 2026, 6:52am UTC](https://discuss.ipfs.tech/t/probelab-s-notable-ipfs-performance-results-week-36-2026/20346 "2026-09-08T06:52:01Z")\
**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:** [September 8, 2026, 6:52am UTC](https://discuss.ipfs.tech/t/probelab-s-notable-ipfs-performance-results-week-36-2026/20346/1 "2026-09-08T06:52:01Z")

</div>

Following up on our update back in [Week 29 (mid-July)](https://discuss.ipfs.tech/t/probelab-s-notable-ipfs-performance-results-week-29-2026/20276), we are looking across the data from July and August to bring you the most notable network performance trends up to today (Week 36, September 2026).

This period saw a significant mid-summer influx of DHT client nodes, sustained sub-second publish times, continuous high volume on indexers, but also stabilization of some core network metrics and smooth gateway migration.

Here is a summary of the most notable results:

### 1. Network Topology

- **DHT Server Baseline:** Core DHT server nodes remain remarkably stable, continuing to hover steadily around the **23k–25k** mark in terms of DHT Server IP addresses. The actual DHT Server nodes, in terms of PeerIDs seen is also steady, around **12k-13k.** Both of these numbers refer to the weekly average over all crawls. The number of servers at a specific point in time (network snapshot) stands at **4k nodes** simultaneously online.
- **Mid-August Client Spike:** In contrast to the stable server count, the estimated number of active Amino DHT client nodes experienced a significant surge in mid-August (Weeks 33 and 34), **peaking at ~800k client nodes** (up from the post-Week 18 baseline of ~400k). Over late August and early September, this spike has begun to taper back down toward normal levels.
- **Bootstrappers:** The IPFS Amino DHT bootstrap infrastructure maintained **100% availability** with zero performance degradation or churn during the client traffic influx.
- 📊 _Track this here:_ [IPFS Servers vs Clients](https://probelab.io/ipfs/#chart-ipfs-servers-vs-clients-ts) & [Bootstrapper Performance](https://probelab.io/ipfs/bootstrappers/)

### 2. Kubo & DHT Lookup Trends

- **Publish Gains holding strong:** Content publishing times introduced with Kubo v0.39+ have sustained their sub-second performance, holding tight at **under 1 second** across the network.

- **Lookup Latencies:** Despite the temporary doubling of active client nodes in mid-August, DHT lookup latencies remained unaffected, maintaining a steady average **around 0.3s–0.35s**.

- **Regional Lookup Performance (IPNI vs. DHT):** Comparing lookup performance across geographic probe locations reveals a distinct latency gradient:

- 📊 _Track this here:_ [Kubo Publish Performance](https://probelab.io/ipfs/kubo/#chart-kubo-publish-performance-ts), [DHT Lookup Performance](https://probelab.io/ipfs/dht/#chart-ipfs-dht-lookup-performance-ts), & [IPNI vs DHT Lookup Comparison CDF](https://probelab.io/ipfs/charts/ipni-dht-lookup-comparison-cdf/?date=2026-09-07&aggregation_type=p50)

### 3. Bitswap & Content Volume Growth

- **Sustained CID Volume:** Daily unique CIDs circulated through Bitswap stayed strongly elevated throughout August, consistently pushing **over 100M to 120M+ unique CIDs/day**.

- **WANT CID Demand:** The p90 WANT CID request volume closely mirrored the mid-August node influx, showing increased peer interactions during the client activity peak.

- 📊 _Track this here:_ [Bitswap Unique CIDs](https://probelab.io/ipfs/bitswap/#chart-ipfs-bitswap-unique-cids-ts)

### 4. `cid.contact` Performance Excellence

- **Indexer Ingress:** Traffic hitting `cid.contact` remained near historical highs, handling **over 198M+ daily IPNI lookup requests** , especially during August.

- **Ingest Uptime:** The IPNI infrastructure maintained its **\>99% uptime** threshold throughout the period, with advertisement ingestion delays (\>5 min), or downtime remaining practically non-existent. Impressive performance!

- 📊 _Track this here:_ [IPNI Uptime & Latencies](https://probelab.io/ipfs/ipni/cid.contact/#chart-ipni-uptime-bar) & [IPNI Requests](https://probelab.io/ipfs/ipni/cid.contact/#chart-ipfs-ipni-requests-ts)

### **5. Gateways & Service Worker Performance**

- **Massive Traffic Spike:** Public HTTP gateway requests (`ipfs.io`, `dweb.link`) experienced a massive volume surge alongside the mid-August client node influx, **peaking at several billion requests per day** (a multi-fold increase over the baseline 200M–300M daily average seen in prior months).

- **Correlated Activity & Rate Limiting:** This multi-billion daily request surge indicates heavy automated/bot polling or specialized client scraping activity hitting gateway endpoints in tandem with the DHT client node increase. A notable portion of this volume was handled via CloudFlare security filtering and HTTP 429 rate-limiting actions before scaling back down toward baseline levels in late August.

- **Service Worker Adoption (`inbrowser.link`):** Despite temporary traffic surges on legacy public gateways, the structural migration toward client-side verification via Service Worker Gateways continues to progress steadily.

- **Service Worker TTFB Performance:**

- 📊 _Track this here:_ [IPFS Gateway Requests Time-Series](https://probelab.io/ipfs/charts/ipfs-gateway-requests-ts/?start=2026-03-10&end=2026-09-08) & [Service Worker Gateway TTFB](https://probelab.io/ipfs/gateways/#chart-ipfs-service-worker-gateway-ttfb-ts)

### 6. Security & Keyspace Distribution

- **Keyspace Density & Prefix Depth:** As noted in [the discussion](https://discuss.ipfs.tech/t/probelab-s-notable-ipfs-performance-results-week-29-2026/20276/2) following Week 29, region threshold crossings at depth-6 reflect mild distributed elevations across sub-prefixes rather than concentrated clustering. At depth-10, no single prefix exceeded ~20 peers, indicating no active targeted key-clustering attack or localized routing table overload.

- 📊 _Track this here:_ [Keyspace Region Population](https://probelab.io/ipfs/security/#chart-keyspace-regions-population)

* * *

Huge thanks to the network infrastructure and developer teams maintaining performance across all fronts! Feel free to share your thoughts, questions, or observations below, or reach out to the team via the [ProbeLab contact page](https://probelab.io/contact/).
