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 Okta is down?

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

How many people have reported Okta issues today?

As of Oct 8, 2026 17:20 UTC, 0 users had reported issues with Okta in the previous 24 hours.

How can I report a Okta 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.

Productivity

Is Okta down right now?

UnknownOfficial status last polled Sep 7, 2026 18:41 UTCwww.okta.com Official status page

Okta identity and single sign-on

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

Is Okta down right now?

Unknown. Okta does not have a conclusive current status. A single-runtime HTTP reachability check succeeded; no fresh official status confirms whole-service health. No current vendor status signal: vendor status was last polled on 2026-09-07, more than 7 days ago. The most recent attempt on 2026-10-08 could not be acquired.

Status as of Oct 8, 2026 17:20 UTC

Unknown

Okta: status unknown

As of Oct 8, 2026 17:20 UTC

No product check is currently qualified to corroborate an incident for this service. Overall service status has not been established.

Reports 24h

Last incident

May 5, 2026 06:03 UTC

Trend

0/15m

Monitoring

Coverage gap

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 Okta.

Incident days

No recorded incident

0 min

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 Okta. 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

0 incidents

Busiest day

0 min

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

Okta outage on May 5 — 19-minute disruption

May 5, 05:43 AM → May 5, 06:03 AM · 19 minutes · medium

An incident affecting Okta services was detected on May 5, 2026, following user reports. The disruption lasted approximately 19 minutes and was fully resolved by 06:03 UTC.

Duration

19 minutes

tracked by PulseWatch

Impact

The incident was initially detected through user reports. During the peak of the disruption, four user reports were received within a 15-minute window. No specific issue types or geographic regions were predominantly identified among these reports. The impact was observed across Okta services, leading to a temporary disruption for affected users.

Incident timeline

May 5, 05:43 AM
PulseWatch detected elevated report volume (medium severity)
May 5, 05:45 AM
Peak of 0 reports in 15 minutes (baseline 1.3)
May 5, 06:03 AM
Report volume returned to baseline — incident resolved

Official updates

May 5, 05:43 AM
Okta status page acknowledged the incident.
View official source

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

Not calculated: Okta is unknown, so there is no incident history to measure and no uptime figure is shown.

Other productivity 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.