Delayed delivery to Snowflake Streaming destinations (AWS us-east-1)

What to do

• Check whether you use RudderStack in us, us-east-1. 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.

• RudderStack says a fix is out: check your own error rates before you undo any failover.

• Watch RudderStack's own updates; this page re-reads them every minute.

• Subscribe to RudderStack's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=rudderstack works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from RudderStack 1

1. monitoringNov 10, 2026, 6:27 PM UTC

   Since approximately 15:12 UTC, we are seeing delayed event delivery to Snowflake Streaming destinations whose Snowflake accounts are hosted in AWS us-east-1. The delay is caused by timeouts and elevated latency from Snowflake’s Snowpipe Streaming service in that region. Event ingestion is unaffected. All events are safely queued and will be delivered once Snowflake recovers, so no data loss is expected. Other destinations and Snowflake regions are not affected. We have raised the issue with Snowflake and are monitoring closely.

   provider

Corrections

None so far.

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