Sablier subgraph health check failed

[fielding]

Sablier subgraph health check FAILED

Date: 2026-07-29
Detected by: Automated health check routine

Endpoint

https://indexer.hyperindex.xyz/53b7e25/v1/graphql

Query Used

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

Failure Details

• HTTP Status Code: 429 (Too Many Requests)
• Raw Response Body: (empty — server returned no body with the 429 status)

Impact

RipGuard's on-chain fallback is active so vaults still load, but vault discovery is degraded (slower). The subgraph is the primary fast path for vault discovery.

Possible Causes

• Rate limiting on the Envio indexer endpoint
• Endpoint is overloaded or temporarily unavailable
• The endpoint or schema may have changed

Recommended Actions

• Verify the subgraph endpoint is still active and not deprecated
• Check if the schema has changed — update the query in packages/app/src/app/vaults/page.tsx if needed
• If persistently rate-limited, add request caching or contact Envio for higher limits
• Re-run health check after investigating to confirm resolution

[fielding]

Health check re-ran on 2026-08-02 and the subgraph is still failing.

Failure details:

• HTTP status: 429 Too Many Requests
• Response body: (empty)
• Endpoint: https://indexer.hyperindex.xyz/53b7e25/v1/graphql
• Query: LockupStream(where: { chainId: { _eq: "8453" } }, limit: 1) { tokenId depositAmount }

The endpoint is rate-limiting requests. This may indicate the indexer project/plan has hit a usage quota, or the endpoint URL has changed. RipGuard's on-chain fallback is active, but vault discovery will be slower until resolved.

Suggested next step: check the Hyperindex dashboard for the project 53b7e25 to see quota/rate-limit status, or review the query in packages/app/src/app/vaults/page.tsx.

---

Generated by Claude Code