- Detected by Pingoru
- Jun 17, 2026, 03:56 PM UTC
- Resolved
- Jun 17, 2026, 04:12 PM UTC
- Duration
- 15m
Affected: Pharmacy Data Solutions
Timeline · 2 updates
-
investigating Jun 17, 2026, 03:56 PM UTC
Optum Insight has identified an issue impacting erroneous rejections for some transactions associated with specific pharma VOD programs. We are investigating the issue and will provide an update once available. # INC50589485
-
resolved Jun 17, 2026, 04:12 PM UTC
Optum Insight has resolved the issue impacting erroneous rejections for some transactions associated with specific pharma VOD programs and will continue monitoring. If you experience and such issues, please reach out to the Pharmacy Support Help Desk at 866-379-6389. # INC50589485
Read the full incident report →
- Detected by Pingoru
- Jun 16, 2026, 04:17 PM UTC
- Resolved
- Jun 16, 2026, 04:35 PM UTC
- Duration
- 17m
Affected: Pharmacy Network Solutions
Timeline · 2 updates
-
investigating Jun 16, 2026, 04:17 PM UTC
We have identified intermittent timeouts occurring with our Cardfinder service and are working to resolve the issue. We will send an update once there is any new information or a resolution. INC #INC50569042
-
resolved Jun 16, 2026, 04:35 PM UTC
The issue causing intermittent timeouts with our Cardfinder service have been resolved and the service is no longer experiencing any timeouts. Thank you for your patience while we worked through this issue. INC #INC50569042
Read the full incident report →
- Detected by Pingoru
- May 12, 2026, 07:38 PM UTC
- Resolved
- May 12, 2026, 08:11 PM UTC
- Duration
- 32m
Affected: Pharmacy Network Solutions
Timeline · 2 updates
-
investigating May 12, 2026, 07:38 PM UTC
RXNS pharmacy transactions for WA Department of Labor VPN Connection went down 7:20 AM CT. As a result, 100% of transaction traffic to the affected VPN was unavailable during the incident window. Investigation and Troubleshooting Activities: The PE Team and Product Operations Team are actively troubleshooting the issue. The Network Team is currently investigating VPN connectivity. The Application Operations Team is coordinating with the processor to obtain an update on the current connection status. INC#INC49975636
-
resolved May 12, 2026, 08:11 PM UTC
RXNS pharmacy transactions for the WA Department of Labor VPN connection went down at 07:20 AM CT. As a result, 100% of transaction traffic to the affected VPN was unavailable during the incident window. The VPN connection was restored without intervention from the Optum side at approximately 02:58 PM CT, after which transaction traffic began flowing normally. INC#INC49975636
Read the full incident report →
- Detected by Pingoru
- May 07, 2026, 07:26 PM UTC
- Resolved
- May 07, 2026, 11:58 PM UTC
- Duration
- 4h 31m
Affected: Pharmacy Network Solutions
Timeline · 4 updates
-
investigating May 07, 2026, 07:26 PM UTC
NCPDP pharmacy benefit claims destined to AL and CT Medicaid VPN connections for patient's with AL and CT Medicaid coverage are not making it to either payer. 100% of the traffic destined to these payers is currently down. Optum Insight is actively working on this issue. INC # INC49898339
-
identified May 07, 2026, 08:31 PM UTC
Our technical teams are continuing to work to resolve this issue, and we will provide updates as more becomes available. INC # INC49898339
-
identified May 07, 2026, 09:54 PM UTC
Customer network team and Optum technical teams are continuing to work to resolve this issue, and we will provide updates as more becomes available.
-
resolved May 07, 2026, 11:58 PM UTC
Optum Insight worked with Gainwell to resolve connectivity to AL and CT Medicaid. The connection was restored at 6:27pm CST.
Read the full incident report →
- Detected by Pingoru
- May 04, 2026, 06:48 PM UTC
- Resolved
- May 04, 2026, 07:22 PM UTC
- Duration
- 34m
Affected: Pharmacy Software Solutions
Timeline · 2 updates
-
investigating May 04, 2026, 06:48 PM UTC
Optum Insight has identified an issue causing intermittent impact to Script Routing Transactions. This issue is currently being investigated and an update will be provided as soon as possible. #INC49825179
-
resolved May 04, 2026, 07:22 PM UTC
Optum Insight has resolved the issue causing intermittent impact to Script Routing transactions. Impacted script-routing transactions should be resubmitted as necessary. #INC49825179
Read the full incident report →
- Detected by Pingoru
- May 04, 2026, 04:27 PM UTC
- Resolved
- May 04, 2026, 06:20 PM UTC
- Duration
- 1h 53m
Affected: Pharmacy Software Solutions
Timeline · 4 updates
-
investigating May 04, 2026, 04:27 PM UTC
We are aware of an issue with a certificate expiration causing major impact to your business. Our teams are currently engaged and will provide an update as it becomes available. #INC49821636
-
investigating May 04, 2026, 05:15 PM UTC
A workaround has been found for the issue, and is being communicated via your support team. #INC49821636
-
monitoring May 04, 2026, 05:21 PM UTC
The workaround has proved successful when applied. We are continuing to monitor until completion. #INC49821636
-
resolved May 04, 2026, 06:20 PM UTC
The workaround given has resolved the issue where it has been applied. The rollout to stores is continuing and expected to be complete within the next hour. #INC49821636
Read the full incident report →
- Detected by Pingoru
- Apr 30, 2026, 05:48 PM UTC
- Resolved
- Apr 30, 2026, 05:48 PM UTC
- Duration
- —
Affected: Pharmacy Network Solutions
Timeline · 1 update
-
resolved Apr 30, 2026, 05:48 PM UTC
As previously communicated Optum Insight identified inconsistent payment activity and claim reopening outcomes across the DME MACs post-implementation of their new policy of requiring a KX modifier being submitted on inhalation drug claims. As a result, we placed all inhalation drug and corresponding dispensing fee claims on hold temporarily to prevent the occurrence of further denials. Optum Insight is pleased to share that we have completed system enhancements, including necessary coding updates resulting from collaborative testing. Consequently, all previously held claims have been released with the appropriate modifier codes as of Monday, April 27, 2026. We appreciate your continued partnership and remain available for any questions through our customer support team at 866-379-6389.
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 02:39 PM UTC
- Resolved
- Apr 22, 2026, 11:36 PM UTC
- Duration
- 8h 57m
Affected: Pharmacy Network Solutions
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 02:27 PM UTC
- Resolved
- Apr 20, 2026, 04:42 PM UTC
- Duration
- 2h 15m
Affected: Contract Manager
Timeline · 4 updates
-
investigating Apr 20, 2026, 02:27 PM UTC
CM is currently experiencing an unexpected connectivity issue today, Monday, April 20, 2026. As a result, users may be unable to access the CM application. Optum is currently working to resolve this as soon as possible and will continue to keep you updated on the progress made to correct this issue. We apologize for any inconvenience this may cause. #INC49575022
-
investigating Apr 20, 2026, 03:31 PM UTC
We continue to work on resolving the outage associated with the Contract Manager environment. We are currently building and testing a new release to address the issue. Updates will be shared as more information becomes available. #INC49575022
-
investigating Apr 20, 2026, 04:40 PM UTC
The issue impacting Contract Manager environment has been resolved. Service was restored after unblocking affected system components and stabilizing the environment. A permanent fix is being deployed to address the underlying security vulnerability and prevent recurrence. #INC49575022
-
resolved Apr 20, 2026, 04:42 PM UTC
The issue impacting Contract Manager environment has been resolved. Service was restored after unblocking affected system components and stabilizing the environment. A permanent fix is being deployed to address the underlying security vulnerability and prevent recurrence. #INC49575022
Read the full incident report →
- Detected by Pingoru
- Apr 14, 2026, 08:47 AM UTC
- Resolved
- Apr 14, 2026, 12:33 PM UTC
- Duration
- 3h 46m
Affected: Real Time
Timeline · 5 updates
-
investigating Apr 14, 2026, 08:47 AM UTC
The Medical Network Payer Connectivity Services Realtime Processing is experiencing and a Realtime service interruption. As a result all Realtime processing is down. Our teams are actively working to troubleshoot and resolve the issue. INC# INC49466830
-
investigating Apr 14, 2026, 09:47 AM UTC
Medical Network PCS – Real-Time Processing is currently experiencing a service interruption, and all real-time transactions are unavailable. Engineering teams are actively investigating the issue and working on restoration. Updates will be shared as more information becomes available. INC# INC49466830
-
investigating Apr 14, 2026, 10:51 AM UTC
Medical Network PCS real‑time services remain down; engineering teams are actively troubleshooting and performing recovery actions. INC# INC49466830
-
investigating Apr 14, 2026, 11:45 AM UTC
We are currently experiencing a service interruption affecting Medical Network PCS real-time processing. At this time, all real-time transactions are unavailable. Our engineering teams are actively investigating the issue and working to restore service as quickly as possible. INC# INC49466830
-
resolved Apr 14, 2026, 12:33 PM UTC
Teams restored the missing components through an approved emergency action, after which real‑time transactions started working again. Thank you for your patience as our teams worked to resolve this incident. INC# INC49466830
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 03:37 PM UTC
- Resolved
- Apr 09, 2026, 03:45 PM UTC
- Duration
- 8m
Affected: TES Ambulatory
Timeline · 2 updates
-
investigating Apr 09, 2026, 03:37 PM UTC
We are aware of the ZScaler issues with MDIV/MMIS. We are actively investigating the issue with the larger Optum/Zscaler team and will provide updates as soon as available. INC #INC49392819
-
resolved Apr 09, 2026, 03:45 PM UTC
The Zscaler issue with MDIV/MMIS has been resolved. We appreciate your patience while being restored.
Read the full incident report →
- Detected by Pingoru
- Apr 03, 2026, 03:47 PM UTC
- Resolved
- Apr 03, 2026, 05:41 PM UTC
- Duration
- 1h 53m
Affected: Pharmacy Software Solutions
Timeline · 3 updates
-
investigating Apr 03, 2026, 03:47 PM UTC
We are aware of the slow EPR response times. We are actively investigating the slowness and will provide updates as more information becomes available. We apologize for any inconvenience this may cause. INC#INC49298901
-
identified Apr 03, 2026, 04:03 PM UTC
We are still working on the Central Services Database failover. During this time there will be a brief outage. We appreciate your patience as we’re working towards the solution. INC#INC49298901
-
resolved Apr 03, 2026, 05:41 PM UTC
Customers, We have resolved the issue causing slowness within EPR. We appreciate your patience as we worked towards the solution. INC#INC49298901
Read the full incident report →
- Detected by Pingoru
- Mar 20, 2026, 02:54 PM UTC
- Resolved
- Mar 20, 2026, 11:40 PM UTC
- Duration
- 8h 46m
Timeline · 5 updates
-
investigating Mar 20, 2026, 02:54 PM UTC
We are aware of an issue occurring within the system. We will provide updates as more information becomes available. Incident type : Estimator is down Incident description: Estimator is down for all customers currently, and we are working to resolve this issue as quickly as possible. INC#INC49049942
-
investigating Mar 20, 2026, 05:13 PM UTC
The team is currently aware of an issue within the system and will provide further updates as more details are confirmed. Incident type : Estimator is down Incident description: Estimator is down for all customers currently, and we are working to resolve this issue as quickly as possible. INC#INC49049942
-
identified Mar 20, 2026, 07:24 PM UTC
The team is aware of the issue affecting the system and will share updates as additional details become available. Call has been reconvened to 05:00 PM EST for further investigation.
-
identified Mar 20, 2026, 09:22 PM UTC
The team knows about the issue impacting the system and will provide updates when more information is available. INC#INC49049942
-
resolved Mar 20, 2026, 11:40 PM UTC
The issue that impacted the estimator has been resolved. Thank you for your patience as our teams worked to resolve this incident. INC#INC49049942
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2026, 01:56 PM UTC
- Resolved
- Mar 18, 2026, 06:39 PM UTC
- Duration
- 4h 43m
Timeline · 3 updates
-
investigating Mar 18, 2026, 01:56 PM UTC
We are aware that customers may not be able to login to EngageCare Provider. Our teams are actively working to troubleshoot and resolve the issue. INC #INC49002906
-
monitoring Mar 18, 2026, 03:13 PM UTC
We continue to monitor the issue and teams remain actively engaged. Further updates will be provided as available.
-
resolved Mar 18, 2026, 06:39 PM UTC
The login issues for EngageCare Provider are now resolved. If you have any further issues, please open Customer Care Hub Support Request. INC #INC49002906
Read the full incident report →
- Detected by Pingoru
- Mar 14, 2026, 05:01 PM UTC
- Resolved
- Mar 14, 2026, 07:42 PM UTC
- Duration
- 2h 40m
Affected: Pharmacy Network Solutions
Timeline · 3 updates
-
investigating Mar 14, 2026, 05:01 PM UTC
Optum has identified a critical connectivity issue affecting transactions routed to Prime Therapeutics / Magellan. The issue is resulting in connection‑to‑payer errors and is currently preventing successful claim processing for impacted plans. Optum teams are actively engaged and working with the payer to restore connectivity as quickly as possible. BIN 022659 BIN 009737/ 011503 BIN 002286 INC #INC48943150
-
investigating Mar 14, 2026, 06:13 PM UTC
Issue Ongoing- Optum has identified a critical connectivity issue affecting transactions routed to Prime Therapeutics / Magellan. The issue is resulting in connection‑to‑payer errors and is currently preventing successful claim processing for impacted plans. Optum teams are actively engaged and working with the payer to restore connectivity as quickly as possible. BIN 022659 BIN 009737/ 011503 BIN 002286 INC #INC48943150
-
resolved Mar 14, 2026, 07:42 PM UTC
3-14-2026 there was a critical connectivity issue affecting transactions routed to Prime Therapeutics / Magellan. The issue is resulted in connection‑to‑payer errors and preventing successful claim processing for impacted plans. Optum teams engaged with Prime and connectivity is restored on 3-14-2026 at 2:10pm CST. Please resubmit any impacted claims. BIN 022659- resolved BIN 009737/ 011503- resolved BIN 002286- resolved INC #INC48943150
Read the full incident report →
- Detected by Pingoru
- Mar 09, 2026, 07:44 PM UTC
- Resolved
- Mar 10, 2026, 01:45 PM UTC
- Duration
- 18h
Affected: Pharmacy Network Solutions
Timeline · 5 updates
-
investigating Mar 09, 2026, 07:44 PM UTC
Recast Claim Formatter performed an infrastructure change over the weekend which involved recreating a virtual machine that changed its private IP address which then prevented the firewall access as it was originally opened only previous private ip address. We are currently in the process of resolving this issue, opening the firewall and performing a rolling restart. Some of you may not be experiencing any issues while others are. #INC48839327
-
identified Mar 09, 2026, 08:20 PM UTC
The call has moved to reconvene to perform the required firewall updates to restore service. Further updates will be shared once the call resumes at 10:15 PM EST. #INC48839327
-
monitoring Mar 10, 2026, 02:35 AM UTC
We are currently implementing the planned changes identified during the war room. The team is actively monitoring the process, and updates will be shared as progress continues. #INC48839327
-
monitoring Mar 10, 2026, 05:25 AM UTC
The call has been moved to 09:30 AM CT as the current activity is still in progress and needs more time. The team will confirm the application status once it is completed. #INC48839327
-
resolved Mar 10, 2026, 01:45 PM UTC
Recast Claim Formatter services are restored to full activity. #INC48839327
Read the full incident report →
- Detected by Pingoru
- Mar 07, 2026, 07:07 PM UTC
- Resolved
- Mar 08, 2026, 02:26 AM UTC
- Duration
- 7h 19m
Affected: Pharmacy Software Solutions
Timeline · 6 updates
-
investigating Mar 07, 2026, 07:07 PM UTC
We are facing issues with traffic routed through wso2. Any services leveraged through this will be impacted. We are actively investigating the problem and will provide updates as more information becomes available. Services impacted: WSO2 Services #INC48815572
-
identified Mar 07, 2026, 08:07 PM UTC
We are seeing alleviation with traffic routed through WSO2. You should now be able to search prescribers, perform DEA validation, and leverage any APIs that go through WSO2. We will continue to monitor performance with will provide updates accordingly. Services impacted: WSO2 Services; Central Prescriber, DEA Validation, APIs #INC48815572
-
identified Mar 07, 2026, 09:21 PM UTC
We are seeing alleviation with traffic routed through WSO2. You should now be able to search prescribers, perform DEA validation, and leverage any APIs that go through WSO2. we're working with a customer facing issues on their end. We will continue to monitor performance with will provide updates accordingly. Services impacted: WSO2 Services; Central Prescriber, DEA Validation, APIs #INC48815572
-
identified Mar 07, 2026, 11:35 PM UTC
We are seeing alleviation with traffic routed through WSO2. You should now be able to search prescribers, perform DEA validation, and leverage any APIs that go through WSO2. we're working with a customer facing issues on their end. We will continue to monitor performance with will provide updates accordingly. Services impacted: WSO2 Services; Central Prescriber, DEA Validation, APIs #INC48815572
-
identified Mar 08, 2026, 12:39 AM UTC
We are seeing alleviation with traffic routed through WSO2. You should now be able to search prescribers, perform DEA validation, and leverage any APIs that go through WSO2. We will continue to monitor performance and provides next update at 20:45:00 CT. #INC48815572
-
resolved Mar 08, 2026, 02:26 AM UTC
We restarted WSO2 to clear out failed connections and monitored performance while working with customers. #INC48815572
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2026, 04:04 PM UTC
- Resolved
- Mar 06, 2026, 04:16 PM UTC
- Duration
- 12m
Timeline · 2 updates
-
investigating Mar 06, 2026, 04:04 PM UTC
We are currently investigating an issue impacting InterQual Connect customers using prod.ds.interqual.com or prod2.ds.interqual.com, where users are receiving blank screen or error when they launch InterQual. Our team is actively working to identify and resolve the problem. We will provide additional information as our investigation progresses. Current Status: We are currently investigating this issue. Additional information will be provided as we make progress towards a resolution. #INC48798457
-
resolved Mar 06, 2026, 04:16 PM UTC
The issue that was preventing users from accessing InterQual has been resolved. If you are still experiencing issues, please clear your browser cache and try again. If the issue persists, please contact Product Support. #INC48798457
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2026, 01:10 PM UTC
- Resolved
- Mar 06, 2026, 03:24 PM UTC
- Duration
- 2h 14m
Affected: Pharmacy Software Solutions
Timeline · 4 updates
-
investigating Mar 06, 2026, 01:10 PM UTC
We are aware of an issue with Central Prescriber resulting in failures during Prescriber searches. We are actively working with the vendor to resolve. #INC48793810
-
identified Mar 06, 2026, 02:05 PM UTC
The issue has been identified as a certificate issue with Lexis Nexis. We are working with them to resolve. #INC48793810
-
identified Mar 06, 2026, 03:01 PM UTC
We have identified the issue as a result of a certificate change implemented by LexisNexis and are actively working with LexisNexis to install the updated certificate. We will continue to provide updates as progress is made. #INC48793810
-
resolved Mar 06, 2026, 03:24 PM UTC
The Central Prescriber issue has been resolved; LexisNexis has reverted their change. #INC48793810
Read the full incident report →
- Detected by Pingoru
- Mar 05, 2026, 11:13 PM UTC
- Resolved
- Mar 06, 2026, 11:12 PM UTC
- Duration
- 23h 59m
Affected: Pharmacy Network Solutions
Timeline · 7 updates
-
investigating Mar 05, 2026, 11:13 PM UTC
Optum Insight migrated to Cloudflare for connectivity to rxnsconnect.changehealthcare.com effective date March 2, 2026. Some pharmacies may have intermittent connectivity issues. Technical staff is activity working to resolve any issues. If you experience any timeouts and your organization does IP filtering, you will need to whitelist for outbound traffic IP Subnet 168.183.3.128 /27 (usable range 168.183.3.128-168.183.3.159). If continue to see issues please report to your software vendor or call our customer support team at: 866-379-6389. #INC48787011
-
investigating Mar 06, 2026, 01:08 AM UTC
Some customers may continue to experience intermittent connectivity errors when connecting to rxnsconnect.changehealthcare.com. The technical teams are actively working to resolve the issue. We will provide further updates as more information becomes available on 3-6-2026 by 11 am CST. #INC48787011
-
investigating Mar 06, 2026, 05:09 PM UTC
Some customers may continue to experience intermittent connectivity errors when connecting to rxnsconnect.changehealthcare.com. The technical teams are actively working to resolve the issue. We will provide further updates as more information becomes available by 1 PM CST. #INC48787011
-
investigating Mar 06, 2026, 07:12 PM UTC
Some customers may continue to experience intermittent connectivity errors when connecting to rxnsconnect.changehealthcare.com. The technical teams are actively working to resolve the issue. We will provide further updates as more information becomes available by 3 PM CST. #INC48787011
-
investigating Mar 06, 2026, 08:58 PM UTC
Some customers may continue to experience intermittent connectivity errors when connecting to rxnsconnect.changehealthcare.com. The technical teams are actively working to resolve the issue. We will provide further updates as more information becomes available by 5 PM CST. #INC48787011
-
investigating Mar 06, 2026, 11:11 PM UTC
Optum Insight migrated to Cloudflare for connectivity to rxnsconnect.changehealthcare.com effective date March 2, 2026. Some pharmacies experienced intermittent connectivity issues. Technical staff worked diligently to resolve the issue. The issue was resolved at 4:18pm CST 3-6-2026. #INC48787011
-
resolved Mar 06, 2026, 11:12 PM UTC
Optum Insight migrated to Cloudflare for connectivity to rxnsconnect.changehealthcare.com effective date March 2, 2026. Some pharmacies experienced intermittent connectivity issues. Technical staff worked diligently to resolve the issue. The issue was resolved at 4:18pm CST 3-6-2026. #INC48787011
Read the full incident report →
- Detected by Pingoru
- Mar 04, 2026, 07:33 PM UTC
- Resolved
- Mar 06, 2026, 02:02 PM UTC
- Duration
- 1d 18h
Timeline · 8 updates
-
investigating Mar 04, 2026, 03:35 PM UTC
Customers may experience performance issues or errors on Direct Entry jobs due to password issues. INC # INC48750170
-
investigating Mar 04, 2026, 04:36 PM UTC
Customers may experience slowness or errors with Medicare Direct Entry jobs. Optum continues to research. INC # INC48750170
-
investigating Mar 04, 2026, 05:33 PM UTC
Customers have been provided a workaround for the password issue by disabling the automated DE password update and manually updating the password on the Medicare system. Optum continues to work on the root problem. INC # INC48750170
-
investigating Mar 04, 2026, 11:28 PM UTC
Customers may experience errors with Medicare Direct Entry processing. Resolution efforts are in process.
-
investigating Mar 05, 2026, 04:26 PM UTC
Customers may continue to experience slowness and errors with Medicare Direct Entry jobs. Research towards resolution continues. #INC48776620
-
investigating Mar 05, 2026, 06:39 PM UTC
Customers may continue to experience slowness and errors with Medicare Direct Entry jobs. The technical team is actively working to resolve the issue. We will provide further updates as more information becomes available at 2:00 PM CST. #INC48776620
-
identified Mar 05, 2026, 08:15 PM UTC
Customers continue to experience slowness and errors with Medicare Direct Entry. A fix is in review and will be distributed tonight. #INC48776620
-
resolved Mar 06, 2026, 02:02 PM UTC
This issue has been resolved. Performance has returned to optimal levels. Support will resume all impacted jobs for hosted clients. For Turnkey clients, please resume any failed jobs. If you have any questions, please contact Support. Action Needed: Please reinstate the automated password changes in Assurance if you disabled them. If you are still experiencing issues with your password, please contact Medicare to reset your password and update the information within Assurance. #INC48776620
Read the full incident report →
- Detected by Pingoru
- Mar 04, 2026, 06:00 PM UTC
- Resolved
- Mar 04, 2026, 06:22 PM UTC
- Duration
- 21m
Timeline · 2 updates
-
investigating Mar 04, 2026, 06:00 PM UTC
We are currently experiencing intermittent issues with MDIV this morning. Our AIX and MDIV engineering teams are actively working to identify the root cause and resolve the issue as quickly as possible. Thank you for your patience and understanding while we work through this. We will share updates on any significant developments and notify you as soon as service is fully restored. INC# INC48748784
-
resolved Mar 04, 2026, 06:22 PM UTC
Corrective actions implemented - services restored. INC# INC48748784
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 04:35 PM UTC
- Resolved
- Mar 03, 2026, 05:02 PM UTC
- Duration
- 26m
Timeline · 2 updates
-
investigating Mar 03, 2026, 04:35 PM UTC
An update has been loaded to hosted Assurance which will resolve account errors caused yesterday. Support is working to resume jobs failed currently. Turnkey customer should request Product Update to retrieve the files. INC# INC48727484
-
resolved Mar 03, 2026, 05:02 PM UTC
Updates have been applied to correct account errors and failed jobs are running successfully. INC# INC48727484
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 02:45 PM UTC
- Resolved
- Mar 02, 2026, 07:49 PM UTC
- Duration
- 5h 4m
Timeline · 5 updates
-
investigating Mar 02, 2026, 02:45 PM UTC
Assurance Reimbursement Management is experiencing an issue with intermittent performance with Medicare Direct Entry (MDE). This may result in: Failed, queued, slow jobs ERROR: Unrecognized screen encountered after screen 'edsnet_blankscreen' Optum is working to resolve this issue. We will notify you as soon as additional information becomes available. We apologize for any inconvenience. INC/CSA/Ref # INC48697869
-
investigating Mar 02, 2026, 04:12 PM UTC
We are working on correcting our process to accommodate the changes made to the MDE System. INC/CSA/Ref # INC48697869
-
identified Mar 02, 2026, 05:18 PM UTC
Fix is ready, working on getting up to our distribution server now. INC/CSA/Ref # INC48697869
-
monitoring Mar 02, 2026, 06:15 PM UTC
Updated scripts have been tested and distributed to production. Support has started resuming failed jobs. Further updates will be provided at 2PM CST. INC/CSA/Ref # INC48697869
-
resolved Mar 02, 2026, 07:49 PM UTC
The updated scripts have been distributed and all impacted jobs have been restarted. Turnkey customers need to run EPD to receive the fix, then restart failed jobs.
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 01:47 PM UTC
- Resolved
- Feb 27, 2026, 02:28 PM UTC
- Duration
- 40m
Timeline · 2 updates
-
investigating Feb 27, 2026, 01:47 PM UTC
We are aware of an issue with end-users experiencing errors while trying to access the Clinical Exchange application. We are investigating this as a priority. INC# INC48666477
-
resolved Feb 27, 2026, 02:28 PM UTC
An issue with some end‑users experiencing errors while attempting to access the Clinical Exchange application has been resolved. We are continuing to monitor. INC# INC48666477
Read the full incident report →