# Confluent: Some GCP peering status is incorrectly reported as FAILED

> Confluent status incident “Some GCP peering status is incorrectly reported as FAILED” on 2024-05-03: impact minor (vendor’s label), 5.3 h, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/confluent/incidents/895wlsky1yv3
Last updated: 2024-05-03T23:23:00Z

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2024-05-03 18:04 UTC · Resolved: 2024-05-03 23:23 UTC · Duration: 5.3 h
- Updates: 1
- [Vendor status page: https://status.confluent.cloud/incidents/895wlsky1yv3](https://status.confluent.cloud/incidents/895wlsky1yv3)
- [Company: Confluent](https://rewindex.com/company/confluent.md)

## Timeline of updates

- **resolved** 2024-05-03 23:23 UTC: This incident has been resolved.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._

## Cite this

Status incident (vendor impact label: minor) posted by Confluent, started 2024-05-03 18:04 UTC, resolved after 5.3 h, 1 update(s).

- Canonical URL: https://rewindex.com/company/confluent/incidents/895wlsky1yv3
- Citation: Confluent, “Some GCP peering status is incorrectly reported as FAILED” (2024-05-03 18:04 UTC). Archived by Rewindex: https://rewindex.com/company/confluent/incidents/895wlsky1yv3 (CC BY 4.0).
- Markdown link: `[Confluent: Some GCP peering status is incorrectly reported as FAILED (2024-05-03)](https://rewindex.com/company/confluent/incidents/895wlsky1yv3)`


---
Canonical: https://rewindex.com/company/confluent/incidents/895wlsky1yv3 · Markdown: https://rewindex.com/company/confluent/incidents/895wlsky1yv3.md · JSON: https://rewindex.com/api/v1/companies/confluent/incidents/895wlsky1yv3 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T15:58:18.844Z