Skip to main content
Providers
Is Temporal Cloud down? · Developer tools

Temporal Cloud is up

OperationalNo known problems: Temporal Cloud's status page says operational

99.99% uptime, 90 days · 99.99% over 12 monthsLast incident Checked Official status pageHistory

Reports count in aggregate against normal levels; one alone never makes a claim.

Now

Open incidents

What Temporal Cloud has posted and not resolved.

Temporal Cloud has no open incidents.

Minor

Minor or regional issues (1)

Open issues confined to one country, region, site, carrier route, asset or slice of customers. Temporal Cloud's state, uptime and the Down Index leave them out.

  1. Temporal CloudDegradedMonitoring
    New namespace creation restricted across few GCP regions. Impacted regions are us-central1 and europe-west3

    Temporal Cloud says new namespace creation is temporarily restricted in GCP regions us-central1 and europe-west3 due to compute capacity constraints, while existing namespaces operate normally. The incident is in monitoring.

    monitoring a fix, open 26d 8hCapacityeu, europe-west3, us, us-central1
90 days

Daily history

Worst impact each day, from the provider's own incidents.

  1. 2026-08-14: no incidents
  2. 2026-08-15: no incidents
  3. 2026-08-16: no incidents
  4. 2026-08-17: no incidents
  5. 2026-08-18: no incidents
  6. 2026-08-19: no incidents
  7. 2026-08-20: no incidents
  8. 2026-08-21: no incidents
  9. 2026-08-22: no incidents
  10. 2026-08-23: no incidents
  11. 2026-08-24: no incidents
  12. 2026-08-25: no incidents
  13. 2026-08-26: no incidents
  14. 2026-08-27: no incidents
  15. 2026-08-28: no incidents
  16. 2026-08-29: no incidents
  17. 2026-08-30: no incidents
  18. 2026-08-31: no incidents
  19. 2026-09-01: no incidents
  20. 2026-09-02: 1 incident, worst degraded
  21. 2026-09-03: no incidents
  22. 2026-09-04: no incidents
  23. 2026-09-05: no incidents
  24. 2026-09-06: no incidents
  25. 2026-09-07: no incidents
  26. 2026-09-08: no incidents
  27. 2026-09-09: no incidents
  28. 2026-09-10: no incidents
  29. 2026-09-11: no incidents
  30. 2026-09-12: no incidents
  31. 2026-09-13: no incidents
  32. 2026-09-14: no incidents
  33. 2026-09-15: no incidents
  34. 2026-09-16: no incidents
  35. 2026-09-17: no incidents
  36. 2026-09-18: no incidents
  37. 2026-09-19: no incidents
  38. 2026-09-20: no incidents
  39. 2026-09-21: no incidents
  40. 2026-09-22: no incidents
  41. 2026-09-23: no incidents
  42. 2026-09-24: no incidents
  43. 2026-09-25: no incidents
  44. 2026-09-26: no incidents
  45. 2026-09-27: no incidents
  46. 2026-09-28: no incidents
  47. 2026-09-29: no incidents
  48. 2026-09-30: no incidents
  49. 2026-10-01: no incidents
  50. 2026-10-02: no incidents
  51. 2026-10-03: no incidents
  52. 2026-10-04: no incidents
  53. 2026-10-05: 1 incident, worst major outage
  54. 2026-10-06: no incidents
  55. 2026-10-07: no incidents
  56. 2026-10-08: no incidents
  57. 2026-10-09: no incidents
  58. 2026-10-10: no incidents
  59. 2026-10-11: no incidents
  60. 2026-10-12: no incidents
  61. 2026-10-13: no incidents
  62. 2026-10-14: no incidents
  63. 2026-10-15: no incidents
  64. 2026-10-16: no incidents
  65. 2026-10-17: no incidents
  66. 2026-10-18: no incidents
  67. 2026-10-19: no incidents
  68. 2026-10-20: no incidents
  69. 2026-10-21: no incidents
  70. 2026-10-22: no incidents
  71. 2026-10-23: no incidents
  72. 2026-10-24: no incidents
  73. 2026-10-25: no incidents
  74. 2026-10-26: no incidents
  75. 2026-10-27: no incidents
  76. 2026-10-28: no incidents
  77. 2026-10-29: no incidents
  78. 2026-10-30: no incidents
  79. 2026-10-31: no incidents
  80. 2026-11-01: no incidents
  81. 2026-11-02: no incidents
  82. 2026-11-03: no incidents
  83. 2026-11-04: no incidents
  84. 2026-11-05: no incidents
  85. 2026-11-06: no incidents
  86. 2026-11-07: no incidents
  87. 2026-11-08: no incidents
  88. 2026-11-09: no incidents
  89. 2026-11-10: no incidents
  90. 2026-11-11: no incidents
90 days agoToday

Daily history for the 12 components with the most incident days. Every component's current state is in the Markdown copy.

Reliability

Last 90 days in numbers

From the provider's own posts, including history read from its archive.

Uptime
99.99%12 months
Incidents
22on 2 days
Median duration
45m
Longest
10h 30m
Postmortem rate
0%partial and major outages
Reports

People reporting problems

Hourly counts, last 24 hours.

No reports in the last 24 hours.

Follow Temporal Cloud incidents

Following several providers? Check your stack to get one feed for all of them.

https://down.guide/feed?provider=temporal-cloud
Open feed

In Slack, install the RSS app and run /feed subscribe https://down.guide/feed?provider=temporal-cloud in a channel. In Discord, add a feed bot such as MonitoRSS and give it this URL. Or paste it into Feedly or any RSS reader.

https://down.guide/feed?provider=temporal-cloud&format=atom
Open feed

The same entries as Atom, for readers that prefer it.

https://down.guide/feed?provider=temporal-cloud&format=json
Open feed

The same entries as JSON Feed 1.1, each with the full incident under _down_guide, for scripts.

https://down.guide/api/v1/incidents?provider=temporal-cloud
Open feed

Pages of 30 incidents, newest first. Pass the response's next_cursor as cursor for the next page.

History

Recent incidents

The last 90 days.

All history
  1. Some customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures

    Temporal Cloud says some customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures. The provider identified the issue and applied a mitigation, and it is now monitoring the results.

    lasted 3h 44mus-west-2us, us-west-2
  2. Intermittent request failures for some namespaces in GCP us-east4
    lasted 45mus-east4us, us-east4
  3. Temporal CloudOperational
    Elevated connection resets for some GCP namespaces
    lasted 0mus-east4, us-central1us, us-central1, us-east4
  4. Temporal CloudOperational
    Elevated latency and errors in GCP us-west1
    lasted 17mus-west1us, us-west1
  5. Elevated latency and errors in AWS us-east-1
    lasted 2h 17mus-east-1us, us-east-1
  6. Temporal CloudOperational
    Elevated error rates for cross-region traffic between US AWS regions
    lasted 0mus, us-east-1, us-east-2, us-west-2
  7. Temporal CloudOperational
    Elevated GCP storage latency in us-central1 – precautionary namespace failover
    lasted 4h 25mus, us-central1
  8. Temporal CloudMajor outage
    Increased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UI
    lasted 29m
  9. UI Disruptions in GCP us-central1
    lasted 40mWeb UIus, us-central1
  10. Temporal CloudOperational
    Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors
    lasted 0mus, us-east4
  11. Increased latency in region us-west-2
    lasted 53mus-west-2us, us-west-2
  12. Some customers may have incorrectly received a "credit expiry notification"
    lasted 6h 29mBilling
  13. Temporal CloudOperational
    Some customers in APSE region may experience incomplete responses from Temporal Cloud metrics (OpenMetrics)
    lasted 4h 19mMetrics
  14. Temporal CloudPartial outage
    Customers in us-central1 and asia-southeast2 may experience a delay in workflow progress
    lasted 10h 30mus-central1, asia-southeast2apac, asia-southeast2, us, us-central1
  15. Elevated Errors in us-west-2 Region
    lasted 8h 16mus-west-2us, us-west-2

Temporal Cloud status: questions

Is Temporal Cloud down right now?

No known problems: Temporal Cloud's status page says operational (checked 2026-11-11 01:29 UTC from Temporal Cloud's official status page).

What is Temporal Cloud's uptime?

99.99% over the last 90 days and 99.99% over 12 months, from the incidents Temporal Cloud posted on its own status page. A major outage counts in full and a partial outage as 30% of its time, per component.

When was Temporal Cloud's last outage?

Some customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures, starting 2026-11-06 13:40 UTC and lasting 3h 44m: https://down.guide/DWN-9912219cfd

How do I get alerts when Temporal Cloud goes down?

Subscribe to https://down.guide/feed?provider=temporal-cloud (RSS; add format=atom or format=json). In Slack, install the RSS app and run /feed subscribe with that URL; in Discord, give it to a feed bot such as MonitoRSS. No account needed.

Where does down.guide get Temporal Cloud's status?

From Temporal Cloud's official status page, https://status.temporal.io, read every minute. Temporal Cloud's words are quoted verbatim and linked.