# Okta: Group Push Delays on OK3

- Provider: [Okta](https://outages.live/okta.md)
- Type: Incident
- State: Resolved
- Worst impact: Partial outage
- Started: 2026-10-21 18:49 UTC
- Resolved: 2026-10-28 22:34 UTC (lasted 7 days)
- Components: Core Platform
- Official update: https://status.okta.com/#incident/a9CWR0000002NgU2AU

## Updates from Okta

### update, 2026-10-28 22:26 UTC

We sincerely apologize for any impact this incident has caused to you, your business, and your customers. At Okta, trust and transparency are our top priorities. Outlined below are the facts regarding this incident. We are committed to implementing improvements to the service to prevent future occurrences of this incident. Detection and Impact: On October 21st, 2026, at 11:48 AM PT, Okta customer reports alerted our engineering team of group push membership processing delays for US Cell OK3. During this time, customers may have experienced delays in Group Push operations. As a result, access for new membership changes to downstream provisioned applications was delayed. Root Cause Summary: The root cause of the processing delays was a legacy concurrency limit that restricted the overall throughput of background application reconciliation operations. During this time, surges in background asynchronous work exhausted the cell's maximum allowed concurrent reconciliation tasks. This limit w

### update, 2026-10-21 21:32 UTC

The issue causing Group Push failures has been resolved. Additional root cause information will be available within five business days.

### update, 2026-10-21 19:59 UTC

We are seeing recovery across the impacted Group Push imports. Mitigation efforts have significantly reduced the processing backlog. We are actively monitoring system stability and performance metrics. Next update in 30 minutes.

### update, 2026-10-21 19:48 UTC

A subset of our customers are currently experiencing failures or severe delays in Group Push imports. Background jobs are either stuck in the "pushing" state or taking longer than usual to complete. Existing user access and active sessions remain unaffected. To mitigate the impact, we are continuing to scale up processing capacity. Next update in 30 minutes.