Hi, this host is currently offline due to a hardware issue. Please do not run single-node Postgres for production apps as you will hit this exact case and your database will be unavailable. You can restore from a backup or wait for the host to be restored to service.
There are a few managed providers that will supply a small PG database free of charge; that might be worth a go. If it is reasonably close to your host, latency should not be much of an issue. I use Supabase, though bear in mind they pause any databases that are getting insufficient use.
Yes but i will have data lose if i restore the database from a previous snapshot. What is the situation exactly ? How long time it will take to restore the situation ?
there is a network issue on this host; it’s unknown how long it will take to restore, but our team is working on it.
please note that today’s issue doesn’t have data loss, but tomorrow’s might. from our volumes documentation:
Create redundancy in your primary region: If your app needs a volume to function, and the NVMe drive hosting your volume fails, then that instance of your app goes down. There’s no way around that. You can run multiple Machines with volumes in your app’s primary region to mitigate hardware failures.
Create and store backups: If you only have a single copy of your data on a single volume, and that drive fails, then the data is lost. Fly.io takes daily snapshots and can retain them from 1 to 60 days (5 days by default), but the snapshots shouldn’t be your primary backup method.
