PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Temporal Cloud is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Temporal Cloud. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Temporal Cloud issues today?

As of Sep 28, 2026 10:33 UTC, 0 users had reported issues with Temporal Cloud in the previous 24 hours.

How can I report a Temporal Cloud outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Other

Is Temporal Cloud down right now?

NormalOfficial status last polled Sep 28, 2026 10:13 UTCtemporal.io/cloud Official status page

Are you on the Temporal Cloud team and see something inaccurate? Report it to us. We respond within one business day.

Is Temporal Cloud down right now?

No. Temporal Cloud has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Sep 28, 2026 10:33 UTC

Normal

Temporal Cloud is operating normally

As of Sep 28, 2026 10:33 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

Last incident

Sep 27, 2026 02:36 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Temporal Cloud.

Incident days

No recorded incident

19h 6m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Temporal Cloud. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

1 incident

Busiest day

19h 6m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Temporal Cloud outage on September 27 — 1h 30m disruption

Sep 27, 01:06 AM → Sep 27, 02:36 AM · 1h 30m · medium

An incident affecting Temporal Cloud was detected by automated monitoring systems, including the vendor's status page. The issue began at 2026-09-27T01:06:09.906Z and was resolved at 2026-09-27T02:36:16.265Z.

Peak reports

in 15 min

Total reports

during outage

Duration

1h 30m

until recovery

Impact

During the 1 hour and 30 minute incident, Temporal Cloud experienced a medium-severity disruption. This incident was identified through automated monitoring and the vendor's status page. No user-reported data, including specific affected regions or issue types, was collected for this event.

Outage timeline

Sep 27, 01:06 AM
PulseWatch detected the incident from automated vendor and probe signals (medium severity)
Sep 27, 01:06 AM
Status updated: possible issue
Sep 27, 02:36 AM
Signals cleared — incident resolved

Official updates

Sep 27, 01:06 AM
Temporal Cloud status page acknowledged the incident.
View official source

Reliability

Detected by PulseWatch

30-day uptime

97.3%

90-day uptime

99.0%

Calculated from Temporal Cloud's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other other services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedMedium

Temporal Cloud: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/27/2026, 1:06:09 AM · 1h 30m

01:06 AM02:36 AM

Detection9/27/2026, 1:06:09 AM · 1d ago

Detected — medium severity

ResolvedMedium

9/18/2026, 3:55:59 PM · 8h 10m

03:55 PM12:06 AM

Detection9/18/2026, 3:55:59 PM · 9d ago

Detected — medium severity

ResolvedMedium