fix: update Large tier hardware description to reflect current network scale

Author: cargopete

website/src/pages/en/indexing/overview.mdx

@@ -126,7 +126,7 @@ Indexers may differentiate themselves by applying advanced techniques for making
 - **Small** - Enough to get started indexing several Subgraphs, will likely need to be expanded.
 - **Standard** - Default setup, this is what is used in the example k8s/terraform deployment manifests.
 - **Medium** - Production Indexer supporting 100 Subgraphs and 200-500 requests per second.
-- **Large** - Prepared to index all currently used Subgraphs and serve requests for the related traffic.
+- **Large** - Sufficient for approximately 1,500–2,000 Subgraphs. Note: these figures predate significant network growth. As of 2026, the network has over 15,000 Subgraphs; community operators report ~600 GB total RAM for ~1,700 Subgraphs. Indexing the full network requires substantially more resources than this tier provides.
 
 | Setup | Postgres<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(memory in GBs) |
 | --- | :-: | :-: | :-: | :-: | :-: |