Skip to content

Outage tracker / Temporal

Is Temporal down?

Short linkrlup.io/down/temporal

I'm having a problem

Vendor lists an old incident, not shown as liveWhat Temporal reports

Temporal still lists an incident opened on 2026-10-15 with no update since it opened; we do not show it as live.

As of the last successful poll, 2026-11-05 15:29 UTC.

Temporal's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 1 minute ago

Our checks of Temporal pass from all 4 regions we check.

As of Nov 5, 2026, 3:41 PM UTC, RealUptime's checks of Temporal passed in all 4 regions that returned a reading.

Front-door checks

our check readinglive · checked Nov 5, 2026, 3:41 PM UTC
US-East1324 msChecks passing
US-West1411 msChecks passing
Europe972 msChecks passing
Asia-Pacific2723 msChecks passing
their status pagetheir claim, not our reading

Temporal reports: Minor incident (“Partially Degraded Service”)

from Temporal's own status page, checked Nov 5, 2026, 3:33 PM UTC
Temporal's status page reports Partially Degraded Service. Our checks of Temporal currently pass with normal latency. Our checks currently pass from all 4 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show the vendor's report and our check reading side by side. A check can miss problems that users see. Read both before you draw a conclusion.

Temporal's own component breakdown, as they publish it

  • Web UIOperational
  • ap-northeast-1Operational
  • asia-south1Operational
  • Cloud Ops APIOperational
  • ap-northeast-2Operational
  • europe-west3Operational
  • MetricsOperational
  • ap-south-1Operational
  • us-east4Operational
  • Namespace ManagementOperational
  • ap-south-2Operational
  • us-central1Operational
  • Auth(n)/Auth(z)Operational
  • ap-southeast-1Operational
  • us-west1Operational
  • Audit LoggingOperational
  • ap-southeast-2Operational
  • asia-southeast2Operational
  • CapacityDegraded performance
  • Export HistoryOperational
  • ca-central-1Operational
  • BillingOperational
  • eu-central-1Operational
  • eu-west-1Operational
  • eu-west-2Operational
  • sa-east-1Operational
  • us-east-1Operational
  • us-east-2Operational
  • us-west-2Operational
  • CapacityOperational

These are Temporal's components, named and scored by Temporal. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Temporal's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Temporal response time, by region

US-East
1.9sp95 · latest
2.5s1.3s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
US-West
2.0sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
Europe
1.3sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
Asia-Pacific
2.7sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 3.0s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.4s2026-11-05 UTC: p95 2.7s
Oct 7Oct 21Nov 5

Check your own site while you wait on Temporal

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Temporal. It cannot diagnose Temporal's own systems.

Email me when Temporal reports an incident on its status page, and again when it reports it resolved.

Get an email when Temporal reports an incident

Email me when Temporal reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Temporal's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1324msstatus code: 200checked: Nov 5, 2026, 3:41 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Temporal normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1411msstatus code: 200checked: Nov 5, 2026, 3:40 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Temporal normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionTemporal is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionTemporal is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionTemporal is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 972msstatus code: 200checked: Nov 5, 2026, 3:32 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Temporal normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionTemporal is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2723msstatus code: 200checked: Nov 5, 2026, 3:33 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Temporal normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionTemporal is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionTemporal is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Temporal, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Temporal yet, which is not evidence that nothing is wrong.

Recent probe events

Intermittent request failures for some namespaces in GCP us-east4, 45mdeclared on their status page2026-10-31
Elevated connection resets for some GCP namespaces, 1mdeclared on their status page2026-10-19
New namespace creation restricted across few GCP regions. Impacted regions are us-central1, us-east4 and europe-west3declared on their status page2026-10-15
Elevated latency and errors in GCP us-west1, 17mdeclared on their status page2026-10-14
Elevated latency and errors in AWS us-east-1, 2h 17mdeclared on their status page2026-10-09
Elevated error rates for cross-region traffic between US AWS regions, 1mdeclared on their status page2026-10-09
Elevated GCP storage latency in us-central1 – precautionary namespace failover, 4h 25mdeclared on their status page2026-10-08
Increased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UI, 29mdeclared on their status page2026-10-05

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Temporal since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Temporal covering any window you pick, with our check readings and Temporal's own claim at the time, side by side.

Full check history for Temporal: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Temporal uptime by RealUptime's checksLive, from this page's own readings.
[![Temporal uptime by RealUptime's checks](https://realuptime.io/outages/temporal/badge.svg?days=30)](https://realuptime.io/outages/temporal)
<a href="https://realuptime.io/outages/temporal"><img src="https://realuptime.io/outages/temporal/badge.svg?days=30" alt="Temporal uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Temporal down?", https://realuptime.io/outages/temporal. The readings change with every check, so give the date you read them.

What we check

primary
https://temporal.io/
secondary
https://status.temporal.io/

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: temporal.io

RealUptime is not affiliated with Temporal; the name identifies what we checked, and nothing here speaks for Temporal's own team. We send a single web request to Temporal from 4 regions on our own schedule and time the response. We do not see inside Temporal's systems, do not use an account or real transaction, and are not the same signal Temporal's own team has access to. Treat this as one external data point, not a verdict. What we check for Temporal is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. Temporal operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 2508 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.

Related services

1PasswordAWS (Amazon Web Services)AblyAcuity SchedulingAdobe Fonts