Where does this status come from?

From Temporal Cloud's own status page API at https://status.temporal.io. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Temporal Cloud's words.

How can my agent or app check Temporal Cloud status?

Fetch https://upbutler.com/status/temporal/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"temporal"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Temporal Cloud's?

Add "temporal" to the dependencies of your UpButler workspace. When one of your monitors fails while Temporal Cloud has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Temporal Cloud down?

Right now

No. Temporal Cloud is operational.

No incidents reported.

Read from status.temporal.io 4 min ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/temporal/status.agent.json

MCP: upstream_status {"service":"temporal"}

Managed Temporal namespaces per region.

What Temporal Cloud reports

Operational

Taken as is from Temporal Cloud's own status page API. Incident titles and component names below are theirs.

Open status.temporal.io

UpButler's independent probe

There is no keyless endpoint of Temporal Cloud that says anything useful, so UpButler does not probe it. To check your own Temporal Cloud account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Temporal Cloud components

30 operational

Amazon Web Services (AWS)

ap-northeast-1Operational
ap-northeast-2Operational
ap-south-1Operational
ap-south-2Operational
ap-southeast-1Operational
ap-southeast-2Operational
ca-central-1Operational
eu-central-1Operational
eu-west-1Operational
eu-west-2Operational
sa-east-1Operational
us-east-1Operational
us-east-2Operational
us-west-2Operational

Google Cloud Platform (GCP)

asia-south1Operational
europe-west3Operational
us-east4Operational
us-central1Operational
us-west1Operational
asia-southeast2Operational

Global Services

Web UIOperational
Cloud Ops APIOperational
MetricsOperational
Namespace ManagementOperational
Auth(n)/Auth(z)Operational
Audit LoggingOperational
Export HistoryOperational
BillingOperational
GCP CapacityOperational
AWS CapacityOperational

Temporal Cloud incidents, last 90 days

7 finished incidents seen since UpButler started tracking on 2026-10-10, 1 of them rated major or critical by Temporal Cloud. A typical one lasted 40 min; the longest 4 h 25 min.

Started (UTC)	Incident	Impact	Lasted
2026-10-09 22:33	Elevated latency and errors in AWS us-east-1	minor	2 h 17 min
2026-10-09 22:25	Elevated error rates for cross-region traffic between US AWS regions	none	under a minute
2026-10-08 21:53	Elevated GCP storage latency in us-central1 – precautionary namespace failover	none	4 h 25 min
2026-10-05 20:23	Increased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UI	critical	29 min
2026-10-01 21:07	UI Disruptions in GCP us-central1	minor	40 min
2026-10-01 14:52	Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors	none	under a minute
2026-09-27 01:01	Increased latency in region us-west-2	minor	53 min

Tell your outage from Temporal Cloud's

Declare that your project depends on Temporal Cloud. When one of your monitors fails while Temporal Cloud has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - temporal

Ask before you retry

curl -s https://upbutler.com/status/temporal/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "temporal",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Temporal Cloud down right now?: No. As of 2026-10-10 05:07 UTC, Temporal Cloud is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From Temporal Cloud's own status page API at https://status.temporal.io. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Temporal Cloud's words.
How can my agent or app check Temporal Cloud status?: Fetch https://upbutler.com/status/temporal/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"temporal"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Temporal Cloud's?: Add "temporal" to the dependencies of your UpButler workspace. When one of your monitors fails while Temporal Cloud has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in code, packages and workflows

UpButler is not affiliated with Temporal Cloud. Status and incident text belong to Temporal Cloud and are read from their public status source; the probe result is UpButler's own measurement.