Some customers may have incorrectly received a "credit expiry notification"
Sep 18, 15:54 UTCSep 18, 22:23 UTC
Duration
6h 29m
Impact
Minor
Root cause
Not disclosed
Temporal, 90 days
27 incidents
Affected
BillingGlobal Services - Billing
Final update
This incident has been resolved.
Timeline
- Resolved · Sep 18, 22:23 UTC
This incident has been resolved.
- Monitoring · Sep 18, 17:21 UTC
A fix has been implemented and we are currently working on sending out correction emails to affected customers.
- Identified · Sep 18, 16:00 UTC
The issue has been identified and a fix is being implemented.
- Investigating · Sep 18, 15:54 UTC
We are currently investigating this issue.
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