Skip to content

Reorder #1082

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 2 commits into from
Feb 26, 2026
Merged

Reorder #1082

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a91ff95
Reorder
idalithb Feb 26, 2026
be747b4
Update website/src/pages/en/subgraphs/fair-use-policy.mdx
idalithb Feb 26, 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
15 changes: 8 additions & 7 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 @@ -28,17 +28,18 @@ You can monitor your usage via [Subgraph Studio](https://thegraph.com/studio/).

To preserve the stability of Edge & Node's Subgraph Studio and preserve the reliability of The Graph Network, the Edge & Node Support Team will monitor storage usage and take corresponding action with Subgraphs that have:

- Abnormally high or sustained bandwidth or storage usage beyond posted limits
- Circumvention of storage thresholds (e.g., use of multiple free-tier accounts)
- Abnormally high or sustained bandwidth or storage usage beyond posted limits.
- Circumvention of storage thresholds (e.g., use of multiple free-tier accounts).

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

If you exceed your included storage:

- Try [pruning Subgraph data](/subgraphs/best-practices/pruning/) to remove unused entities and help stay within storage limits
- [Publish your Subgraph to the Network](https://thegraph.com/docs/en/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
- You will receive an email alert
- A grace period of **7 days** will be provided to upgrade or reduce storage
- You will receive an email alert.
- A grace period of **7 days** will be provided to take the following options:
- [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 is on a chain without indexer rewards, but you'd like to get it indexed, you can work directly with independent Indexers. Contact @jmulq on Telegram or email [InfraDAO](mailto:indexing@infradao.com) to discuss options.
- Try [pruning Subgraph data](/subgraphs/best-practices/pruning/) to remove unused entities and help stay within storage limits.

Edge & Node's team is committed to helping users avoid unnecessary interruptions and will continue to support all builders.

Expand All @@ -48,4 +49,4 @@ Subgraphs inactive for over **7 days** or Subgraphs that exceed free-tier storag

### 5. Support

If you believe your usage is incorrectly flagged or have unique use cases (e.g. approved special request pending new Subgraph upgrade plan), reach out to [InfraDAO](mailto:indexing@infradao.com) or `@jmulq` on Telegram.
If you believe your usage is incorrectly flagged or have unique use cases (e.g. approved special request pending new Subgraph upgrade plan), reach out to [Edge & Node team](mailto:info@edgeandnode.com).