After monitoring the rollback and deploy of the improved update we are confident the issue has been resolved.

Thank you for your patience as we worked to resolve the issue.

We have identified the issue and have reverted the changes.

There was a change to our database that caused failing syncs to not retry.

We are now monitoring the roll back.

Thank you again for your patience as we work to resolve this issue.

This incident has been resolved.

We implemented a fix and are currently monitoring the result.

The issue has been successfully resolved. Thank you again for your patience as worked this issue to resolution and we apologize for any inconvenience this issue might have caused.

We are seeing US data plan sync succeeding but we are still seeing some failures in EU. We are continuing to work on a fix for this incident.

We believe this is due to a certificate issue and are working on a fix.

Users are currently seeing errors when creating a new connector or connection, re-testing existing connectors, and starting syncs.

We will provide updates as we investigate further. Thank you for your patience as we investigate this issue.

The issue has been successfully resolved.
Thank you again for your patience as worked this issue to resolution and we apologize for any inconvenience this issue might have caused.

We are continuing to monitor the results of the fix and expect syncs to succeed

Thank you for your patience as we investigated this issue and we apologize for any inconvenience.

We are continuing to monitor the issue, however the fix we implemented may cause some syncs to fail but the next scheduled sync should succeed.

We implemented a fix to increase the number of workers and are currently monitoring the result.

Affected connections should continue to sync as expected.

This incident has been resolved. If you are seeing any further permissions errors, please re-authenticate your Instagram connector.

Please reach out to Airbyte Cloud support if you have any questions.

After monitoring the fix implemented we have resolved the issue.

The issue occurred under certain conditions and caused syncs to to not be properly retried.

Thank you for your patience as we investigated this issue and we apologize for any inconvenience.

We believe we have found the root cause and have implemented a fix. We will be monitoring the results.

We are still seeing instances of these long running syncs and failures with "Setting attempt to FAILED because the temporal workflow for this connection was restarted, and existing job state was cleaned.". We are continuing our investigation and will add updates as we have them.

We have been monitoring the results over the weekend and would like to continue monitoring throughout the day.

We implemented a fix and are currently monitoring the result. Any sync affected will show as a failed sync but the next scheduled sync should run as expected.

The issue has been successfully resolved. Thank you again for your patience as worked this issue to resolution and we apologize for any inconvenience this issue might have caused.

We have identified the issue and rolled-back changes. We are currently monitoring the result.

This incident has been resolved.

The issue has been successfully resolved. All systems are functioning as intended.

Thank you again for your patience as worked this issue to resolution and we apologize for any inconvenience this issue might have caused.

We believe that we have addressed the manual sync issue. All systems appear normal and currently monitoring.

We have fixed the internal networking error. During this outage syncs failed to start and the web was inaccessible.

We implemented a fix and are currently monitoring the result.

We unintentionally recreated a necessary networking component. While this component was being recreated internal traffic was disrupted. We have finished recreating this networking component and expect the system to recover soon.

A fix has been deployed for the Postgres Source Connector and this incident has been resolved. All syncs previously impacted should now complete successfully.

The issue has been successfully resolved. Thank you again for your patience as worked this issue to resolution and we apologize for any inconvenience this issue might have caused.

We implemented a fix and are currently monitoring the results.