https://approjects-vendor-status-watch.static.hf.space/v/confluent.htmlIncidents from Confluent's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/c6dwlzjgjdc4confluent:2026-09-15T23:59:22.735ZTue, 15 Sep 2026 23:59:22 +0000This incident has been resolved.https://stspg.io/wmqt41lq5q45confluent:2026-09-08T20:01:29.000ZTue, 08 Sep 2026 20:01:29 +0000The issues is now resolved. Connectivity to AWS us-east-1 should be fully operational.https://stspg.io/kqjcc6c3r8qfconfluent:2026-09-08T09:17:37.373ZTue, 08 Sep 2026 09:17:37 +0000The systems have recovered and Confluent Cloud is fully operational.https://stspg.io/t0syqzdkvc44confluent:2026-09-01T16:27:06.981ZTue, 01 Sep 2026 16:27:06 +0000The GCP issue affecting the us-central1 region has been mitigated and all Confluent Cloud services in the region have returned to normal operation. Provisioning capability, error rates and latency have recovered to expected levels. Customers should no longer experience impact. If you continue to see any issues, please contact Confluent Support.https://stspg.io/5wt8kn9m95tjconfluent:2026-08-25T04:17:43.970ZTue, 25 Aug 2026 04:17:43 +0000Confluent services in the Azure Southeast Asia region are now healthy and operating normally.https://stspg.io/1vjp6vl24zpsconfluent:2026-08-23T21:00:00.000ZSun, 23 Aug 2026 21:00:00 +0000Between 21:15 – 22:30 UTC and 00:05 – 01:15 UTC on Aug 23–24, 2026, Confluent Cloud logging service was degraded. Customers may notice missing Connect and Flink logs in the Confluent Cloud UI, the Confluent CLI, and configured logging integration destinations during these windows. Other log types and the Connect / Flink workloads themselves were unaffected. The issue has been mitigated.https://stspg.io/7s3xlkvbvy9xconfluent:2026-08-20T17:10:10.282ZThu, 20 Aug 2026 17:10:10 +0000The GCP issues in us-west1 region have been mitigated. Confluent services are no longer seeing any impact based on our monitoring.https://stspg.io/3rlyl3f3zwjxconfluent:2026-07-17T22:01:05.506ZFri, 17 Jul 2026 22:01:05 +0000All the statements should be running now.https://stspg.io/rd4yxrg03rvsconfluent:2026-07-15T23:33:34.173ZWed, 15 Jul 2026 23:33:34 +0000The issue impacting the AWS eu-central-1 region has now been resolved. All clusters are fully operational and healthy.https://stspg.io/h9lmytg6dph1confluent:2026-07-13T14:25:44.138ZMon, 13 Jul 2026 14:25:44 +0000This incident has been resolved.https://stspg.io/pgcqbdb17v44confluent:2026-06-29T17:44:47.262ZMon, 29 Jun 2026 17:44:47 +0000This incident has been resolved.https://stspg.io/bk119p381b3lconfluent:2026-06-29T11:40:42.000ZMon, 29 Jun 2026 11:40:42 +0000This incident has been resolved.https://stspg.io/6fvs943zgjnbconfluent:2026-06-25T15:59:11.533ZThu, 25 Jun 2026 15:59:11 +0000This incident has been resolved.https://stspg.io/lthjwrmh3506confluent:2026-06-23T04:30:00.000ZTue, 23 Jun 2026 04:30:00 +0000On June 23rd, between 7:00 to 7:16 UTC the Confluent Cloud Metrics API was unavailable. Confluent has identified the issue and restored functionality.https://stspg.io/bnqhx8chtf8gconfluent:2026-06-21T07:14:59.000ZSun, 21 Jun 2026 07:14:59 +0000This incident has been resolved.https://stspg.io/3tp074wtdz16confluent:2026-06-16T16:02:07.000ZTue, 16 Jun 2026 16:02:07 +0000No further issues have been observed. The incident is now resolved as of 2026-06-16 17:58 UTC.https://stspg.io/h0jlmdjmj2pjconfluent:2026-06-12T07:42:15.393ZFri, 12 Jun 2026 07:42:15 +0000This incident has been resolved.https://stspg.io/78q7jr24kqbpconfluent:2026-05-29T05:57:51.720ZFri, 29 May 2026 05:57:51 +0000The Multi Service degradation on Azure has been mitigated. Confluent Cloud is operating normally.https://stspg.io/fy9tth9szn2nconfluent:2026-05-22T00:21:51.280ZFri, 22 May 2026 00:21:51 +0000The incident has been resolved.https://stspg.io/br3hbb97ft7rconfluent:2026-05-08T01:14:00.584ZFri, 08 May 2026 01:14:00 +0000The incident has been resolved and us-east-1 (use1-az4) is fully operational.https://stspg.io/4w6cd9lddrg9confluent:2026-05-06T22:12:13.716ZWed, 06 May 2026 22:12:13 +0000The maintenance is complete.https://stspg.io/qw5jby3c02wbconfluent:2026-04-24T17:18:15.361ZFri, 24 Apr 2026 17:18:15 +0000This incident has been resolved.https://stspg.io/vfmk6fwpxzzpconfluent:2026-04-21T09:34:28.929ZTue, 21 Apr 2026 09:34:28 +0000This incident has been resolved.https://stspg.io/mqw2yg36sy23confluent:2026-03-20T13:58:18.753ZFri, 20 Mar 2026 13:58:18 +0000Resolved.https://stspg.io/xqhsd157m43cconfluent:2026-03-05T04:40:11.173ZThu, 05 Mar 2026 04:40:11 +0000Confluent Cloud Metrics API are now fully functional. The incident has been resolved and systems are functioning as normal.https://stspg.io/695lzy5z6fl2confluent:2026-03-02T07:19:27.054ZMon, 02 Mar 2026 07:19:27 +0000This incident has been resolved.https://stspg.io/zhr406mnzqqpconfluent:2026-03-01T18:08:42.883ZSun, 01 Mar 2026 18:08:42 +0000This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region.https://stspg.io/5h0sqqqyghn1confluent:2026-02-26T19:56:30.188ZThu, 26 Feb 2026 19:56:30 +0000This incident has been resolved.https://stspg.io/x3nggj5qr2whconfluent:2026-02-26T13:59:54.118ZThu, 26 Feb 2026 13:59:54 +0000This incident has been resolved.https://stspg.io/zchnlr4d6qvyconfluent:2026-02-25T05:01:53.981ZWed, 25 Feb 2026 05:01:53 +0000This incident has been resolved.