Airbyte - Notice history

Data Sync - Operational

99% - uptime
May 2024 · 98.29%Jun · 100.0%Jul · 99.93%
May 2024
Jun 2024
Jul 2024

WebApp - Operational

100% - uptime
May 2024 · 100.0%Jun · 100.0%Jul · 99.98%
May 2024
Jun 2024
Jul 2024

Notifications - Operational

100% - uptime
May 2024 · 100.0%Jun · 100.0%Jul · 100.0%
May 2024
Jun 2024
Jul 2024

Normalization - Operational

100% - uptime
May 2024 · 100.0%Jun · 100.0%Jul · 100.0%
May 2024
Jun 2024
Jul 2024

Airbyte Homepage (Airbyte.com) - Operational

100% - uptime
May 2024 · 100.0%Jun · 100.0%Jul · 100.0%
May 2024
Jun 2024
Jul 2024

Third Party Component - Operational

Airbyte API - Operational

100% - uptime
May 2024 · 100.0%Jun · 100.0%Jul · 100.0%
May 2024
Jun 2024
Jul 2024

Connector Builder - Operational

Notice history

Jul 2024

Destination Postgres: Syncs failing
  • Resolved
    Resolved

    Issue resolved but any connection impacted will have missing data in the final tables. To correct this a Clear must be run on the connection. The following sync will be a historical backfill, please submit a Support Ticket via https://support.airbyte.com/hc/en-us with any questions or concerns.

May 2024

Source: Facebook Marketing - nonexisting fields error
  • Resolved
    Resolved

    This incident has been resolved.

    As a reminder, this fix is a breaking change. This requires an upgrade to the new 3.1.0 version of Facebook Marketing. Please follow the steps here to successfully update the connector.

  • Monitoring
    Monitoring

    The team has provided a fix which is a breaking change. This requires an upgrade to the new version 3.1.0 of Facebook Marketing. Please follow the steps here to successfully update the connector.

  • Identified
    Identified

    We are continuing to work on a fix for this incident. Meta Appears to have silently modified the schema of the AdsInsights endpoint for conversion_lead_rate and cost_per_conversion_lead  causing the following error message:

    "error": {
            "message": "(#100) Tried accessing nonexisting field (cost_per_conversion_lead) on node type (AdsInsights)",
  • Investigating
    Investigating

    We are currently investigating this incident. Meta Appears to have silently modified the schema of the AdsInsights endpoint for conversion_lead_rate and cost_per_conversion_lead  causing the following error message:

    "error": {
            "message": "(#100) Tried accessing nonexisting field (cost_per_conversion_lead) on node type (AdsInsights)",
Destination: Redshift - Long Running Syncs after Amazon Redshift Updated to version 1.0.67305
  • Resolved
    Resolved

    This incident has been resolved. If your connection was actively running a sync before 4:00 PM ET/1:00 PM PT, please cancel the sync and start a new one.

  • Monitoring
    Monitoring

    We implemented a fix and are currently monitoring the result. If your connection was actively running a sync before 4:00 PM ET/1:00 PM PT, please cancel the sync and start a new one.

  • Identified
    Identified

    We have identified the root cause of this issue and are actively investigating the fix. This issue is impacting Users who have updated their Redshift to version 1.0.67305 (https://docs.aws.amazon.com/redshift/latest/mgmt/cluster-versions.html#cluster-version-181)

May 2024 to Jul 2024

Next