Sablier subgraph health check failed

[fielding]

Sablier Envio Subgraph Health Check Failed

Date: 2026-08-15

Failure Details

Field	Value
Endpoint	https://indexer.hyperindex.xyz/53b7e25/v1/graphql
HTTP Status	429 Too Many Requests
Response Body	(empty)

Query That Failed

{ LockupStream(where: { chainId: { _eq: "8453" } }, limit: 1) { tokenId depositAmount } }

Impact

The subgraph powers vault discovery in RipGuard. With this endpoint rate-limiting or unavailable, vault loading falls back to slower on-chain reads. Users are not blocked, but experience degraded performance.

Possible Causes

• Transient rate limit / quota exceeded on the HyperIndex endpoint
• Endpoint has changed or the subgraph schema has been updated (field renames)
• Network/infrastructure issue on the HyperIndex side

Recommended Investigation

1. Manually test the endpoint to confirm it's still rate-limiting or now healthy
2. Check if the subgraph schema has changed (e.g. tokenId or depositAmount renamed)
3. If the endpoint is permanently broken, update the query in packages/app/src/app/vaults/page.tsx
4. Consider adding retry logic or caching to reduce request frequency