Database Replication Lag
Incident Report for ReCharge
Resolved
At 2:30am est our DB read replica fell behind master. This means that while all writes were saved properly, reads were severely degraded. As of 8:30am est this issue was resolved and we will be addressing alerting among other things to make sure it does not happen again.
Posted Jan 28, 2020 - 11:30 PST