Airbyte - Notice history

All systems operational

Data Sync - Operational

99.39% uptime
May 2024 · 98.29%Jun · 100.0%Jul · 99.93%

Previous page

Next page

May 2024
Jun 2024
Jul 2024

WebApp - Operational

99.99% uptime
May 2024 · 100.0%Jun · 100.0%Jul · 99.98%

Previous page

Next page

May 2024
Jun 2024
Jul 2024

Notifications - Operational

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

Previous page

Next page

May 2024
Jun 2024
Jul 2024

Normalization - Operational

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

Previous page

Next page

May 2024
Jun 2024
Jul 2024

Airbyte Homepage (Airbyte.com) - Operational

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

Previous page

Next page

May 2024
Jun 2024
Jul 2024

Third Party Component - Operational

Airbyte API - Operational

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

Previous page

Next page

May 2024
Jun 2024
Jul 2024

Connector Builder - Operational

Airbyte Agents - Operational

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

Previous page

Next page

May 2024
Jun 2024
Jul 2024

Notice history

View current status

Jul 2024

Airbyte Cloud UI not Loading
ResolvedMajor outage6 minutes
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Investigating
    UTC
    Investigating

    We are currently investigating this incident that is causing the Cloud Platform to not load properly.

    Thank you for your patience, we are working to resolve this as quickly as possible.

WebApp: Syncs not starting.
Resolved
  • Resolved
    UTC
    Resolved

    A fix has been implemented. Resolved.

Destination Postgres: Syncs failing
ResolvedPartial outage
  • Resolved
    UTC
    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.

EU Syncs Unable to Start
ResolvedDegraded performance4 hours 35 minutes
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring

    We implemented a fix and are currently monitoring the result. ~20% of EU syncs during this time period were affected and should automatically recover.

  • Investigating
    UTC
    Investigating

    We are currently investigating an issue where some syncs in the EU region are unable to start.

    Thank you for your patience while we investigate this issue.

Syncs issues detected: Syncs failing to start.
ResolvedPartial outage1 hour 46 minutes
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    UTC
    Investigating
    We are currently investigating this incident.

Jun 2024

Connector Builder temporarily not able to test connections
ResolvedPartial outage46 hours 13 minutes
  • Resolved
    UTC
    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
    UTC
    Monitoring

    A fix has been implemented and we are currently monitoring the update.

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

  • Identified
    UTC
    Identified

    You are currently not able to test any connectors in the connector builder in the Airbyte UI. We are continuing to work on a fix for this incident.

    Note: Any syncs using a connector built in the Airbyte Connector Builder are not affected by this issue.

Destination Snowflake - Connection isses: SQL Compilation Error
ResolvedPartial outage8 hours 32 minutes
  • Resolved
    UTC
    Resolved

    This incident has been resolved - please run a new sync on your connection.

  • Monitoring
    UTC
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Identified
    UTC
    Identified

    Identified: All Destination Snowflake streams running in OVERWRITE mode are failing.

  • Investigating
    UTC
    Investigating
    We are currently investigating this incident.

May 2024

Airbyte Cloud Inaccessible with Ad Blocking Browser Extensions Enabled
ResolvedDegraded performance1 hour 56 minutes
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring

    A fix has been implemented and we are currently monitoring the update.

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

  • Investigating
    UTC
    Investigating

    We are currently investigating an issue where Airbyte Cloud is inaccessible if your browser has an ad blocking extension enabled. Disabling the extension should allow you to access your workspace.

    Our team is currently investigating a potential fix and we apologize for any inconvenience caused and appreciate your patience as we work to resolve this issue.

Source: Facebook Marketing - nonexisting fields error
Resolved86 hours 32 minutes
  • Resolved
    UTC
    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
    UTC
    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
    UTC
    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
    UTC
    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)",
Secrets disabled for some users
Resolved42 hours 23 minutes
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Identified
    UTC
    Identified

    We have been informed that this issue is impacting additional users. Our team is actively working on a solution to mitigate the problem.

  • Monitoring
    UTC
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Identified
    UTC
    Identified

    We are seeing some users connections fail due to their secrets being disabled. The team is aware of this and is currently working on enabling those secrets for the affected users.

Data Sync: Long Running Syncs
Resolved106 hours 12 minutes
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    UTC
    Investigating

    Some syncs are failing and blocking for many hours before timing out.

Destination: Redshift - Long Running Syncs after Amazon Redshift Updated to version 1.0.67305
ResolvedPartial outage29 hours
  • Resolved
    UTC
    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
    UTC
    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
    UTC
    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)

Previous

May 2024 to Jul 2024

Next