Live / Providers / Temporal
Temporal
temporal.ioReporting incidents
SaaS & business software · SquidGrid tracks Temporal’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.
Public — what Temporal is reporting
Current & recent incidents
ResolvedElevated latency and errors in GCP us-west1
None impact · 2026-10-14 13:36 UTC · source
ResolvedIncreased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UI
None impact · 2026-10-05 20:52 UTC · source
Track record
SquidGrid has archived 15 incidents from Temporal’s own status page since 2026-09-01.
- 1 rated major or critical in the last 90 days
- Median time from first post to resolved: 3 h (last 180 days)
- Longest in the last 90 days: 10.5 h
- Most recent incident: 9 days ago
- 1 open right now
- Status page last checked 2026-11-16 01:28 UTC
Recent incidents in the archive
With SquidGrid — where the route changes
Independent path health
A status page tells you what Temporal has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.
Temporal runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Temporal is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.
🔒 Sign in to see
Incident track record: 90-day trend, median and worst time to fix
What tends to break, from their own incident write-ups
Recent public reports of problems with this service
Included with any paid plan.
See the full report →