Vendor reports: degradedResolved · vendor status “resolved”Official status API

Fivetran: Managed Data Lake Destinations Experiencing Sync Delays in GCP us-east4 Region.

Reported by Fivetran · Data & Analytics · source last read 2 min ago

Official source (opens in a new tab)
Vendor start
Oct 30, 2026, 04:10 UTC
Vendor's clock
Resolved
Oct 30, 2026, 05:00 UTC
Vendor's clock
First seen by Statuswall
Nov 11, 2026, 02:11 UTC
Statuswall's clock
Duration
50 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Fivetran reports degraded: "Fivetran: Managed Data Lake Destinations Experiencing Sync Delays in GCP us-east4 Region.".[E1, E2]
  • The vendor marked it resolved at 2026-10-30 05:00 UTC.[E3, E7]

Affected products and regions

  • Regions: us-east4 (read from the title, so inferred).[E5]
  • Components: Destinations.[E6]

What is unknown

  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-11-11 02:11 UTC · summary s1, evidence 9c1bca5d10a097d4

Evidence (8)
  1. E1Fivetran reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Fivetran: Managed Data Lake Destinations Experiencing Sync Delays in GCP us-east4 Region.". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-10-30 04:10 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): us-east4. (Statuswall) source (opens in a new tab)
  6. E6Components the vendor attached: Destinations. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-10-30 05:00 UTC. (vendor) source (opens in a new tab)
  8. E8First seen by Statuswall: 2026-11-11 02:11 UTC. (Statuswall)

Affected scope

us-east4

Components: Destinations

Read from region codes written in the incident title, so treat it as inferred.

Potential relevance

Fivetran is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Oct 30, 2026, 04:10 UTCVendor-reported startVendor time
  2. Oct 30, 2026, 05:00 UTCVendor-reported resolutionVendor time
  3. Nov 11, 2026, 02:11 UTCFirst seen by Statuswall (vendor status: resolved)Seen by Statuswall