Is Temporal Down?

Partially — Temporal is degraded

Temporal's status page: Degraded · degraded performance of Capacity
FlareWarden checks: Website reachable · 8 of 8 regions · 1395 ms

Right now

The verdict is the worse of these two. How we decide

Temporal's status page

status.temporal.io · read 2 minutes ago · checked every 3 minutes

Degraded

minor monitoring since Oct 15, 5:12 PM UTC

New namespace creation restricted across few GCP regions. Impacted regions are us-central1, us-east4 and europe-west3

We have temporarily restricted new Temporal Cloud namespace creation across few GCP regions due to compute capacity constraints. Impacted regions are us-central1, us-east4 and europe-west3. Existing namespaces continue to operate normally. For details, available alternatives, and how to request an exception, see https://docs.temporal.io/evaluate/cloud/regions#gcp-capacity-restriction

Latest update 1 day ago

Temporal's components, as its status page reports them
Component	Status
Capacity	Degraded Performance
Web UI	Operational
Cloud Ops API	Operational
Metrics	Operational
Namespace Management	Operational
Auth(n)/Auth(z)	Operational
Audit Logging	Operational
Export History	Operational
Billing	Operational
Capacity	Operational

20 locations All operational

Open their status page

FlareWarden checks

temporal.io from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 1395 ms
Checked: 5 minutes ago

By region

Ashburn reachable, 531 ms
Dallas reachable, 2264 ms
Frankfurt reachable, 2134 ms
Johannesburg reachable, 1453 ms
London reachable, 842 ms
Los Angeles reachable, 1412 ms
Newark reachable, 1020 ms
São Paulo reachable, 1508 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	44 ms	1 ms	7 ms	526 ms
Dallas	136 ms	1 ms	53 ms	2226 ms
Frankfurt	18 ms	1 ms	9 ms	1950 ms
Johannesburg	187 ms	0 ms	62 ms	997 ms
London	16 ms	2 ms	22 ms	688 ms
Los Angeles	16 ms	1 ms	25 ms	1343 ms
Newark	5 ms	1 ms	19 ms	1002 ms
São Paulo	13 ms	2 ms	7 ms	1286 ms

We check that temporal.io loads, not every feature behind it. Test it yourself

History

Incidents Temporal reported

Since Oct 22, 3 days · from status.temporal.io

Incidents: 1
Major or critical: 0
Median to resolve: —

New namespace creation restricted across few GCP regions. Impacted regions are us-central1, us-east4 and europe-west3
minor · Oct 15
Ongoing

Temporal website availability

Measured by FlareWarden · temporal.io

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 1372ms

Last 30 days

66-day clean streak

Sep 25 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of temporal.io from multiple regions every 6 hours. Temporal's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 66 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Temporal itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Temporal goes down

We check Temporal every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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