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

ClickPipes failing on Kinesis in AWS us-east-1

Reported by ClickHouse Cloud · Databases · source last read 4 min ago

Official source (opens in a new tab)
Vendor start
Sep 15, 2026, 18:57 UTC
Vendor's clock
Resolved
Sep 17, 2026, 00:43 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 d 5 h
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

  • ClickHouse Cloud reports degraded: "ClickPipes failing on Kinesis in AWS us-east-1".[E1, E2]
  • The vendor marked it resolved at 2026-09-17 00:43 UTC.[E3, E7]

Affected products and regions

  • Regions: us-east-1 (read from the title, so inferred).[E5]

What is unknown

  • Which components are affected: the vendor did not say.[E6]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-09-17 00:43 UTC · summary s1, evidence 6d368ace71a5c19c

Evidence (7)
  1. E1ClickHouse Cloud reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "ClickPipes failing on Kinesis in AWS us-east-1". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-09-15 18:57 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): us-east-1. (Statuswall)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2026-09-17 00:43 UTC. (vendor)

Affected scope

us-east-1

Components: not stated by the vendor

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

Potential relevance

ClickHouse Cloud 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. Sep 15, 2026, 18:57 UTCVendor-reported startVendor time
  2. Sep 17, 2026, 00:43 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.