Temporal logo

Is Temporal Down?

Developer ToolsLive status, outages, and incident history

No. Temporal is up right now.

Every monitored Temporal system is operational as of October 13, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment Temporal breaks

Temporal is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Temporal status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Temporal Component Status

The main Temporal systems on this page. All 36 are operational right now.

36operational
Amazon Web Services (AWS) » ap-northeast-1
Operational
Amazon Web Services (AWS) » ap-northeast-2
Operational
Amazon Web Services (AWS) » ap-south-1
Operational

33 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Amazon Web Services (AWS) » ap-south-2, Amazon Web Services (AWS) » ap-southeast-1, Amazon Web Services (AWS) » ap-southeast-2, Amazon Web Services (AWS) » ca-central-1, Amazon Web Services (AWS) » eu-central-1, Amazon Web Services (AWS) » eu-west-1, Amazon Web Services (AWS) » eu-west-2, Amazon Web Services (AWS) » sa-east-1, Amazon Web Services (AWS) » us-east-1, Amazon Web Services (AWS) » us-east-2, Amazon Web Services (AWS) » us-west-2, Global Services » Audit Logging, and 21 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Temporal Outages & Incidents

Incident history from the official Temporal status page, including resolution updates.

Elevated latency and errors in AWS us-east-1Resolved Oct 9, 2026 · 2h 17mResolved

This incident has been resolved. The AWS us-east-1 region is stable and all affected namespaces have been failed back. --- [2026-10-09T23:11:27.956Z] (monitoring) Latency and error rates in AWS us-east-1 have returned to normal levels and affected namespaces have recovered. We are continuing to monitor the region. We will provide another update once failback is complete. --- [2026-10-09T23:16:51.671Z] (investigating) Mitigation remains in progress. We are continuing to fail over affected namespaces with Multi-Region Replication enabled to their replica regions. Some customers may continue to experience elevated latency while this work is underway. We will provide another update within 30 minutes. --- [2026-10-09T22:50:31.376Z] (investigating) We have identified the cause of elevated latency affecting a subset of namespaces in AWS us-east-1. Namespaces with Multi-Region Replication enabled are being failed over to their replica region to restore service. We will provide another update within 30 minutes. --- [2026-10-09T22:38:15.349Z] (investigating) We are investigating elevated latency and increased deadline exceeded errors affecting some namespaces in the AWS us-east-1 region. Workflows may progress more slowly than usual. Our team is actively working to identify the cause. We will provide another update within 30 minutes.

Elevated error rates for cross-region traffic between US AWS regionsResolved Oct 9, 2026 · 0 minResolved

Between 18:41 and 18:54 UTC on October 9, 2026, cross-region traffic to and from AWS us-east-1, us-east-2, and us-west-2 may have seen increased error rates. The issue has been resolved.

Elevated GCP storage latency in us-central1 – precautionary namespace failoverResolved Oct 8, 2026 · 4h 24mResolved

This incident is now resolved. --- [2026-10-09T01:04:22.872Z] (monitoring) Cloud Storage latency in GCP us-central1 has returned to normal levels. We are continuing to monitor the region and will begin failing multi-region namespaces back to us-central1 shortly. --- [2026-10-08T21:53:02.490Z] (investigating) We are monitoring elevated Cloud Storage latency from GCP in us-central1. As a precaution, multi-region namespaces in this region have been failed over to their replica regions. No impact to workflow execution has been observed. We will fail back once GCP confirms recovery.

Temporal Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Temporal incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Jul 15100.00% average · 20 days with incidentsOct 13

Going further back: Temporal uptime by month and every recorded Temporal outage.

Live Temporal Outage Reports

Problems reported by engineers using Temporal. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Temporal problems reported yet.

Something wrong with Temporal on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Temporal

Is Temporal down? Temporal reports live availability for 31 components at status.temporal.io, among them ap-northeast-1, asia-south1 and Web UI. Track Temporal outages, degradations and past incidents here, with uptime history and alerts across your developer tooling stack.

Over the past 30 days, PulsAPI has measured Temporal uptime at 100.00%. Response times, incident history, and SLA tracking for Temporal are available on the PulsAPI dashboard.

Temporal Status FAQ

Is Temporal down right now?

The verdict at the top of this page comes from the latest poll of the official Temporal status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Temporal is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Temporal recovers.

How do I check Temporal uptime history?

PulsAPI tracks Temporal uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Temporal changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Temporal outages?

PulsAPI reads the official Temporal status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Temporal components?

Yes. PulsAPI monitors 36 individual Temporal components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Temporal goes down?

Yes. Create a free account and subscribe to Temporal: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Temporal to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Temporal problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Temporal?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Temporal plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Temporal with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services