Planned maintenanceResolved · vendor status “completed”Official status API

Kubernetes cluster update.

Reported by Airbyte · Data & Analytics · source last read 4 min ago

Vendor start
Jan 17, 2023, 12:00 UTC
Vendor's clock
Resolved
Jan 17, 2023, 12:00 UTC
Vendor's clock
First seen by Statuswall
Nov 11, 2026, 03:40 UTC
Statuswall's clock
Duration
Not available
This source does not publish reliable durations

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Airbyte reports planned maintenance: "Kubernetes cluster update.".[E1, E2]
  • The vendor marked it resolved at 2023-01-17 12:00 UTC.[E3, E7]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • 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-11-11 05:40 UTC · summary s1, evidence f7c9ad4051520e48

Evidence (9)
  1. E1Airbyte reports planned maintenance. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Kubernetes cluster update.". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "completed". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2023-01-17 12:00 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2023-01-17 12:00 UTC. (vendor) source (opens in a new tab)
  8. E8First seen by Statuswall: 2026-11-11 03:40 UTC. (Statuswall)
  9. E9Statuswall saw the vendor change severity from degraded to maintenance at 2026-11-11 05:40 UTC. (Statuswall)

Affected scope

Not stated by the vendor

Components: not stated by the vendor

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Airbyte 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. Jan 17, 2023, 12:00 UTCVendor-reported startVendor time
  2. Jan 17, 2023, 12:00 UTCVendor-reported resolutionVendor time
  3. Nov 11, 2026, 03:40 UTCFirst seen by Statuswall (vendor status: completed)Seen by Statuswall
  4. Nov 11, 2026, 05:40 UTCVendor changed severity: Degraded → MaintenanceSeen by Statuswall