PROVIDER STATUS
Provider connectivity is monitored independently
VOYALEX isolates provider failures so one slow or unavailable integration does not automatically remove healthy provider results from the user journey.
01
Health and circuit state
Runtime health distinguishes healthy, degraded, rate-limited, authentication-failed, open-circuit and half-open states.
- Circuit state is provider-specific.
- Authentication errors are not retried like temporary network errors.
- Half-open probes can restore a recovered provider.
02
Latency containment
Public searches operate inside bounded provider and end-to-end execution budgets so one integration cannot hold the request indefinitely.
- Provider windows are bounded.
- Retries share the same execution budget.
- Existing healthy results can complete as partial success.
03
What public status exposes
Public status intentionally avoids credentials, endpoints with secrets, private certificates or internal exception traces.
- Only safe operational state is exposed.
- Secrets and authorization material are never public status fields.
- Technical diagnostics remain an administrative concern.
TRAVEL BUYING INTELLIGENCE
Run a live scan ↗
See provider health inside a live scan
The result experience shows safe provider health evidence alongside the actual comparison.
