Is Temporal Down?

No — Temporal is up

Reachable from all 8 checked regions

Average response time: 1352ms

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://status.temporal.io

Temporal uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

1344ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 52 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

52-day clean streak

Sep 10 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

1388ms

DNS 53ms TCP 2ms TLS 18ms TTFB 1205ms

arn

1376ms

DNS 135ms TCP 1ms TLS 11ms TTFB 1155ms

cdg

960ms

DNS 55ms TCP 9ms TLS 15ms TTFB 795ms

dfw

1203ms

DNS 76ms TCP 0ms TLS 54ms TTFB 1169ms

sin

2453ms

DNS 1002ms TCP 1ms TLS 6ms TTFB 2016ms

sjc

1334ms

DNS 29ms TCP 1ms TLS 8ms TTFB 1212ms

syd

1252ms

DNS 51ms TCP 1ms TLS 6ms TTFB 809ms

yyz

857ms

DNS 204ms TCP 12ms TLS 32ms TTFB 805ms

What Temporal does

Temporal runs durable workflows: application code that survives process crashes, restarts and long waits because Temporal records every step and can replay it. Teams use it for payment flows, order fulfilment and multi-step AI pipelines where losing state halfway is unacceptable. Temporal Cloud is the hosted version, running customer namespaces in named AWS and GCP regions.

What an outage looks like

Workflow starts and signals are rejected, and clients report failures reaching the frontend for a namespace. Running workflows appear stuck: activities stop being dispatched to workers, and timers fire late or not at all. The Web UI fails to load workflow histories. Because Temporal persists state, work usually pauses rather than disappearing, and resumes once the namespace recovers.

What to do about it

status.temporal.io reports per region, listing AWS regions such as us-east-1, us-west-2 and eu-west-1 alongside GCP regions, plus Web UI, Cloud Ops API, Metrics, Namespace Management, Auth and Billing separately. Check the region your namespace lives in rather than the overall banner. Leave workers running: they reconnect and resume dispatch when the service returns, so restarting them rarely helps.

Is it down for everyone, or just you?

If this page says Temporal is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Confluent

AWS

Datadog

CockroachDB

Temporal outage FAQ

Will my running workflows be lost?

Usually not. Temporal persists workflow state and replays event history, so a service interruption typically pauses execution rather than discarding it. Activities that were mid-flight are retried according to their retry policy once the namespace is reachable again. Workflows with tight timeouts or short activity deadlines are the exception, since those can expire while the service is unavailable.

Is it my workers or Temporal Cloud?

Check whether your workers can reach the frontend at all. If polling calls fail for every worker across different machines and networks, the problem is upstream. If one worker is quiet while others dispatch normally, look at that host. The status page lists regions individually, so confirm the region hosting your namespace rather than reading the overall indicator.

Does an incident in one region affect my namespace?

Only if your namespace lives there. Temporal Cloud namespaces are pinned to a specific AWS or GCP region, and the status page reports each region on its own line. An incident in ap-southeast-2 does not touch a namespace in us-east-1. Global components such as Web UI, Billing and Namespace Management are listed separately and can fail independently of any region.

The Web UI is broken but my workflows seem fine. Is that possible?

Yes. Web UI is its own component, separate from the regional services that execute workflows. The UI can fail to render histories while workers continue polling and completing tasks normally. Verify with your own metrics or the CLI before assuming execution has stopped, since a console problem is not the same as a data plane problem.

How we measure this

We request Temporal's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Temporal publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Temporal goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required