Airbyte - Notice history

Since resolving this issue we have found that connections scheduled to run during the outage (5:30AM - 10:30AM PST) went into a quarantined state.

We have since taken action to force fail and rectify these connections to allow them to return to a normal state.

We sincerely apologize for any inconvenience this outage has caused and again thank you for your patience as our teams worked hard towards a resolution.

The issue has been successfully resolved. The root cause was related to this morning server miss communication error.

During the times of 5:30AM PST to 10:30AM PST any syncs that were scheduled to start during that time will have most likely failed but moving forward the next scheduled sync is expected to succeed.

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

We implemented a fix and currently monitoring the result.

We have identified the root cause and are working on a fix.

After monitoring the fix we are confident the issue has been successfully resolved.

This issue was due to a server configuration error web service was degrades and UI was unavailable for ~3 hours but syncs were continuing to run and were unaffected.

We apologize for any inconvenience and thank you for your patience as we worked this issue to a resolution.

We are continuing to work on a fix for this incident.

We are continuing to work on a fix for this incident.

Our engineers have deployed a fix. Users should be able to reset their passwords now.

We are continuing to work on a fix for this incident.

A resolution as been implemented. Sync modes show correctly in connection replication settings UI and users can now make changes in their connection setting page.

Thank you for your patience while we worked to resolve this issue and apologies for any inconvenience this issue might have caused.

The issue has been identified and the team is working on a fix.

Please continue to refrain from making any changes to your connection settings.

The issue has been resolved.

Thank you for your patience as we worked to bring this issue to resolution.

We implemented a fix and currently monitoring the result.

We are continuing to work on a fix for this incident. We believe we have found the root cause and are testing an update.

We just resolved the issue!

The root cause for this issue has been determined. Incremental streams can be successfully created as long as the user sets the "Cursor field" and "Primary key" for the stream.

We are pushing a change to no longer select Incremental syncs by default, while we work to improve UI clarity around this point.