Repository navigation
fix: fail over indexer requests - #11
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The primary Render indexer currently returns 503, which leaves discovery unavailable even though the replacement service is healthy.
This change replaces the single-upstream rewrite with a same-origin API proxy that tries the existing service first and fails over to
https://resolve-indexer-r4fs.onrender.comfor network failures, timeouts, rate limits, and 5xx responses. The status page uses the same ordered failover logic, and deployment/submission docs list both services.Validation:
/health,/ready, and/markets?limit=1: 503/health,/ready, and/markets?limit=1: 200npm test -- --run: 22 tests passednpm run typecheck: passed