CHYP.ai · ORBIT // Cloudy_Day Security Suite

Outages · Databases & data

Operational Confluent Cloud outage dossier

confluent.io · Official status page (Statuspage-compatible JSON)

Official status now

Operational Operational

checked 0 min ago How we score status

All Systems Operational

Read just now from: Official status page (Statuspage-compatible JSON) · official page ↗

ORBIT score

100

Clear skies: official status: Operational

At a glance

20official incidents, 90 d
100%of our checks clean (7)
3.7 hmedian time to resolve
0visitor reports, 24 h
0reports, last 15 min
0status changes recorded

90-day timeline (1 day tracked)

2026-08-24: no data yet2026-08-25: no data yet2026-08-26: no data yet2026-08-27: no data yet2026-08-28: no data yet2026-08-29: no data yet2026-08-30: no data yet2026-08-31: no data yet2026-09-01: no data yet2026-09-02: no data yet2026-09-03: no data yet2026-09-04: no data yet2026-09-05: no data yet2026-09-06: no data yet2026-09-07: no data yet2026-09-08: no data yet2026-09-09: no data yet2026-09-10: no data yet2026-09-11: no data yet2026-09-12: no data yet2026-09-13: no data yet2026-09-14: no data yet2026-09-15: no data yet2026-09-16: no data yet2026-09-17: no data yet2026-09-18: no data yet2026-09-19: no data yet2026-09-20: no data yet2026-09-21: no data yet2026-09-22: no data yet2026-09-23: no data yet2026-09-24: no data yet2026-09-25: no data yet2026-09-26: no data yet2026-09-27: no data yet2026-09-28: no data yet2026-09-29: no data yet2026-09-30: no data yet2026-10-01: no data yet2026-10-02: no data yet2026-10-03: no data yet2026-10-04: no data yet2026-10-05: no data yet2026-10-06: no data yet2026-10-07: no data yet2026-10-08: no data yet2026-10-09: no data yet2026-10-10: no data yet2026-10-11: no data yet2026-10-12: no data yet2026-10-13: no data yet2026-10-14: no data yet2026-10-15: no data yet2026-10-16: no data yet2026-10-17: no data yet2026-10-18: no data yet2026-10-19: no data yet2026-10-20: no data yet2026-10-21: no data yet2026-10-22: no data yet2026-10-23: no data yet2026-10-24: no data yet2026-10-25: no data yet2026-10-26: no data yet2026-10-27: no data yet2026-10-28: no data yet2026-10-29: no data yet2026-10-30: no data yet2026-10-31: no data yet2026-11-01: no data yet2026-11-02: no data yet2026-11-03: no data yet2026-11-04: no data yet2026-11-05: no data yet2026-11-06: no data yet2026-11-07: no data yet2026-11-08: no data yet2026-11-09: no data yet2026-11-10: no data yet2026-11-11: no data yet2026-11-12: no data yet2026-11-13: no data yet2026-11-14: no data yet2026-11-15: no data yet2026-11-16: no data yet2026-11-17: no data yet2026-11-18: no data yet2026-11-19: no data yet2026-11-20: no data yet2026-11-21: 7 checks, 0 with an official incident (worst: none)90 days agotoday

Each bar is a day. Green: our checks found no official incident. Amber/red: the provider reported one. Grey: before ORBIT started tracking this service. This is "share of our checks with no official incident", not the provider's SLA.

Official incidents per week

2 incident(s), week ending 2026-08-2921 incident(s), week ending 2026-09-0512 incident(s), week ending 2026-09-1222 incident(s), week ending 2026-09-1924 incident(s), week ending 2026-09-2641 incident(s), week ending 2026-10-0313 incident(s), week ending 2026-10-1032 incident(s), week ending 2026-10-1721 incident(s), week ending 2026-10-2410 incident(s), week ending 2026-10-311 incident(s), week ending 2026-11-0710 incident(s), week ending 2026-11-141 incident(s), week ending 2026-11-21113 weeks agothis weekmax 4/week

Impact mix, 90 d

11 major5 minor1 maintenance3 none20
  • 1 maintenance
  • 5 minor
  • 11 major
  • 3 none

Visitor reports, last 24 h

24 h agonow · peak 1/15 min

Unverified reports from ORBIT visitors, in 15-minute buckets. Add yours.

Incident history

  1. → resolved · lasted 23.5 hNew Confluent Cloud account sign-ups temporarily unavailablemaintenance resolved · Confluent Cloud · official notice ↗ · replay & discuss
  2. → resolved · lasted 2.2 hKafka - Increased latency and connectivity issues - Azure - brazilsouthminor resolved · Confluent Cloud · official notice ↗ · replay & discuss
  3. → resolved · lasted 3.7 hMultiple Confluent Cloud services are in a degraded state - GCP EU-West2major resolved · Confluent Cloud · official notice ↗ · replay & discuss
  4. → resolved · lasted 3.8 hDelay in Kafka cluster provisioningminor resolved · Confluent Cloud · official notice ↗ · replay & discuss
  5. → resolved · lasted 2.8 hConfluent Cloud Console (UI) degraded functionalitynone resolved · Confluent Cloud · official notice ↗ · replay & discuss
  6. → resolved · lasted 56 minPossible outage in AWS us-east-1major resolved · Confluent Cloud · official notice ↗ · replay & discuss
  7. → resolved · lasted 10.6 hExperiencing high error rate in AZURE in West Europe regionmajor resolved · Confluent Cloud · official notice ↗ · replay & discuss
  8. → resolved · lasted 56 minExperiencing high error rate in AZURE in Germany West Central regionmajor resolved · Confluent Cloud · official notice ↗ · replay & discuss
  9. → resolved · lasted Missing Metrics on Confluent Cloudmajor resolved · official notice ↗ · replay & discuss
  10. → resolved · lasted 13.1 hElevated error rates in Azure East USminor resolved · Confluent Cloud · official notice ↗ · replay & discuss
  11. → resolved · lasted 11.5 hConfluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2major resolved · Confluent Cloud · official notice ↗ · replay & discuss
  12. → resolved · lasted 4.8 hElevated error rates in Azure Germany West Central regionmajor resolved · Confluent Cloud · official notice ↗ · replay & discuss
  13. → resolved · lasted 9.3 hConfluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2major resolved · Confluent Cloud · official notice ↗ · replay & discuss
  14. → resolved · lasted Confluent Cloud Metrics API experienced elevated latency and error ratesnone resolved · official notice ↗ · replay & discuss
  15. → resolved · lasted 1.4 hMultiple Confluent Cloud services are in a degraded state - All regionsmajor resolved · Confluent Cloud · official notice ↗ · replay & discuss
  16. → resolved · lasted 17 hConnectivity degradation - AWS us-east-1major resolved · Confluent Cloud · official notice ↗ · replay & discuss
  17. → resolved · lasted 29.7 hService Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1minor resolved · Confluent Cloud · official notice ↗ · replay & discuss
  18. → resolved · lasted 48 minInvestigating Elevated Errors in GCP us-central1minor resolved · Confluent Cloud · official notice ↗ · replay & discuss
  19. → resolved · lasted 3.2 hElevated error rates and latencies in Azure Southeast Asia regionmajor resolved · Confluent Cloud · official notice ↗ · replay & discuss
  20. → resolved · lasted Confluent Cloud logging degradation - Connect and Flinknone resolved · official notice ↗ · replay & discuss

Related services

"Runs on" links are inferred from public information and may be outdated.

How we score status

  1. Source. Every reading comes from the provider's own public status page or status API (Statuspage, Instatus, incident.io-style JSON, or the provider's RSS/JSON). ORBIT never pings or scans the service.
  2. Scope. For each open incident we count the regions or components it names against the total the provider publishes, and label it global, multi-region, 1 region or n of N components.
  3. Age. Incidents are new (under 1 hour), active, long-running (open more than 48 hours) or stale (no provider update for 24 hours or more).
  4. Headline. The headline colour comes from current incidents only. A single-region or small-scope incident caps the headline at "Degraded"; a global or widespread one keeps the provider's impact. Long-running or stale issues limited to one region or a few components get a known long-running issue badge and don't set the headline colour.
  5. Transparency. The provider's own page-level status is always shown next to ORBIT's headline, with a link to the official page. When they differ, the provider's page is the authority on what it says.

Community comments (0)

Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.

No approved comments yet.

Where this data comes from. "Official status" is read from each provider's own public status page or status API (the same JSON or RSS their status page publishes), cached for a minute or more. ORBIT never pings, scans or probes the provider's systems. "Our checks" and history are ORBIT's own record of those readings, kept in our database. Visitor reports are unverified. Headlines are matched by name and shown for context: coincidence, not causation. Cloudy_Day is independent and not an official source for any company listed.

Where to next