Incidentsby IbisBilling API Data Freshness Delay
Apr 10, 14:00 UTCApr 10, 14:00 UTC
Duration
0m
Impact
Informational
Root cause
Not disclosed
Temporal, 90 days
27 incidents
Affected
Not listed by the vendor.
Final update
Billing data freshness in the Billing API was delayed between 2026-04-09 08:00 UTC and 2026-04-10 14:00 UTC. During this period, recently generated billing data was not immediately reflected in API responses. This issue did not affect API availability. The delay has been resolved, and billing data is now updating within normal freshness expectations.
Timeline
- Resolved · Apr 10, 14:00 UTC
Billing data freshness in the Billing API was delayed between 2026-04-09 08:00 UTC and 2026-04-10 14:00 UTC. During this period, recently generated billing data was not immediately reflected in API responses. This issue did not affect API availability. The delay has been resolved, and billing data is now updating within normal freshness expectations.
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