50% off | $1.50$0.75 | $7.50$3.75 | $0.15$0.075 | $0.15$0.075 | 2.12s | 137 tps | |
|---|---|---|---|---|---|---|---|
50% off | $1.50$0.75 | $7.50$3.75 | $0.15$0.075 | $0.15$0.075 | 2.48s | 68 tps | |
Not used in Standard routing:Why these endpoints are not used | |||||||
Flex50% off | $0.75$0.375 | $3.75$1.875 | $0.075$0.0375 | $0.075$0.0375 | 2.08s | 133 tps | |
Priority50% off | $2.70$1.35 | $13.50$6.75 | $0.27$0.135 | $0.27$0.135 | 2.48s | 149 tps | |
Priority50% off | $2.70$1.35 | $13.50$6.75 | $0.27$0.135 | $0.27$0.135 | 2.22s | 100 tps | |
Flex50% off | $0.75$0.375 | $3.75$1.875 | $0.075$0.0375 | $0.075$0.0375 | 13.60s | 20 tps | |
P50, best across providers
P50, best provider
When an error occurs in an upstream provider, we can recover by routing to another healthy provider, if your request filters allow it. You can access per-provider uptime data programmatically through the Endpoints API. Learn more about our load balancing and customization options.
