@okhhg

This has been fixed now. An automated database failover caused the replication state to be in a bad state. RDS recovery took 90% of the 4h downtime. Backfill is in progress.

0 reply

0 recast

0 reaction