Hey there,
It looks like the failover was never performed. The PRIMARY_REGION was configured to sjc but leadership was still held by the PG member within sea. I went ahead and issued the failover for you and things are back to normal.
For future reference, you can get a better picture of things by running the following:
fly ssh console --app <app-name>
stolonctl status
I wrote up details on this here: What is the correct process to change the postgres leader region? - #2 by shaun
If you have any additional questions on this, just let us know!