Vendor Status Watch

← all vendors

Temporal status history

Current state: operational — “All Systems Operational” per https://status.temporal.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

7incidents, last 30 days
31incidents, last 90 days
52incidents on record
Incidents per week, last 12 weeks:

How long do Temporal incidents last?

2.2 hmedian incident duration52 measured
26.7 h90th percentile1 in 10 ran longer
4.3 hmedian, major/critical only5 incidents

From 52 incidents with a vendor-posted start and resolve time. Longest on record: Some customers may be experiencing stuck workflows or activities — 13.8 days (2026-06-03 00:45 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (52)

StartedIncidentStatusImpactDuration
2026-09-11 10:10 UTCSome customers in APSE region may experience incomplete responses from Temporal Cloud metrics (OpenMetrics)resolvednone4 h 18 min
2026-09-10 20:51 UTCCustomers in us-central1 and asia-southeast2 may experience a delay in workflow progressresolvedmajor10 h 29 min
2026-09-03 21:12 UTCElevated Errors in us-west-2 Regionresolvedminor8 h 16 min
2026-09-02 15:26 UTCLow Rate of Namespace Create/Update Failures Across All Regionsresolvedminor22 min
2026-09-01 15:47 UTCElevated error rates in GCP us-central1resolvedminor5 h 55 min
2026-08-21 13:30 UTCSelf-Signup Onboarding Access Restrictionresolvednone0 min
2026-08-20 15:20 UTCCustomers in (GCP) us-west1 may experience elevated API latenciesresolvedminor3 h 39 min
2026-08-13 12:00 UTCCloud Ops API — Elevated Error Rates and Latenciesresolvednone0 min
2026-08-13 11:47 UTCCustomers in AWS us-west-2 may experience elevated API latenciesresolvedminor39 min
2026-08-05 13:17 UTCSome customers in AWS eu-west-1 may experience elevated latenciesresolvedminor2 d 5 h
2026-07-31 22:46 UTCUsage API and UI are experiencing an outageresolvedcritical2 h 13 min
2026-07-23 19:11 UTCSome customers in AWS us-west-2 may experience degraded visibility performanceresolvedminor47 min
2026-07-22 12:35 UTCSome customers in GCP us-east4 may experience elevated latenciesresolvedminor28 min
2026-07-20 18:29 UTCSome customers in AWS us-west-2 may experience degraded visibility performanceresolvedminor44 min
2026-07-20 17:44 UTCSome customers in GCP us-east4 may experience elevated latenciesresolvedminor2 h 10 min
2026-07-20 13:55 UTCSome customers may have experienced lag in Temporal Cloud metrics (OpenMetrics - v1) from 12:45 to 13:25 UTCresolvednone0 min
2026-07-20 13:47 UTCSome customers in AWS eu-west-1 may experience elevated latenciesresolvedminor7 h 02 min
2026-07-17 14:30 UTCCustomers in AWS eu-west-1 may experience elevated API latenciesresolvednone1 h 26 min
2026-07-16 22:26 UTCSome customers may experience a loss in metrics (v0 and v1) starting 19:00 UTCresolvedminor3 h 48 min
2026-07-15 16:55 UTCCustomers in us-east-2 may experience some visibility related errorsresolvedmajor4 h 19 min
2026-07-14 18:47 UTCElevated latencies in us-east-1resolvedminor1 h 10 min
2026-07-14 00:03 UTCBroken Temporal skipping test server linkresolvednone16 min
2026-07-09 16:08 UTCSome customers in AWS us-west-2 may experience unjustified throttling errorsresolvednone17 min
2026-07-08 14:26 UTCSome customers in AWS us-east-1 may experience elevated rate of API errors and elevated latenciesresolvedminor7 h 21 min
2026-07-08 02:40 UTCCustomers in AWS us-east-1 may experience elevated rate of API errors and elevated latenciesresolvedminor7 h 33 min
2026-07-07 23:25 UTCSome customers in AWS us-east-1 may experience elevated rate of transient API errorsresolvedminor10 h 39 min
2026-07-07 13:00 UTCCustomers in GCP us-east4 may experience elevated API latenciesresolvedminor6 d 11 h
2026-07-07 05:54 UTCSome customers in GCP europe-west3 may experience elevated API latenciesresolvedminor1 h 34 min
2026-07-05 18:41 UTCSome customers in AWS us-east-2 may have experienced elevated API latencies and errorsresolvednone56 min
2026-07-05 18:31 UTCSome customers in GCP us-west1 may have experienced elevated API latenciesresolvednone0 min
2026-07-01 18:02 UTCErrors on GetSystemInfo and healthcheck endpoints for latest SDK versionsresolvednone22 h 24 min
2026-06-17 21:18 UTCGCP customers in europe-west3 are experiencing elevated errors for Visibility API callsresolvedminor46 min
2026-06-12 19:09 UTCSome customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses.resolvednone44 h 56 min
2026-06-11 19:58 UTCAudit logs temporarily delayed for a few hours — no data loss.resolvedminor46 min
2026-06-11 14:34 UTCCustomers might observe Usage API returning missing or delayed dataresolvedminor58 min
2026-06-08 22:06 UTCGCP customers in us-east4 are experiencing elevated errors for Visibility API callsresolvedminor2 h 52 min
2026-06-06 02:15 UTCSome customers in AWS sa-east-1 may experience elevated API latenciesresolvedminor2 h 11 min
2026-06-03 00:45 UTCSome customers may be experiencing stuck workflows or activitiesresolvednone13 d 20 h
2026-05-29 13:31 UTCSome customers in us-west-2 may experience elevated rate of API errors & higher latenciesresolvedminor2 h 18 min
2026-05-28 20:22 UTCSome customers in AWS us-east-1 experienced a small number of gRPC UNIMPLEMENTED errorsresolvednone25 h 51 min
2026-05-27 03:00 UTCSome customers in AWS us-east-1 may observe a small number of gRPC UNIMPLEMENTED errorsresolvednone12 h 00 min
2026-05-22 23:40 UTCNamespace creation and modification availablity degradedresolvedminor2 min
2026-05-22 01:30 UTCCustomers using OpenMetric for external observability may see gaps in some metricsresolvednone4 d 21 h
2026-05-15 18:30 UTCTemporal UI was unable to display human readable execution detailsresolvednone0 min
2026-05-13 16:43 UTCSome customers in GCP us-east4 experienced elevated API latenciesresolvedminor0 min
2026-05-12 07:30 UTCSome customers in GCP us-east4 experienced elevated API latenciesresolvedminor5 h 08 min
2026-05-08 01:14 UTCSome customers in AWS us-east-1 may experience elevated API latenciesresolvedminor26 h 42 min
2026-05-05 05:43 UTCSome customers in us-west-2 may experience elevated rate of API errors and high latencyresolvedmajor16 h 02 min
2026-05-04 22:50 UTCSome customers in AWS us-east-1 may be seeing a small number of gRPC UNIMPLEMENTED errorsresolvedmajor1 h 45 min
2026-04-21 23:15 UTCDegraded Child Workflow Executionresolvedminor21 min
2026-04-15 08:58 UTCSome customers in us-west-2 experiencing increased visibility API latenciesresolvedminor2 h 17 min
2026-04-10 08:00 UTCBilling API Data Freshness Delayresolvednone6 h 00 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Temporal with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "temporal"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}