Airbyte - Notice history

All systems operational

Data Sync - Operational

100% - uptime
Jan 2023 · 100.0%Feb · 99.87%Mar · 99.96%

Previous page

Next page

Jan 2023
Feb 2023
Mar 2023

WebApp - Operational

100% - uptime
Jan 2023 · 100.0%Feb · 100.0%Mar · 99.97%

Previous page

Next page

Jan 2023
Feb 2023
Mar 2023

Notifications - Operational

100% - uptime
Jan 2023 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2023
Feb 2023
Mar 2023

Normalization - Operational

100% - uptime
Jan 2023 · 100.0%Feb · 99.87%Mar · 100.0%

Previous page

Next page

Jan 2023
Feb 2023
Mar 2023

Airbyte Homepage (Airbyte.com) - Operational

100% - uptime
Jan 2023 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2023
Feb 2023
Mar 2023

Third Party Component - Operational

Airbyte API - Operational

100% - uptime
Jan 2023 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2023
Feb 2023
Mar 2023

Connector Builder - Operational

Notice history

Mar 2023

Airtable source: Revoked third-party integration access.
  • Resolved
    Resolved

    A fix has been pushed.

    If your connection has been failing with '400 Client Error: Bad Request for url: https://airtable.com/oauth2/v1/token' permissions error, please re-authenticate one last time.

    We apologize for this inconvenience and thank you for your patience while worked to resolve the issue.

  • Monitoring
    Monitoring

    We implemented a fix and are currently monitoring the result.

  • Identified
    Update

    We are continuing to work on a permanent solution for the Airtable source authentication.

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

    We are still continuing to work on a permanent solution for the Airtable source authentication.

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

    We are continuing to work on a permanent solution for the Airtable source authentication.

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

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

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

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

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

    We are continuing to work on a permanent solution for the Airtable source authentication.

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

    We are still continuing to work on a permanent solution for the Airtable source authentication.

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

    The team is continuing their work on a permanent fix for the Airtable source authentication.

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

    We are continuing to work on a permanent fix for Airtable source authentication.

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

    We are continually working on a permanent solution for Airtable authentication.

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

    We are continuing to work with Airtable to sort out the authentication for our integration.

    As a temporary workaround: You can re-authenticate your Airtbale connector and run a sync.

  • Identified
    Update

    We are still trying to work with Airtable to sort out why our integration authentication was revoked and reestablish the integration.

    The current workaround is still to re-authenticate and to rerun your sync.

    We apologize for the inconvenience and hope to have this issue resolved soon.

  • Identified
    Identified

    We are seeing a number of failures for Airtable source connections due to Airtable revoking Airbyte as a third-party integration.

    The following error will be seen in the Airbyte UI:
    2023-03-27 07:58:17 - Additional Failure Information: '400 Client Error: Bad Request for url: https://airtable.com/oauth2/v1/token'

    You can reauthenticate and run a sync for a temporary fix.

    We currently working on a fix for this incident.

CDC enabled Postgres source: Casting from string to integer
  • Resolved
    Resolved

    We discovered an issue with CDC-enabled Postgres source connections. Datatypes were casting from string to integer causing some failures.

    This incident has since been resolved.

Some Airbyte Cloud Pages Not Loading - "Oops Something Went Wrong"
  • Resolved
    Resolved

    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.

  • Monitoring
    Monitoring

    We have identified and implemented a fix and are monitoring the fix.

  • Investigating
    Investigating

    We are currently investigating this incident.

Credit Page is Inaccessible
  • Resolved
    Resolved

    This incident has been resolved.

  • Monitoring
    Monitoring

    We implemented a fix and are currently monitoring the result.

  • Identified
    Identified

    We have identified the issue and working on resolving the issue.

  • Investigating
    Investigating

    Our credit and billing page is currently inaccessible and we are currently investigating this issue.

Destination Snowflake regex pattern errors
  • Resolved
    Resolved

    This incident has been resolved.

  • Monitoring
    Monitoring

    We implemented a fix and are currently monitoring the result.

  • Identified
    Identified

    The team has identified the issue and we are continuing to work on a fix for this incident.

  • Investigating
    Investigating

    We noticed a large amount of user's with Snowflake destination are currently failing to errors that mention Errors: [$.host: does not match the regex pattern.

    We are currently investigating this incident.

Feb 2023

Upgrade of production node pool machine types to offer faster syncs
  • Completed
    February 24, 2023 at 4:44 PM
    Completed
    February 24, 2023 at 4:44 PM

    Maintenance has completed successfully.

  • In progress
    February 24, 2023 at 4:00 PM
    In progress
    February 24, 2023 at 4:00 PM

    Maintenance is now in progress

  • Planned
    February 24, 2023 at 4:00 PM
    Planned
    February 24, 2023 at 4:00 PM

    We are upgrading our production machines type hardware to more powerful one, this will help to speed up our syncs.
    Because of the implemented retries mechanism we do not anticipate any action needed on the part of customers.

    Thank you for your patience as we upgrade Airbyte.

Migrating from Airbtye.io to Airbyte.com on February 23rd
  • Completed
    February 23, 2023 at 7:28 PM
    Completed
    February 23, 2023 at 7:28 PM

    The migration has completed successfully.

    All previously succeeding syncs that experienced a failure during the migration should succeed on the next run. The only exception is for the Snapchat Marketing, please re-authenticate your connector to allow further syncs to succeed.

    Thank you for your patience during this maintenance and reach out to Airbyte Cloud support with any questions.

  • Update
    February 23, 2023 at 4:00 PM
    In progress
    February 23, 2023 at 4:00 PM

    We are migrating from Airbtye.io to Airbyte.com on February 23rd. All traffic pointed to Airbyte.io should automatically be redirected to Airbyte.com. We are addressing a long tail of small problems where some hardcoded URLs must be changed. Most syncs should be successful. A small number of connectors and some EU syncs will fail for a short period as we resolve this.

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

  • In progress
    February 23, 2023 at 4:00 PM
    In progress
    February 23, 2023 at 4:00 PM

    We are migrating from Airbtye.io to Airbyte.com on February 23rd. All traffic pointed to Airbyte.io should automatically be redirected to Airbyte.com. We are addressing a long tail of small problems where some hardcoded URLs must be changed. Most syncs should be successful. A small number of connectors and some EU syncs will fail for a short period as we resolve this.

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

Upgrade of production node pool machine types to offer faster syncs
  • Completed
    February 23, 2023 at 5:00 PM
    Completed
    February 23, 2023 at 5:00 PM

    Maintenance has completed successfully

  • Update
    February 23, 2023 at 4:00 PM
    Planned
    February 23, 2023 at 4:00 PM

    Maintenance is now in progress

  • Planned
    February 23, 2023 at 4:00 PM
    Planned
    February 23, 2023 at 4:00 PM

    We are upgrading our production machines type hardware to more powerful one, this will help to speed up our syncs.
    Because of the implemented retries mechanism we do not anticipate any action needed on the part of customers.

    Thank you for your patience as we upgrade Airbyte.

Slow Loading Times & Sync Failures on Airbtye Cloud
  • Resolved
    Resolved

    We just resolved the issue!

  • Monitoring
    Monitoring

    We have identified the issue which ocurred during an update to the Airbyte platform.

    We saw some slow loading pages and also determined that some sync were failing during normalization. Connections that saw failures should succeed on the next sync.

    We are currently still monitoring to ensure we are stable.

  • Investigating
    Investigating

    We have noticed some slow loading on Airbtye Cloud and are currently investigating the issue.

Invalid Certificate for cloud.airbyte.com
  • Resolved
    Resolved

    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.

Jan 2023

High number of normalization failures
  • Resolved
    Resolved

    We have implemented a fix for all normalization errors related to this issue.

    Thank you again for your patience while the team worked to resolve this issue.

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

  • Monitoring
    Update

    We are still actively triaging and monitoring the fixes we have implemented.

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

  • Monitoring
    Update

    We are continually triaging and monitoring the fixes we are implementing.

    We thank you for you continued patience.

  • Monitoring
    Update

    We are continuing to actively triage and monitor normalization failures.

    Thank you for your patience.

  • Monitoring
    Update

    After monitoring the issue we have found further normalization errors and are looking into another route to resolve these failures.

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

  • Monitoring
    Update

    We have implemented a fix that we are seeing is resolving most of the normalization issues.

    We are still seeing a small subset of connections with sources that have complex schemas failing with normalization errors.

    As these errors arise we are taking action to resolve the issue.

    Thank you again for your patience and please reach out to Airbyte Cloud support if you have any questions while we continue to ensure all normalization failures have been resolved.

  • Monitoring
    Monitoring

    We implemented a fix and currently monitoring the result.

  • Identified
    Update

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

  • Identified
    Identified

    We have noticed a number of syncs failing due to errors with normalization for multiple users. We are working on a fix to resolve this issue.

    We apologize for any inconvenience and thank you for your patience

High number of normalization failures
  • Resolved
    Resolved

    This issue has been resolved. If your most recent sync failed, we expect the next sync to succeed.

    We apologize for the inconvenience and thank you for your patience as the team worked to resolve the issue.

  • Monitoring
    Monitoring

    We have noticed a number of syncs failing due to errors with normalization for multiple users. We believe this was caused by a recent deployment that has since been reverted and are monitoring the change

    We apologize for any inconvenience and thank you for your patience

Sync Failures
  • Resolved
    Resolved

    A small subset of workspaces may have experienced a single sync failure or a failed sync attempt due to a brief platform interruption.

    The next scheduled sync should succeed.

    We apologize for any inconvenience and thank you for your patience

Slow loading UI
  • Resolved
    Resolved

    We just resolved the issue!

  • Monitoring
    Monitoring

    We implemented a fix and currently monitoring the result.

  • Identified
    Identified

    We are currently seeing the UI load slowly again due to a third-party issue.

    They are currently working on a fix. This is not affecting connections in any way.

  • Monitoring
    Monitoring

    We implemented a fix and currently monitoring the result.

  • Investigating
    Investigating

    We are currently investigating this incident.

    This is not affecting any data syncs and connections should be running as expected.

Kubernetes cluster update.
  • Completed
    January 17, 2023 at 12:00 PM
    Completed
    January 17, 2023 at 12:00 PM

    Maintenance has completed successfully

  • In progress
    January 17, 2023 at 10:00 AM
    In progress
    January 17, 2023 at 10:00 AM

    Maintenance is now in progress

  • Planned
    January 17, 2023 at 10:00 AM
    Planned
    January 17, 2023 at 10:00 AM

    We are planning for a scheduled maintenance during that time.

Jan 2023 to Mar 2023

Next