Airbyte: Third-Party Incident: Snowflake Service Degradation

What to do

Check whether you use Airbyte Snowflake Destination, Snowflake Source. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2025-12-16 12:54 UTC and 2025-12-16 12:54 UTC may need a replay.
Subscribe to Airbyte's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=airbyte works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

resolvedDec 16, 2025, 12:54 PM UTC
Type: Incident Duration: 4 hours and 10 minutes Affected Components: Snowflake Destination, Snowflake Source Dec 16, 17:04:00 GMT+0 - Resolved - Snowflake has resolved their outage. Dec 16, 12:54:20 GMT+0 - Investigating - We are aware of an ongoing incident affecting Snowflake, which may impact Airbyte connections that use Snowflake as a destination or source. Some users may experience failed syncs, increased latency, or intermittent errors while the Snowflake incident is ongoing. Our systems are otherwise operating normally, and we are actively monitoring the situation.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Airbyte still down?

No, this incident was resolved 2025-12-16 12:54 UTC. For Airbyte's live state, see https://down.guide/airbyte.

How long did it last?

0m, from 2025-12-16 12:54 UTC to 2025-12-16 12:54 UTC, by the times Airbyte posted.

What was affected?

Airbyte named Snowflake Destination, Snowflake Source.

What caused it?

Airbyte hasn't published a root cause. If it does, it shows here.

Where does this come from?

Airbyte's official status page, https://status.airbyte.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.