Skip to content

Update fair use with sync rate req #1108

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
idalithb merged 3 commits into from
Jun 9, 2026
Merged

Update fair use with sync rate req #1108

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
dfdffbb
Enumerate sync rate term
kchandrasekera Jun 9, 2026
a680ab3
Link to supported networks instead of pruning
kchandrasekera Jun 9, 2026
8b5f582
Make the changes conform to format reqs
kchandrasekera Jun 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions website/src/pages/en/subgraphs/fair-use-policy.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +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 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/).

Expand All @@ -36,14 +36,15 @@ 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.
Comment thread
kchandrasekera marked this conversation as resolved.

The Edge & Node Support Team reserves the right to revise fair limits or impose temporary constraints for operational integrity.

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.
Expand Down
Loading