From dfdffbbc46910ee2377407f499991508bb3275bc Mon Sep 17 00:00:00 2001 From: Kenny Date: Tue, 9 Jun 2026 00:34:29 -0400 Subject: [PATCH 1/3] Enumerate sync rate term --- website/src/pages/en/subgraphs/fair-use-policy.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/website/src/pages/en/subgraphs/fair-use-policy.mdx b/website/src/pages/en/subgraphs/fair-use-policy.mdx index 9c7212128746..ed7a09bbd091 100644 --- a/website/src/pages/en/subgraphs/fair-use-policy.mdx +++ b/website/src/pages/en/subgraphs/fair-use-policy.mdx @@ -27,6 +27,9 @@ Beyond that, pricing is variable and adjusts based on usage patterns, network co #### **Syncing Limits** Subgraphs must sync within **14 days** of deployment. +Subgraphs older than 14 days that fall significantly behind chainhead — at least 2,000 blocks behind with sustained outlier lag — may be deleted, even if they previously synced successfully. + + > You can monitor your usage to avoid surpassing limits via [Subgraph Studio](https://thegraph.com/studio/). @@ -36,7 +39,8 @@ To preserve the stability of Edge & Node's Subgraph Studio and the reliability o - **Storage** usage beyond posted limits. This includes circumvention of storage thresholds (e.g., use of multiple free-tier accounts). - **Utilization** that is abnormally high, or zero utilization, or sustained bandwidth. -- **Sync** time greater than 14 days after deployment. +- **Sync time** greater than 14 days after deployment. +- **Sync rate** that is a sustained outlier for the chain, over 14 days old, and at least 2,000 blocks behind chainhead. The Edge & Node Support Team reserves the right to revise fair limits or impose temporary constraints for operational integrity. From a680ab3b2ec8f12a09f7aa40033e077125ab6a25 Mon Sep 17 00:00:00 2001 From: Kenny Date: Tue, 9 Jun 2026 00:35:33 -0400 Subject: [PATCH 2/3] Link to supported networks instead of pruning --- website/src/pages/en/subgraphs/fair-use-policy.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/en/subgraphs/fair-use-policy.mdx b/website/src/pages/en/subgraphs/fair-use-policy.mdx index ed7a09bbd091..8a847100e409 100644 --- a/website/src/pages/en/subgraphs/fair-use-policy.mdx +++ b/website/src/pages/en/subgraphs/fair-use-policy.mdx @@ -47,7 +47,7 @@ The Edge & Node Support Team reserves the right to revise fair limits or impose If you exceed your fair use limits, you will receive an email alert giving you a grace period of **7 days** to take action. Here are some options: - Try [pruning Subgraph data](/subgraphs/best-practices/pruning/) to remove unused entities and help stay within storage limits. -- If your subgraph references chains that receive indexing rewards, [indicated by double check marks in the Subgraphs column here](/subgraphs/best-practices/pruning/), then [publish your Subgraph to the Network](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) and [add signal](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) to encourage other Indexers on the network to serve it. +- If your subgraph references chains that receive indexing rewards, [indicated by double check marks in the Subgraphs column here](/supported-networks/), then [publish your Subgraph to the Network](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) and [add signal](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) to encourage other Indexers on the network to serve it. - If your Subgraph references a chain that **does not** receive indexing rewards, reach out to InfraDAO [indexing@infradao.com⁠] or @jmulq on Telegram to discuss options that meet your technical needs. Edge & Node's team is committed to helping users avoid unnecessary interruptions and will continue to support all builders. From 8b5f582725c4919ddd0d0e864866d0c48a67bc82 Mon Sep 17 00:00:00 2001 From: Kenny Date: Tue, 9 Jun 2026 00:48:42 -0400 Subject: [PATCH 3/3] Make the changes conform to format reqs --- website/src/pages/en/subgraphs/fair-use-policy.mdx | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/website/src/pages/en/subgraphs/fair-use-policy.mdx b/website/src/pages/en/subgraphs/fair-use-policy.mdx index 8a847100e409..c8c841b28577 100644 --- a/website/src/pages/en/subgraphs/fair-use-policy.mdx +++ b/website/src/pages/en/subgraphs/fair-use-policy.mdx @@ -26,10 +26,7 @@ Beyond that, pricing is variable and adjusts based on usage patterns, network co #### **Syncing Limits** -Subgraphs must sync within **14 days** of deployment. -Subgraphs older than 14 days that fall significantly behind chainhead — at least 2,000 blocks behind with sustained outlier lag — may be deleted, even if they previously synced successfully. - - +Subgraphs must sync within **14 days** of deployment. Subgraphs older than 14 days that fall significantly behind chainhead — at least 2,000 blocks behind with sustained outlier lag — may be deleted, even if they previously synced successfully within 14 days. > You can monitor your usage to avoid surpassing limits via [Subgraph Studio](https://thegraph.com/studio/).