Incidentsby IbisSome customers may experience a loss in metrics (v0 and v1) starting 19:00 UTC
Jul 16, 22:26 UTCJul 17, 02:14 UTC
Duration
3h 48m
Impact
Minor
Root cause
Not disclosed
Temporal, 90 days
27 incidents
Affected
Google Cloud Provider (GCP) - us-east4
Final update
A configuration error caused a partial loss of metrics (v0 and v1) for some customers between 2026-07-16 19:00 UTC and 2026-07-17 02:12 UTC. We have updated the config and mitigated impact across impacted regions. All global metrics are now restored and the incident is resolved.
Timeline
- Resolved · Jul 17, 02:14 UTC
A configuration error caused a partial loss of metrics (v0 and v1) for some customers between 2026-07-16 19:00 UTC and 2026-07-17 02:12 UTC. We have updated the config and mitigated impact across impacted regions. All global metrics are now restored and the incident is resolved.
- Monitoring · Jul 17, 00:24 UTC
Mitigation is complete and global metrics are restored. We are currently monitoring.
- Identified · Jul 17, 00:00 UTC
Mitigation is still in progress and metrics are slowly being restored across namespaces.
- Identified · Jul 16, 23:21 UTC
We're in the process of mitigating impact and metrics are slowly being restored across some namespaces.
- Investigating · Jul 16, 22:42 UTC
Global metrics service has been impacted by this incident. We're working on mitigation.
- Investigating · Jul 16, 22:26 UTC
We are currently investigating, additional details to come shortly. Impact is limited to metrics only.
More from Temporal
Full historyNew namespace creation restricted across all GCP regionsstill openElevated latency and errors in GCP us-west1lasted 17mElevated latency and errors in AWS us-east-1lasted 2h 17mElevated error rates for cross-region traffic between US AWS regionslasted 0mElevated GCP storage latency in us-central1 – precautionary namespace failoverlasted 4h 25mIncreased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UIlasted 29m