Status Tracker v0.24
Incident began at 2025-01-06 11:01 and ended at 2025-01-06 12:24 (all times are US/Pacific).
The issue with Google Cloud Console, Google Cloud Support has been resolved for all affected users as of Monday, 2025-01-06 11:45 US/Pacific.
Only a few chat instances were impacted during the incident.
We thank you for your patience while we worked on resolving the issue.
Affected products: Google Cloud Console, Google Cloud Support
Affected locations: Global
Incident began at 2025-01-06 11:01 and ended at 2025-01-06 12:24 (all times are US/Pacific).
The issue with Google Cloud Console, Google Cloud Support has been resolved for all affected users as of Monday, 2025-01-06 11:45 US/Pacific.
Only a few chat instances were impacted during the incident.
We thank you for your patience while we worked on resolving the issue.
Affected products: Google Cloud Console, Google Cloud Support
Affected locations: Global
Jan 6, 17:56 UTC
Resolved – Some users may have experienced an error or increased latency when accessing the CLM user interface in UAT. Incident duration and timelines are subject to revision pending the results of any related investigation.
Customers may have experienced errors or latency from 2025-01-06 05:56 PM UTC until 2025-01-06 06:20 PM UTC.
January 6, 2025 15:27 UTC
Monitoring – We’re continuing to monitor for further errors related to the incident. We see further decreases in the errors.
January 6, 2025 15:57 UTC
Monitoring – We’ve identified the cause of the errors, and the errors have returned to normal. The incident is now mitigated, but we’re continuing to monitor for any further impact.
More information on the incident can be found in this issue: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19079
January 6, 2025 16:42 UTC
Resolved – We’ve identified the cause of the errors and the errors have returned to normal. The incident is now resolved.
More information on the incident can be found in this issue: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19079
Jan 6, 06:25 MST
Identified – The issue has been identified and a fix is being implemented.
Jan 6, 06:35 MST
Resolved – This incident has been resolved.