Airbyte - Notice history

Data Sync - Operational

99.34% uptime
Mar 2024 · 99.82%Apr · 99.94%May · 98.29%
Mar 2024
Apr 2024
May 2024

WebApp - Operational

99.96% uptime
Mar 2024 · 100.0%Apr · 99.87%May · 100.0%
Mar 2024
Apr 2024
May 2024

Notifications - Operational

100.0% uptime
Mar 2024 · 100.0%Apr · 100.0%May · 100.0%
Mar 2024
Apr 2024
May 2024

Normalization - Operational

100.0% uptime
Mar 2024 · 100.0%Apr · 100.0%May · 100.0%
Mar 2024
Apr 2024
May 2024

Airbyte Homepage (Airbyte.com) - Operational

100.0% uptime
Mar 2024 · 100.0%Apr · 100.0%May · 100.0%
Mar 2024
Apr 2024
May 2024

Third Party Component - Operational

Airbyte API - Operational

100.0% uptime
Mar 2024 · 100.0%Apr · 100.0%May · 100.0%
Mar 2024
Apr 2024
May 2024

Connector Builder - Operational

Airbyte Agents - Operational

100.0% uptime
Mar 2024 · 100.0%Apr · 100.0%May · 100.0%
Mar 2024
Apr 2024
May 2024

Notice history

View current status

May 2024

Source: Facebook Marketing - nonexisting fields error
Resolved86 hours 32 minutes
  • ResolvedUTC

    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.

  • MonitoringUTC

    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.

  • IdentifiedUTC

    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)",
  • InvestigatingUTC

    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
ResolvedPartial outage29 hours
  • ResolvedUTC

    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.

  • MonitoringUTC

    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.

  • IdentifiedUTC

    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.
Resolved289 hours 30 minutes
  • ResolvedUTC

    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.

  • IdentifiedUTC

    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.

  • MonitoringUTC

    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.

  • IdentifiedUTC

    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.

  • InvestigatingUTC
    We are currently investigating this incident.

Mar 2024

Previous

Mar 2024 to May 2024

Next