Add a health check endpoint returning database, Redis, and Stellar Horizon connectivity status

[Chucks1093]

Summary

There is no health check endpoint for the server, making it impossible for load balancers or uptime monitors to verify that all dependencies are reachable. A GET /health endpoint that probes the database, Redis, and Horizon and returns their status should be added.

Scope

• Add GET /health endpoint that does not require authentication
• Probe the database with a lightweight SELECT 1 query
• Probe Redis with a PING command
• Probe Stellar Horizon by fetching the root endpoint and checking for a 200 response
• Return 200 with a JSON body listing each dependency and its status (ok or degraded)
• Return 503 if any dependency is degraded, with the degraded dependencies listed

Acceptance Criteria

• 200 returned when all dependencies are healthy
• 503 returned when any dependency is degraded
• Response body lists database, redis, and horizon with individual statuses
• Endpoint responds within 2 seconds under normal conditions
• Endpoint accessible without a JWT

ETA: 12 hours

---

Coordinate on Telegram

[Meet-hybrid]

I would like to contribute to this issue. I have experience with JavaScript/TypeScript, React, backend APIs, testing, Git, and software architecture. I will follow the acceptance criteria, add tests, and provide a focused pull request.

[Meet-hybrid]

I would like to contribute to this issue. I have experience with JavaScript/TypeScript, React, backend APIs, testing, Git, and software architecture. I will follow the acceptance criteria, add tests, and provide a focused pull request.

[anifast-123]

@anifast-123 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I would like to implement the unauthenticated GET /health endpoint to probe the database, Redis, and Stellar Horizon, returning a 503 status code if any dependency is degraded. I can ensure the database check executes a lightweight SELECT 1 query and responds within the required two-second window.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @anifast-123 to this issue.

[axeroofficialtournament-del]

@axeroofficialtournament-del has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello Maintainer, I have gone through this issue documentation and i am interesting and would love to be assigned this particular issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @axeroofficialtournament-del to this issue.

[jajafwangshak86-ops]

@jajafwangshak86-ops has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

let me handle this please

ℹ️ Repo Maintainers: To accept this application, review their application or assign @jajafwangshak86-ops to this issue.

[drips-wave]

Congratulations, @jajafwangshak86-ops! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @jajafwangshak86-ops: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@jajafwangshak86-ops's PR #860 was approved and merged by @Chucks1093.

🏆 @jajafwangshak86-ops: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (917 total points). Track your full progress on GrantFox.

👏 Great work, @jajafwangshak86-ops! Keep contributing to accesslayerorg.