We were adding a new certificate to a load balancer in support of a new service. This new service overwrote the existing certificate for cloud.airbyte.com. We noticed this issue quickly and reverted the changes, but DNS is not realtime and took a few minutes to go into effect.

You may have seen an error when accessing Airbyte Cloud suggesting your connection was not private, this was only due to the existing certificate being overwritten.

This should not have affected any syncs and you should be able to access your workspaces as normal.

Please reach out to Airbyte Cloud support if you have any questions and we thank you for your patience while we resolved this issue.