Is Temporal down?

Last checked 8m ago
Current status
Temporal is up

No incidents right now.

Official status page: https://status.temporal.io · Polled every 5 minutes · 28 components tracked

Temporal is operational right now. Last checked 8m ago; the most recent incident resolved 4d ago.

Real-time Temporal status, recent outages, and incident history — pulled directly from Temporal's official status page at https://status.temporal.io every 5 minutes. Pingoru tracks 28 Temporal services and has captured 33 incidents in the last 90 days (98.83% uptime). Get email, Slack, Discord, or webhook alerts the moment Temporal reports a new incident — free for 5 monitors, no credit card.

Users who monitor Temporal also follow these Development services: Bitbucket OpenAI Datadog US1 Sentry NPM Travis CI Postman Pusher Pendo SonarCloud View all 6,000+ providers
Temporal uptime 98.83% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 4h 18m
    Started Sep 11, 2026, 10:10 AM UTC · Resolved Sep 11, 2026, 02:29 PM UTC
    Metrics
    Timeline · 3 updates
    • investigating · Sep 11, 2026, 11:24 AM UTC

      We are currently investigating a degradation in OpenMetrics endpoint causing incomplete responses for customers in APSE region

    • monitoring · Sep 11, 2026, 01:31 PM UTC

      OpenMetrics incomplete responses have recovered and remain stable. We continue to monitor the situation.

    • resolved · Sep 11, 2026, 02:29 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 10h 29m
    Started Sep 10, 2026, 08:51 PM UTC · Resolved Sep 11, 2026, 07:21 AM UTC
    us-central1asia-southeast2
    Timeline · 7 updates
    • identified · Sep 10, 2026, 09:51 PM UTC

      Some customers with namespaces in the us-central1 and asia-southeast2 regions may experience errors and blocked progress on their workflows. We are currently rolling out a fix.

    • monitoring · Sep 10, 2026, 10:27 PM UTC

      The issue has been mitigated (as of 21:55 UTC) and we are actively monitoring the previously impacted environments.

    • monitoring · Sep 10, 2026, 10:29 PM UTC

      We are continuing to monitor for any further issues.

    • monitoring · Sep 10, 2026, 10:59 PM UTC

      While a small number of customer environments may still see some issues, mitigation has been in place and we continue to actively monitor.

    • monitoring · Sep 10, 2026, 11:29 PM UTC

      We are continuing to monitor for any further issues.

    • monitoring · Sep 10, 2026, 11:30 PM UTC

      We are continuing to monitor for any further issues.

    • resolved · Sep 11, 2026, 07:21 AM UTC

      The environment has been validated and all residual issues have been cleared. This incident is now resolved.

    Latest: The environment has been validated and all residual issues have been cleared. This incident is now resolved.

  3. Resolved 8h 16m
    Started Sep 03, 2026, 09:12 PM UTC · Resolved Sep 04, 2026, 05:28 AM UTC
    us-west-2
    Timeline · 4 updates
    • investigating · Sep 03, 2026, 11:10 PM UTC

      We are investigating connectivity errors affecting some customers with namespaces in the us-west-2 region relating to an AWS outage in this region. Our team is actively assessing impact and working on mitigation. Affected MRN namespaces have been failed over. We will provide updates as more information becomes available. https://health.aws.amazon.com/health/status

    • monitoring · Sep 03, 2026, 11:25 PM UTC

      We are starting to see recovery as of 23:01 UTC.

    • monitoring · Sep 04, 2026, 02:13 AM UTC

      As of 9/4 00:07 UTC, AWS has confirmed the incident impacting us-west-2 is resolved. After a further period of monitoring, we have confirmed service is stable and have begun failing back the affected MRN namespaces.

    • resolved · Sep 04, 2026, 05:28 AM UTC

      As of 9/4 05:03 UTC, all affected MRN namespaces have been failed back to us-west-2. No further issues have been observed and this incident is resolved.

    Latest: As of 9/4 05:03 UTC, all affected MRN namespaces have been failed back to us-west-2. No further issues have been observed and this incident is resolved.

  4. Resolved 22m
    Started Sep 02, 2026, 03:26 PM UTC · Resolved Sep 02, 2026, 03:49 PM UTC
    Namespace Management
    Timeline · 2 updates
    • identified · Sep 02, 2026, 03:26 PM UTC

      We have identified an issue where some customers may receive failures when creating or updating namespaces. We are currently rolling back the affected service. Temporal Cloud will ensure failures are manually retried.

    • resolved · Sep 02, 2026, 03:49 PM UTC

      The rollback of the affected service has completed. Namespace configuration changes will resume as expected.

    Latest: The rollback of the affected service has completed. Namespace configuration changes will resume as expected.

  5. Resolved 5h 55m
    Started Sep 01, 2026, 03:47 PM UTC · Resolved Sep 01, 2026, 09:43 PM UTC
    us-central1
    Timeline · 3 updates
    • investigating · Sep 01, 2026, 03:47 PM UTC

      We are currently investigating elevated error rates in GCP us-central1, and have proactively failed over MRN namespaces in this region as a precaution.

    • identified · Sep 01, 2026, 04:07 PM UTC

      We have identified this as an upstream network issue with GCP: https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev

    • resolved · Sep 01, 2026, 09:43 PM UTC

      GCP is reporting that mitigations are in place, and that all services in this region are operational. MRN namespaces have been failed back to their primary regions.

    Latest: GCP is reporting that mitigations are in place, and that all services in this region are operational. MRN namespaces have been failed back to their primary regions.

See the full Temporal outage history

27 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Temporal outage history →

Or sign up free to get alerts when Temporal breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 32 incidents View full outage history →