Live / Optum / Incident
Optum: System Incident - Medical Network - Batch - Production
Optum · optum.comMajor incidentResolved2026-10-14 17:46 UTC
Public — what happened
Summary
Optum reported a major incident affecting its Medical Network batch production systems, saying an on-and-off problem was disrupting its Real-Time Claim Edits (RTCE) service. According to Optum, the trouble began on 10/14/26 at 10:15 am, and it posted its first notice at 17:23 UTC that day while its teams looked into the problem. Optum did not name a cause, and the incident was marked resolved at 17:46 the same day.
Affected
Batch
Timeline
- Started — 2026-10-14 17:23 UTC
- Investigating — 2026-10-14 17:23 UTC
- Resolved — 2026-10-14 17:46 UTC · 23 min 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 43, 2026, our weekly internet health report.