Does a VPS automatically stay online if its physical host fails?
Virtualisation alone does not guarantee continuous availability during a physical-host failure. Automatic restart, migration and recovery depend on the provider’s platform and the service terms. Your application may also need its own redundancy and data-consistency design.
Instructions
1. Confirm the platform recovery model
Ask what happens during host failure, whether the VPS is restarted elsewhere, what storage is accessible, and which recovery objectives apply. Do not infer these capabilities from the presence of a snapshot or power button.
2. Identify application dependencies
Map databases, uploaded files, DNS, certificates and external services. A restarted virtual machine can still have an unavailable application if a dependency, credential or stateful component has not recovered.
3. Test the agreed outcome safely
Use a planned recovery exercise in an isolated target where possible. Observe the actual return of the application, not only a Running server status. In Britixo, review Activity and the final state after supported operations; monitoring or notifications provide evidence but do not themselves repair an outage.
Check the result
- Platform and application recovery responsibilities are documented.
- A planned test demonstrates the required data and application recovery within the agreed target.
Troubleshooting
- The server is Running but the site is unavailable
- Check guest boot completion, services, databases, network policy and application logs.
- The platform offers no automatic failover
- Design an appropriate additional recovery or redundancy arrangement instead of assuming one exists.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.