Airbyte - Notice history

All systems operational

Data Sync - Operational

100% - uptime
Jul 2022 · 100.0%Aug · 100.0%Sep · 100.0%

Previous page

Next page

Jul 2022
Aug 2022
Sep 2022

WebApp - Operational

100% - uptime
Jul 2022 · 100.0%Aug · 100.0%Sep · 99.72%

Previous page

Next page

Jul 2022
Aug 2022
Sep 2022

Notifications - Operational

100% - uptime
Jul 2022 · 100.0%Aug · 100.0%Sep · 100.0%

Previous page

Next page

Jul 2022
Aug 2022
Sep 2022

Normalization - Operational

100% - uptime
Jul 2022 · 100.0%Aug · 100.0%Sep · 100.0%

Previous page

Next page

Jul 2022
Aug 2022
Sep 2022

Airbyte Homepage (Airbyte.com) - Operational

100% - uptime
Jul 2022 · 100.0%Aug · 100.0%Sep · 100.0%

Previous page

Next page

Jul 2022
Aug 2022
Sep 2022

Third Party Component - Operational

Airbyte API - Operational

100% - uptime
Jul 2022 · 100.0%Aug · 100.0%Sep · 100.0%

Previous page

Next page

Jul 2022
Aug 2022
Sep 2022

Connector Builder - Operational

Notice history

Sep 2022

Worker Pods Unable to Start Up, Affecting the Initiation of all New Syncs
  • Resolved
    Resolved

    We just resolved the issue!

    No action on the user end is needed on affected syncs to start again.

    Thank you all for your patience as we worked this out.

  • Monitoring
    Monitoring

    We have implemented a fix and currently monitoring the result.

  • Investigating
    Investigating

    We have found an issue where worker pods are unable to start up. This will keep new syncs from starting (old + new connections).

    We are currently investigating the root cause of the issue, and are working quickly to revert the changes.

    Updates to follow as soon as we have them.

Toggling Connections on the Connection Page Changes Destination Namespace Setting
  • Resolved
    Resolved

    We just resolved the issue. Thank you for your patience while we worked to fix this issue.

  • Identified
    Identified

    We have identified an issue that affects the Destination Namespace settings for a connection when the connection is toggle (on/off) on the 'Connection' list page.

    If a connection with Destination Namespace set to ‘Custom format’, is then toggled (enabled/disabled) from the ‘Connections’ list page, the Destination Namespace will be set from ‘Custom format’ to ‘Mirror source structure’.

    We apologies for the inconvenience and we are actively working towards a fix.

'Cron' Replication Setting Saving as 'Manual'
  • Resolved
    Resolved

    We just resolved the issue for both Cloud and OSS. Frequency changes should are now working as expected.

    Thank you all for your patience as we resolved this.

  • Identified
    Identified

    The root cause has been identified (currently affecting OSS and Cloud users) and we are working on a fix now.

    Updates to come as we finish up and deploy the fix.

  • Investigating
    Investigating

    We are currently experiencing an issue where users try and save the cron replication setting, it defaults to manual.

    We are working to identify and resolve this. Updates to follow as soon as we know more.

Destination BigQuery Sync Not Using GCS staging and A Custom Namespace Look Successful but are Failing
  • Resolved
    Resolved

    After monitoring the implemented fix we have confirmed this issue has been resolved.

    If you were affected by this issue, we recommend running a reset to ensure your data is accurate and up-to-date.

    Please reach out to Airbyte Technical Cloud support if you have questions!

    Thank you for your patience and apologies for any inconvenience this issue has caused.

  • Monitoring
    Monitoring

    We are now testing a solution internally and currently monitoring the result.

    Updates to come here when all tests pass and we deploy to cloud. Thanks for your patience as we work to resolve this!

  • Identified
    Update

    Update: This issue is affecting destinations BigQuery + BigQuery (denormalized typed struct).

    Workaround for both destinations: Use the default dataset setup for your BigQuery destination settings, not the custom namespace. In this case, we suggest resesting and syncing fresh.

    More updates to come as we continue towards a resolution.

  • Identified
    Identified

    Workaround identified: Use the default dataset setup for your BigQuery destination settings, not the custom namespace.

    More updates to come as we continue towards a resolution.

  • Investigating
    Investigating

    We are currently investigating an issue with the BigQuery destination. The connector is successfully pushing data, but to the wrong location.

    The connector looks successful but is failing for new data past September 12th.

    We will update here with more information as soon as we have it.

Failed Syncs Caused by Increased Load
  • Resolved
    Resolved

    We just resolved the issue! We experienced unexpected network traffic that overloaded our system which led to some unique errors. We have addressed the issue by bolstering our infrastructure and enabled two additional IP addresses. If you have a database connector or other connector that requires IPs to be whitelisted, you may need to make sure that all of the following IP addresses are whitelisted : 34.106.109.131 | 34.106.196.165 | 34.106.60.246 Sorry for the inconvenience and we appreciate your understanding.

  • Monitoring
    Monitoring

    A fix has been pushed and we are monitoring the update.

  • Investigating
    Investigating

    Our platform is seeing increased load we are seeing high error rates in jobs.

    Sorry for the inconvenience while we are investigating this issue.

Aug 2022

Syncs Failing
  • Resolved
    Resolved

    We experienced an outage due to an update where syncs would fail during the hours of 2:23 PM to 3:10 PM MST. Apologies for any disruption and thank you for your patience while we worked towards a resolution. All connection should be running as expected.

Jul 2022

Hubspot Connections Fail when Fetching Associations
  • Resolved
    Resolved

    The Hubspot connector experienced 36 minutes of downtime due to an update that affected fetching associations on July 29th. The team quickly reverted the changes and connection began to succeed.

Maintenance Window
  • Completed
    July 26, 2022 at 10:36 AM
    Completed
    July 26, 2022 at 10:36 AM

    Maintenance has completed successfully.

  • In progress
    July 26, 2022 at 10:00 AM
    In progress
    July 26, 2022 at 10:00 AM

    Maintenance is now in progress

  • Planned
    July 26, 2022 at 9:00 AM
    Planned
    July 26, 2022 at 9:00 AM

    Kubernetes cluster update. Maintenance didn't start yet.

Jul 2022 to Sep 2022

Next