Data Sync

99.39% uptime
Apr 2024 · 99.94%May · 98.29%Jun · 100.0%
Apr 202499.94% uptime
May 202498.29% uptime
Jun 2024100.0% uptime

WebApp

99.96% uptime
Apr 2024 · 99.87%May · 100.0%Jun · 100.0%
Apr 202499.87% uptime
May 2024100.0% uptime
Jun 2024100.0% uptime

Notifications

100.0% uptime
Apr 2024 · 100.0%May · 100.0%Jun · 100.0%
Apr 2024100.0% uptime
May 2024100.0% uptime
Jun 2024100.0% uptime

Normalization

100.0% uptime
Apr 2024 · 100.0%May · 100.0%Jun · 100.0%
Apr 2024100.0% uptime
May 2024100.0% uptime
Jun 2024100.0% uptime

Airbyte Homepage (Airbyte.com)

100.0% uptime
Apr 2024 · 100.0%May · 100.0%Jun · 100.0%
Apr 2024100.0% uptime
May 2024100.0% uptime
Jun 2024100.0% uptime

Third Party Component

Operational

Airbyte API

100.0% uptime
Apr 2024 · 100.0%May · 100.0%Jun · 100.0%
Apr 2024100.0% uptime
May 2024100.0% uptime
Jun 2024100.0% uptime

Connector Builder

Operational

Notice history

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)

Apr 2024

Source Linkedin - Array field as source-defined primary key issue with Destination BigQuery.
  • Resolved
    Resolved

    This incident has been resolved. All impacted users should now be able to update source schema to use a healthy Primary Key and return syncs to a healthy state.

  • Identified
    Identified

    We are continuing to see issues while processing complex primary keys(array/JSON type) that are output by Linked In Ads for users syncing to destination BigQuery. We are continuing to work on a fix for this incident.

  • Monitoring
    Monitoring

    We implemented a fix and are currently monitoring the result. This fix is a breaking change and will require a reset on your connection. More information here.

  • Identified
    Identified

    There are issues with processing complex primary keys(array/JSON type) that are output by Linked In Ads for users syncing to destination BigQuery. We are continuing to work on a fix for this incident.

  • Investigating
    Investigating
    We are currently investigating this incident.

Apr 2024 to Jun 2024