Is Temporal down?

Last checked 2m ago
Current status
Temporal is up

No new incidents. 1 long-running issue listed below.

Temporal is operational right now, apart from 1 long-running issue open since October 15, 2026. Last checked 2m ago.

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

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

Recent outages & incidents

Past 90 days
  1. Resolved 44m
    Started Oct 31, 2026, 01:31 PM UTC · Resolved Oct 31, 2026, 02:16 PM UTC
    us-east4us-west1
    Timeline · 4 updates
    • investigating · Oct 31, 2026, 01:31 PM UTC

      We are investigating intermittent request failures affecting a subset of namespaces in GCP. Affected users may see elevated latency and error rates on API calls, including worker polling (workflow, activity, and Nexus tasks), which can result in reduced task throughput.

    • monitoring · Oct 31, 2026, 01:48 PM UTC

      A fix has been implemented and we are monitoring the results.

    • monitoring · Oct 31, 2026, 01:54 PM UTC

      We are continuing to monitor for any further issues.

    • resolved · Oct 31, 2026, 02:16 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved –
    Started Oct 19, 2026, 10:13 PM UTC · Resolved Oct 19, 2026, 10:13 PM UTC
    us-east4us-central1
    Timeline · 1 update
    • resolved · Oct 19, 2026, 10:13 PM UTC

      Between October 6 and October 15, 2026, some clients connected to GCP-hosted namespaces may have seen intermittent TCP connection resets. SDK retries limited the impact and there is no ongoing impact.

    Latest: Between October 6 and October 15, 2026, some clients connected to GCP-hosted namespaces may have seen intermittent TCP connection resets. SDK retries limited the impact and there i…

  3. Resolved 16m
    Started Oct 14, 2026, 01:20 PM UTC · Resolved Oct 14, 2026, 01:36 PM UTC
    us-west1
    Timeline · 2 updates
    • monitoring · Oct 14, 2026, 01:20 PM UTC

      Between 12:21:15 UTC and 12:22:00 UTC, some users may have experienced elevated latency and error rates in GCP us-west1. The issue has been identified and mitigated. We are continuing to monitor the region. MRN namespaces have been failed over and will be failed back once monitoring confirms the region is stable.

    • resolved · Oct 14, 2026, 01:36 PM UTC

      This incident has been resolved. The GCP us-west1 region is stable and all affected namespaces have been failed back.

    Latest: This incident has been resolved. The GCP us-west1 region is stable and all affected namespaces have been failed back.

  4. Resolved 2h 17m
    Started Oct 09, 2026, 10:33 PM UTC · Resolved Oct 10, 2026, 12:51 AM UTC
    us-east-1
    Timeline · 5 updates
    • investigating · Oct 09, 2026, 10:33 PM UTC

      We are investigating elevated latency and increased ResourceExhausted 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.

    • investigating · Oct 09, 2026, 10:38 PM UTC

      We are continuing to investigate this issue.

    • investigating · Oct 09, 2026, 10:50 PM UTC

      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.

    • monitoring · Oct 09, 2026, 11:11 PM UTC

      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.

    • resolved · Oct 10, 2026, 12:51 AM UTC

      This incident has been resolved. The AWS us-east-1 region is stable and all affected namespaces have been failed back.

    Latest: This incident has been resolved. The AWS us-east-1 region is stable and all affected namespaces have been failed back.

  5. Resolved 13m
    Started Oct 09, 2026, 06:41 PM UTC · Resolved Oct 09, 2026, 06:54 PM UTC
    Timeline · 1 update
    • resolved · Oct 09, 2026, 10:25 PM UTC

      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.

    Latest: 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 res…

See the full Temporal outage history

17 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

Incident record

Since April 2026 · Statuspage by Atlassian · 30 components checked every 5 minutes
98incidents recorded
94last 12 months
22last 90 days
12 hourstypical duration, 12 months

The longest incident in the last year, Some customers may be experiencing stuck workflows or activities on June 3, 2026, ran for 14 days. 1 maintenance window announced in the same period.

Most affected components, last 12 months

  • us-east-113
  • us-west-212
  • us-east49
  • Metrics6
  • eu-west-15

Latest incidents

Outage history

Past 90 days · 22 incidents View full outage history →