История сбоев Centralreach

1. 17 августа 2026 г. в 17:05 UTCidentified

   Наш провайдер сканирования файлов испытывает проблему, которая влияет на доступ к недавно загруженным файлам в CentralReach. В результате некоторые файлы, загруженные недавно, могут быть временно недоступны для просмотра или загрузки. Мы приносим извинения за нарушение и ценим ваше терпение, в то время как мы активно работаем над восстановлением доступа как можно быстрее.

2. 17 августа 2026 г. в 19:58 UTCresolved

   Все области платформы вернулись к ожидаемым операционным уровням.

Автоматический перевод официального обновления инцидента.

1. 13 августа 2026 г. в 16:50 UTCinvestigating

   Мы знаем, что пользователи испытывают медлительность платформы CentralReach. Наша команда активно расследует и работает над тем, чтобы как можно скорее урегулировать этот инцидент. Приносим извинения за неудобства. Мы предоставим больше информации, как только она будет доступна.

2. 13 августа 2026 г. в 17:05 UTCidentified

   We're making adjustments to improve user experience and responsiveness of the CentralReach platform. Our team is continues to investigate and are working to resolve this incident as soon as possible. We will provide more information as soon as it's available.

3. 13 августа 2026 г. в 17:22 UTCmonitoring

   The CentralReach platform has returned to expected operating levels. We're continuing to monitor performance out of an abundance of caution.

4. 13 августа 2026 г. в 18:01 UTCresolved

   This incident has been resolved.

Автоматический перевод официального обновления инцидента.

1. 17 июня 2026 г. в 12:41 UTCinvestigating

   We are currently experiencing system performance issues resulting in some users being unable to save or create appointments in the CentralReach platform. Our team is investigating and rapidly working toward a resolution.

2. 17 июня 2026 г. в 13:26 UTCmonitoring

   An update has been implemented that has improved the experience. Appointments are now working as expected. We're continuing to monitor in an abundance of caution.

3. 17 июня 2026 г. в 15:50 UTCresolved

   The CentralReach platform is now operating at consistent and expected levels. The incident is resolved.

1. 4 мая 2026 г. в 21:47 UTCinvestigating

   We are experiencing platform disruption that is preventing users from logging into CentralReach. Our teams are investigating and working to restore access as quickly as possible.

2. 4 мая 2026 г. в 22:08 UTCinvestigating

   Our teams are continuing to work to restore platform performance to expected levels. Experience has improved but some users may continue to experience slowness when loading some screens.

3. 4 мая 2026 г. в 22:27 UTCmonitoring

   Platform performance has returned to expected levels. We are monitoring to confirm the incident has been fully resolved and will provide a final update shortly.

4. 4 мая 2026 г. в 23:09 UTCresolved

   Platform performance has returned to expected levels and has been fully restored.

1. 19 февраля 2026 г. в 13:53 UTCinvestigating

   We are aware of platform performance problems with the CentralReach system. Our team is actively investigating and working to resolve this incident as soon as possible. We apologize for the inconvenience. We will provide more information as soon as it's available.

2. 19 февраля 2026 г. в 14:58 UTCmonitoring

   The CentralReach platform performance has significantly improved, and we are continuing to monitor. We will provide more information as soon as it's available.

3. 19 февраля 2026 г. в 15:16 UTCresolved

   CentralReach platform performance has returned to expected levels on the web and for CR Mobile.

1. 22 января 2026 г. в 21:56 UTCinvestigating

   Microsoft has a confirmed service degradation impacting multiple Microsoft 365 services. As a result, this is preventing some users who rely on Microsoft credentials from logging in to CentralReach. We apologize for the inconvenience, and will provide updates on this page.

2. 22 января 2026 г. в 22:44 UTCinvestigating

   Microsoft has a confirmed service degradation impacting multiple Microsoft 365 services. As a result, this is preventing some users who rely on Microsoft credentials or MFA emails from logging in to CentralReach. We apologize for the inconvenience, and will provide updates on this page.

3. 23 января 2026 г. в 14:13 UTCresolved

   Microsoft has cleared their disruption announcement and all log in activities are now operating as expected.

1. 20 октября 2025 г. в 13:01 UTCinvestigating

   We are experiencing a confirmed Amazon Web Services Outage which is affecting CentralReach users. As a result, this is preventing users from logging in to CentralReach. We apologize for the inconvenience, and we are working rapidly with AWS to restore access. https://health.aws.amazon.com/health/status

2. 20 октября 2025 г. в 14:41 UTCidentified

   Amazon Web Services (AWS) is experiencing a widespread issue, causing slower performance on some pages. We are working with AWS to resolve this issue as soon as possible. AWS Status page for more information: https://health.aws.amazon.com/health/status

3. 20 октября 2025 г. в 16:02 UTCidentified

   Amazon Web Services (AWS) is experiencing a widespread issue, but beginning to return to typical performance levels. Users may now notice improvements in the CentralReach platform. We are continuing to monitor and work with AWS to resolve this issue as soon as possible. AWS Status page for more information: https://health.aws.amazon.com/health/status

4. 21 октября 2025 г. в 13:59 UTCresolved

   AWS and CentralReach services have returned to expected operating levels.

1. 11 марта 2025 г. в 16:50 UTCinvestigating

   CentralReach is investigating brief disruptions in the platform lasting approximately 2 minutes. Some users may encounter a message that reads "upstream connect error". After 2 minutes, refresh the page to continue working as expected. Our team is actively working to identify the root cause and implement a fix as quickly as possible.

2. 13 марта 2025 г. в 21:12 UTCresolved

   Our teams have implemented an update to improve performance and user experience.

1. 29 января 2025 г. в 19:25 UTCinvestigating

   We are currently investigating reports of a service disruption that is intermittently preventing users from logging in to CentralReach. We apologize for the inconvenience, and we are working rapidly to restore consistent access.

2. 29 января 2025 г. в 19:45 UTCmonitoring

   The cause of the earlier disruption has been identified and resolved. We're continuing to monitor performance.

3. 29 января 2025 г. в 20:21 UTCresolved

   After monitoring and testing, we've confirmed that the platform performance has returned to expected levels.

1. 16 декабря 2024 г. в 15:19 UTCinvestigating

   We are experiencing an issue which is intermittently preventing some users from logging in to CentralReach. We apologize for the inconvenience, and we are working rapidly to restore the log in experience for all users.

2. 16 декабря 2024 г. в 15:31 UTCidentified

   A third party provider is experiencing an issue which is preventing some CentralReach users from logging in. We're working with the provider toward resolution.

3. 16 декабря 2024 г. в 15:42 UTCmonitoring

   CentralReach has restored log in access for all users. Users may need to clear cache for the best experience. We're continuing to work with our third-party and monitoring performance.

4. 16 декабря 2024 г. в 21:33 UTCresolved

   After careful monitoring and consistent activity, we're pleased to report that all areas of CentralReach and the log in screen are operating at expected levels.

1. 4 декабря 2024 г. в 17:48 UTCidentified

   We are aware that some users are intermittently having trouble logging into the CentralReach system. Our team has identified the issue and is working to resolve this incident as soon as possible. We apologize for the inconvenience. We will provide more information as soon as it's available.

2. 4 декабря 2024 г. в 18:10 UTCidentified

   Our engineering teams are continuing efforts to resolve issues affecting the ability to log in. We'll provide another update within 15 minutes.

3. 4 декабря 2024 г. в 18:21 UTCidentified

   Platform performance has improved and we're continuing to monitor. Users will notice improvements logging in.

4. 4 декабря 2024 г. в 18:21 UTCmonitoring

   Platform performance has improved and we're continuing to monitor. Users will notice improvements logging in.

5. 4 декабря 2024 г. в 18:26 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 4 декабря 2024 г. в 19:11 UTCresolved

   After monitoring and successful system testing, we're pleased to confirm that the CentralReach platform has fully returned to expected levels of operation.

1. 15 августа 2024 г. в 22:59 UTCinvestigating

   We have received customer reports of intermittent session log out behavior. Our teams are actively investigating and working toward resolution.

2. 16 августа 2024 г. в 14:48 UTCidentified

   We have received customer reports of intermittent session log out behavior. Our teams have identified the problem and are working toward resolution.

3. 19 августа 2024 г. в 13:50 UTCmonitoring

   A fix has been implemented, so users should notice improvements to session log out behavior. We are monitoring throughout the day today.

4. 20 августа 2024 г. в 15:41 UTCresolved

   After monitoring, we've confirmed that the session log out behavior is now functioning as expected.

1. 21 февраля 2024 г. в 15:24 UTCinvestigating

   Change Healthcare is continuing to experience a service disruption and is working to resolve the issue. Monitor at status.changehealthcare.com. The CentralReach platform is fully operational.

2. 22 февраля 2024 г. в 15:10 UTCidentified

   Change Healthcare is continuing to experience a service disruption and is working to resolve the issue. Monitor at status.changehealthcare.com. The CentralReach platform is fully operational.

3. 4 марта 2024 г. в 13:59 UTCidentified

   Change Healthcare is continuing to experience a service disruption and is working to resolve the issue. Monitor at status.changehealthcare.com. If you are a Change Healthcare customer, Change Healthcare has advised that claim submissions be paused at this time. The CentralReach platform is fully operational.

4. 18 марта 2024 г. в 16:17 UTCidentified

   Change Healthcare is continuing to experience a service disruption and is working to resolve the issue. Monitor at status.changehealthcare.com. If you are a Change Healthcare customer, Change Healthcare has advised that claim submissions remain paused at this time. The CentralReach platform is fully operational.

5. 26 марта 2024 г. в 21:43 UTCidentified

   Change Healthcare is continuing to experience a service disruption and is working to resolve the issue. Monitor at status.changehealthcare.com. Change Healthcare has begun reconnecting with payors, and is in a testing phase for their claims submissions process. We do not yet have clear timelines for the completion of their restoration efforts. The CentralReach platform is fully operational.

6. 12 апреля 2024 г. в 15:03 UTCmonitoring

   Change Healthcare has made progress in their restoration process. We have performed security and operational checks to confirm that we have the technical ability to safely submit claims and retrieve ERAs with Change Healthcare and have begun re-enabling this connectivity. Users should be aware that Change Healthcare has not yet fully reconnected with all payors and ConnectCenter is not yet available. If your organization opted to use a temporary Office Ally connection to submit claims, we recommend that you continue to use that option until ConnectCenter is available and all of your payors are reconnected. The full list of Change Healthcare Exchange Payors for claim submission and ERA retrieval is available at https://support.changehealthcare.com/customer-resources/payer-lists The CentralReach platform remains fully operational.

7. 2 июня 2024 г. в 01:19 UTCresolved

   CentralReach has successfully completed technical testing for submitting claims and retrieving Electronic Remittance Advices (ERAs) via the restored Change Healthcare platform. Please be advised that Change Healthcare is still in the process of reconnecting payors, and ConnectCenter remains unavailable. For ongoing updates on Change Healthcare's restoration efforts and information regarding their cybersecurity event, please refer to the following resources provided directly by Change Healthcare: List of Change Healthcare Payors for Claim Submission and ERA retrieval: https://support.changehealthcare.com/customer-resources/payer-lists Change Healthcare Cyber Attack Information Page: https://www.unitedhealthgroup.com/changehealthcarecyberresponse

1. 16 января 2024 г. в 15:56 UTCmonitoring

   We are aware of a third party McAffee Chrome extension preventing some users from logging in to CentralReach successfully. Disabling extensions will avoid disruptions of the CentralReach platform and user experience. CentralReach is fully operational at this time. Technical Support will assist with any questions or troubleshooting needs.

2. 17 января 2024 г. в 13:31 UTCresolved

   We are aware of a third party McAffee Chrome extension preventing some users from logging in to CentralReach successfully. Disabling extensions will avoid disruptions of the CentralReach platform and user experience. CentralReach is fully operational at this time. Technical Support will assist with any questions or troubleshooting needs.

1. 28 декабря 2023 г. в 23:08 UTCinvestigating

   We have detected slow response in the bulk connect/disconnect functions for the Manage Connections tool in Contacts. While our technical teams are actively working to improve this, please refrain from using this functionality at this this time. All other areas of the CentralReach platform are currently operating as expected.

2. 29 декабря 2023 г. в 01:25 UTCresolved

   Manage Connections tool in Contacts, including bulk updates are now working as expected.

1. 27 ноября 2023 г. в 17:37 UTCinvestigating

   We are aware that users are experiencing slowness and logouts within the CentralReach system. Our team is actively investigating and working to resolve this incident as soon as possible. We apologize for the inconvenience. We will provide more information as soon as it's available.

2. 27 ноября 2023 г. в 17:58 UTCidentified

   We have identified degraded performance in search functionality within the CentralReach platform. Our team is actively working to resolve this incident as soon as possible. We'll continue to provide information as it becomes available.

3. 27 ноября 2023 г. в 18:38 UTCmonitoring

   A fix has been put in place to resolve search and login capabilities that were affecting the CentralReach platform. We're continuing to monitor to ensure consistent performance.

4. 27 ноября 2023 г. в 19:04 UTCresolved

   Platform is now operating at expected performance levels.

1. 22 июня 2023 г. в 15:15 UTCinvestigating

   We've identified and confirmed with Office Ally that they are experiencing an issue preventing claims submission. We are actively investigating with the Office Ally team and will continue to provide updates on the CentralReach Status page. All other claims that are not sent through Office Ally are processing as expected at this time.

2. 22 июня 2023 г. в 15:28 UTCinvestigating

   We are continuing to investigate this issue.

3. 22 июня 2023 г. в 18:29 UTCinvestigating

   Office Ally are continuing to investigate an issue preventing claims submission. We are actively coordinating with the Office Ally team and will continue to provide updates on the CentralReach Status page. All other claims that are not sent through Office Ally are processing as expected at this time.

4. 22 июня 2023 г. в 19:50 UTCmonitoring

   Office Ally have identified the cause of earlier issues and put a fix in place to address problems with claims submission. CentralReach testing has confirmed that gateways are active and claims are successfully being submitted. Both CentralReach and Office Ally are continuing to monitor for consistent performance.

5. 22 июня 2023 г. в 21:00 UTCresolved

   Office Ally resolved the issue that was preventing claims submission. After monitoring by both CentralReach and Office Ally, we've observed performance operating at expected levels. We are resolving this incident, however if you're now encountering any unexpected behavior please contact CentralReach Technical Support for assistance.

1. 13 июня 2023 г. в 19:05 UTCinvestigating

   We are experiencing a confirmed Amazon Web Services Outage which is affecting some software providers such as CentralReach. As a result, this is preventing users from logging in to the CentralReach platform. We apologize for the inconvenience, and we are working rapidly with AWS to restore access.

2. 13 июня 2023 г. в 19:30 UTCidentified

   AWS have identified the cause of elevated error rates that are impacting CentralReach and are working on a fix. The CentralReach login screen continues to be affected, but we will update our status page while efforts continue toward restoring access.

3. 13 июня 2023 г. в 20:03 UTCidentified

   CentralReach is currently experiencing login issues due to AWS errors. Users currently logged in and utilizing the CentralReach platform are not affected. Be mindful of timeouts set in place by your organization to stay logged in and continue working. If you log out you will not be able to log back in until this incident is resolved. In the meantime, AWS are continuing to experience of elevated error rates that are impacting CentralReach. The Amazon Web Services teams are working on an urgent fix. The CentralReach login screen continues to be affected, but we will update our status page while efforts continue toward restoring access.

4. 13 июня 2023 г. в 20:21 UTCidentified

   AWS are continuing to experience of elevated error rates that are impacting CentralReach. The Amazon Web Services teams are working on an urgent fix. The CentralReach login screen continues to be affected, but we will update our status page while efforts continue toward restoring access.

5. 13 июня 2023 г. в 20:55 UTCidentified

   CentralReach is noticing improvements to the login page while AWS are reporting a decrease in the elevated error rates that they were experiencing. While some users will be able to log in to the CentralReach platform, please be aware that AWS is still restoring and monitoring services while they work toward full recovery, which may result in intermittent error messages and forced logouts.

6. 13 июня 2023 г. в 21:42 UTCmonitoring

   CentralReach is noticing improvements to the login page while AWS are reporting that their APIs are recovering. We expect that users will be able to log in to the CentralReach platform, however, please be aware that AWS is still monitoring services while they work toward full recovery, which may result in intermittent error messages or unexpected logouts.

7. 13 июня 2023 г. в 22:13 UTCmonitoring

   CentralReach is noticing improvements to our login page while AWS are reporting that their APIs are recovering. We expect that users will be able to log in to the CentralReach platform, however, please be aware that AWS is still monitoring services while they work toward full recovery,

8. 13 июня 2023 г. в 23:09 UTCresolved

   AWS shared that their issue has cleared and all AWS systems are up and running at expected performance as of 6:47PM ET. CentralReach has performed additional testing on our platform and services, and confirmed that CentralReach is fully operating as expected, including the log in page. This incident is now resolved. If you're experiencing any unexpected behavior at this time, we encourage you to submit a case with CentralReach Technical Support through the CR Community at community.centralreach.com or by phone at 800.939.5414 Option 2.

1. 8 июня 2023 г. в 13:59 UTCidentified

   Claims processing vendor, Change Healthcare, is currently experiencing severe network issues that are significantly impacting application availability for several applications. Real-time processing and some batch processing is down. Change Healthcare engineering teams are working to restore service for these applications. The CentralReach platform and services are otherwise fully operational. Updates will be shared here, and more information is available at the Change Healthcare Status page: https://status.changehealthcare.com/

2. 8 июня 2023 г. в 14:28 UTCidentified

   Change Healthcare is continuing to work on a fix for this issue. Currently network issues are significantly impacting the availability of several of Change Healthcare's applications. The CentralReach platform and services are otherwise fully operational. More info at https://status.changehealthcare.com/

3. 8 июня 2023 г. в 20:11 UTCidentified

   The Change Healthcare network and engineering team is continuing to troubleshoot the issue and monitor intermittent connectivity. There is not an ETA for resolution at this time. The CentralReach platform and services remain otherwise fully operational. More info at https://status.changehealthcare.com/

4. 8 июня 2023 г. в 21:01 UTCidentified

   Change Healthcare is currently experiencing an outage impacting customer-facing applications that use Amazon Web Services (AWS) Cloud Services. Applications are experiencing intermittent connectivity, with customers unable to login. Engineering, application and vendor teams are working to restore connectivity, and an update will be provided when available. The CentralReach platform and services remain otherwise fully operational. You can find updates here as well as the Change Healthcare Status page: https://status.changehealthcare.com/

5. 9 июня 2023 г. в 02:36 UTCidentified

   The Change Healthcare network and engineering team has isolated the problem of incoming traffic to a subset of our network and applications. They are working through specific actions to mitigate the issue. With information currently available, please plan for access to be unavailable tomorrow (June 9). All vendors and appropriate teams are working on this with the highest priority. The CentralReach platform and services remain otherwise fully operational. More info at https://status.changehealthcare.com/

6. 9 июня 2023 г. в 11:25 UTCmonitoring

   Change Healthcare has restored and validated most of their core services, and expect that services will function properly at the start of business on Friday, June 9. Please be aware that you may experience some slowness with claims processing throughout the day as services resume. Change Healthcare and CentralReach will monitor throughout the day and weekend.

7. 9 июня 2023 г. в 15:37 UTCresolved

   Change Healthcare have restored and validated core services and continue to observe proper system functionality. You may experience some slowness throughout the day as services resume and absorb volume, and as Change Healthcare continues to re-optimize traffic. If you sent claims yesterday, we strongly encourage that you audit for any error messages and check whether these claims are in Change Healthcare. If they are not in Change Healthcare's environment, resend the claim. Contact CentralReach Technical Support if you receive any further errors today. If the claims are present in the Change Healthcare environment, please be patient while they continue to process.

1. 24 мая 2023 г. в 15:43 UTCinvestigating

   We are currently investigating reports of a service disruption that is preventing users from logging in to CentralReach. We apologize for the inconvenience, and we are working rapidly to restore access.

2. 24 мая 2023 г. в 15:46 UTCinvestigating

   We've identified the source of a problem that is preventing users from logging in to CentralReach. We apologize for the inconvenience, and we are working rapidly to restore access.

3. 24 мая 2023 г. в 16:15 UTCinvestigating

   Platform performance is now operating as expected. Please reach out to our Technical Support team if you have any questions or concerns.

4. 24 мая 2023 г. в 16:21 UTCresolved

   This incident has been resolved.