Provider Health Monitoring
The Provider Health page shows you the real-time status of every connected provider. If something is wrong with a provider, you will see it here before your users do.What You See
📷 [Screenshot: Provider health page with 13 provider rows, each showing status badge, error rate bar, and latency]For each provider:
| Field | Description |
|---|---|
| Status | Green (healthy), Yellow (degraded), Red (down) |
| Error rate | Percentage of requests that failed in the last 5 minutes |
| P50 latency | Median response time in milliseconds |
| P95 latency | 95th percentile response time, shows worst-case performance |
| Last checked | When Routor last validated this provider |
Status Definitions
| Status | Meaning |
|---|---|
| Healthy | Success rate 95% or higher, and P95 latency at or below 5 seconds |
| Degraded | Success rate between 70% and 95%, or P95 latency above 5 seconds - still in the routing pool but fallbacks are more likely |
| Down | Success rate below 70%, or provider failed startup validation - removed from routing pool |
Startup Validation
When Routor restarts, it pings every configured provider using their free/models endpoint. Providers that fail this check are marked as down immediately and removed from the routing pool before any traffic is accepted.
This is why a misconfigured API key surfaces as a provider being down on this page, not as an error on your users’ requests.
What Happens When a Provider Goes Down
Routor does not wait for you to notice. When a provider’s error rate crosses the threshold, it starts routing around that provider automatically using the fallback chain. You will see:- The provider status badge turn red on this page
- Fallback activity in the dashboard’s request logs (and
X-Routor-Fallback: trueon responses, if your deployment hasDEBUG_ROUTING=1set)