No impact incident
okta: This is an example incident
Oct 14, 2026, 12:39 UTC
started
12:55 UTC
resolved October 13, 2026
—
duration
Current status of okta: Operational — live okta status
Timeline
- Oct 13, 2026, 12:45 UTCmonitoringLet your users know once a fix is in place, and keep communication clear and precise.
- Oct 13, 2026, 12:51 UTCidentifiedAs you continue to work through the incident, update your customers frequently.
- Oct 13, 2026, 12:55 UTCresolvedEmpathize with those affected and let them know everything is operating as normal.
- Oct 13, 2026, 13:21 UTCinvestigatingWhen your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.
Updates as published by okta (original).
Other services with incidents at the same time
- Sangoma 13:38 UTC · Digium Cloud Portal Issue - Digium Cloud Services
- Mercado Pago 13:28 UTC · ALL SITES - Delay in IPN Payments notifications
- Learnworlds 13:28 UTC · Issues with schools located in EU
- WatchGuard Technologies 13:24 UTC · 2026-10-14 - APAC - DNSWatch V1 issues
- YNAB 13:19 UTC · Unable to process Google Play Store subscriptions
- Batch 13:11 UTC · Delays in file-based audience imports
- Zenoti 13:04 UTC · Zenoti Application Degraded Performance - ASIA22
- Liquid Web - Services 13:04 UTC · Premium business email Webmail Access Issues
- Heap 13:03 UTC · User property data delayed in Heap connect syncs (US customers only)
- Brandwatch 13:00 UTC · HUB app notifications affected
- Grafana Cloud 12:57 UTC · Authentication errors in prod-us-west-0
- Ledger 12:52 UTC · Dydx (DYDX) Mainnet Degraded Service
- Sanity 12:48 UTC · Intermittent increased API latency for some customers
- Code42 Software 12:44 UTC · Delay in processing events
- Qualtrics 12:30 UTC · Copied report generation issues in all regions