What should be monitored
- Gateway DNS and TCP reachability
- Authentication success
- Country-route availability
- Connection and response latency
- Usable response rate for defined test targets
Service status without invented uptime numbers.
This static page explains the current disclosure level and the measurements required before LivoProxy publishes historical availability statistics.
Public automated status feed: not yet available
Contact support for an account-specific availability check before starting or scaling a workload.
How an incident should be described
- Start and recovery timestamps in UTC
- Affected connection surface or location
- Observed customer impact
- Mitigation and follow-up actions
- No exposure of credentials or target-sensitive logs
What this page does not claim
- No universal uptime percentage
- No fixed response-time guarantee
- No fixed global IP availability
- No promise that every target is supported
- No SLA unless stated in a signed quote
Publication roadmap
A future automated status service should publish current component state, incident history, maintenance notices, measurement regions, and the calculation method behind any uptime percentage. Until that system exists, this page deliberately avoids a green “all operational” badge that cannot be independently supported.