Live / Optum / Incident
Optum: System Incident - Assurance Reimbursement Management - Production
Optum · optum.comCritical outageResolved2026-10-27 18:12 UTC
Public — what happened
Summary
Optum reported a critical incident affecting its Assurance Reimbursement Management product in production, starting at 15:38 UTC on 2026-10-27. The company said Medicare Direct Entry was performing inconsistently for both EDSNet and CDSNet, which could cause jobs to fail, wait in a queue, or run slowly, with some failures showing a message about not connecting to a host. At 16:44 UTC Optum said its internal teams were still researching the issue, and no cause was given in the updates provided. The incident is marked resolved as of 18:12 UTC.
Affected
Assurance Reimbursement Management
Timeline
- Started — 2026-10-27 15:38 UTC
- Investigating — 2026-10-27 15:38 UTC (2 updates)
- Resolved — 2026-10-27 18:12 UTC · 2h 34m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Optum against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Optum: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Optum report →
More from Optum
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.