Relay Pulse
An API relay that answers HTTP 200 with an empty reply is not alive, and Relay Pulse exists to catch exactly that. Every minute, or any interval you set, it sends a tiny real request to each relay, asks a simple arithmetic question, and counts the probe as healthy only when the right answer comes back. Results land in a color-coded availability matrix where green, yellow, and red blocks show good, slow, and failed checks across the last 90 minutes, 24 hours, 7 days, or 30 days. Each row lists provider, service type, channel, model, price multiplier, days listed, uptime percentage, and the latest latency, and hovering a block reveals its probe counts and a breakdown of why it degraded. Filters narrow the table by category, provider, service, channel, vendor, or model, and the page switches between table and card views, four themes, and English or Chinese. Sponsor levels can pin trusted channels to the top, hot and cold boards separate active relays from dormant ones, and Telegram or QQ bots push status changes. Configuration reloads without a restart, templates cover Claude, Codex, and Gemini style endpoints, and a JSON API exposes current status. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
Deploy