No components marked as affected
Resolved
This incident has been resolved.
Identified
Our team is continuing to roll out a permanent fix to all affected systems
Identified
Our team is continuing to roll out a permanent fix to all affected systems.
Identified
We are continuing to roll out a permanent fix to all affected systems.
Identified
All systems have been patched. We are gradually rolling out the permanent fix to all affected systems.
Identified
We have applied fixes for all new nodes and services. A temporary fix has been applied to existing nodes. We are in the process of applying a permanent fix for the replication issue.
Identified
We have applied fix for the root cause and no new services or nodes should be affected by this. A temporary fix has been applied to almost all previously affected nodes to fix any immediate replication issues. We are still working on applying a permanent fix for all affected nodes.
Identified
We have identified the root cause of the problem and we have prepared a fix, which is ready to be deployed. At the same time we are still making the necessary corrections on the affected nodes in order to restore normality.
Identified
PostgreSQL replica nodes fail to connect to new master after failover. We are manually fixing affected services to fix any immediate issues while working on fixing the root cause. There may be higher than expected replication lag for standby and separate read-replica nodes while the issue is ongoing.