Both postgres instances are replica

flyctl --app amz-db status
Update available 0.0.286 -> v0.0.302.
Run "flyctl version update" to upgrade.
App
  Name     = redacted
  Owner    = redacted
  Version  = 1
  Status   = running
  Hostname = redacted.fly.dev

Deployment Status
  ID          = d80d2b8e-redacted
  Version     = v1
  Status      = successful
  Description = Deployment completed successfully
  Instances   = 2 desired, 2 placed, 2 healthy, 0 unhealthy

Instances
ID      	PROCESS	VERSION	REGION	DESIRED	STATUS           	HEALTH CHECKS     	RESTARTS	CREATED
f0a68a7b	app    	1      	ord   	run    	running (replica)	3 total, 3 passing	0       	4m13s ago
4de33e7a	app    	1      	ord   	run    	running (replica)	3 total, 3 passing	1       	7m12s ago

This is a display bug. It looks like it didn’t detect which was leader for display purposes, but the cluster was working just fine!

The health checks fail if they can’t connect to a leader. Our display status has likely updated by now, it takes a few minutes for that to get in sync.