Philips HealthSuite Outage History

Started Jun 19, 2026, 10:33 AM UTC· resolved Jun 19, 2026, 10:47 AM UTC

1. investigating Jun 19, 2026, 10:33 AM UTC

   We are currently working the issue

Read the full incident report →

Started May 08, 2026, 08:09 AM UTC· resolved May 09, 2026, 08:56 AM UTC

1. investigating May 08, 2026, 08:09 AM UTC

   Operational issue – Amazon Elastic Compute Cloud (N. Virginia) Service Amazon Elastic Compute Cloud Increased Error Rate and Latency May 07 10:11 PM PDT We are observing early signs of recovery. We continue to work towards restoring temperatures to normal levels and bring impacted racks back online in the affected Availability Zone (use1-az4) in the US-EAST-1 Region. We have been able to get additional cooling system capacity online, which has allowed us to recover some affected racks and are actively working to recover additional racks in a controlled and safe manner. In the impacted Availability Zone, EC2 Instances, EBS Volumes, and other AWS Services may continue to experience elevated error rates and latencies for some workflows until full recovery is achieved. We will provide an update by 11:30 PM PDT, or sooner if we have additional information to share. May 07 8:06 PM PDT We are actively working to restore temperatures to normal levels in the affected Availability Zone (use1-az4) in the US-EAST-1 Region, though progress is slower than originally anticipated. Since our last update we have made incremental progress to restore cooling systems within the affected AZ, which will not be visible to external customers but are required for the restoration of affected services. In the impacted Availability Zone, EC2 Instances, EBS Volumes, and other AWS Services are also experiencing elevated error rates and latencies for some workflows. As part of our recovery effort, we have shifted traffic away from the impacted Availability Zone for most services. We recommend customers utilize one of the other Availability Zones in the US-EAST-1 Region, as existing instances in other AZs remain unaffected by this issue. If immediate recovery is required, we recommend customers restore from EBS Snapshots and/or replace affected resources by launching new replacement resources in one of the unaffected zones. We will provide an update by 10:00 PM PDT, or sooner if we have additional information to share. May 07 6:47 PM PDT We continue to work towards mitigating the increased temperatures to its normal levels in the affected Availability Zone (use1-az4) in the US-EAST-1 Region. Other AWS services that depend on the affected EC2 instances and EBS volumes in this Availability Zone, may also experience impairments. We have weighed away traffic for most services at this time. We recommend customers utilize one of the other Availability Zones in the US-EAST-1 Region at this time, as existing instances in other AZ's remain unaffected by this issue. Customers may experience longer than usual provisioning times. We will provide an update by 7:45 PM PDT, or sooner if we have additional information to share. May 07 5:53 PM PDT We continue to investigate instance impairments to a single Availability Zone (use1-az4) in the US-EAST-1 Region. We have experienced an increase in temperatures within a single data center, which in some cases has caused impairments for instances in the Availability Zone. EC2 instances and EBS volumes hosted on impacted hardware are affected by the loss of power during the thermal event. Other AWS services that depend on the affected EC2 instances and EBS volumes in this Availability Zone, may also experience impairments. We will continue to provide updates as recovery continues. May 07 5:25 PM PDT We are investigating instance impairments in a single Availability Zone (use1-az4) in the US-EAST-1 Region. Other Availability Zones are not affected by the event and we are working to resolve the issue. Affected AWS services The following AWS services have been affected by this issue. Impacted (8 services) AWS IoT Core Amazon ElastiCache Amazon Elastic Kubernetes Service Amazon Elastic Load Balancing Amazon Managed Streaming for Apache Kafka Amazon OpenSearch Service Amazon Redshift Amazon SageMaker

2. investigating May 08, 2026, 08:11 AM UTC

   Update: May 07 11:38 PM PDT We continue to make progress in resolving the impaired EC2 instances in the affected Availability Zone (use1-az4) in the US-EAST-1 Region, and are working towards full recovery. We are actively working to bring additional cooling system capacity online, which will enable us to recover the remaining affected racks in a controlled and safe manner. In the impacted Availability Zone, EC2 Instances, EBS Volumes, and other AWS Services may continue to experience elevated error rates and latencies for some workflows. Customers will continue to see some of their affected EC2 instances and EBS volumes as impaired until we achieve full recovery. We will provide an update by May 8, 1:30 AM PDT, or sooner if we have additional information to share.

3. investigating May 08, 2026, 09:02 AM UTC

   May 08 1:32 AM PDT Mitigation efforts remain underway to resolve the impaired EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region. These EC2 instances and EBS volumes were impacted due to a loss of power during the thermal event. The work to bring additional cooling system capacity online, which will enable us to recover the remaining affected infrastructure in a controlled and safe manner, is taking longer than we had initially anticipated. Some services, such as IoT Core, ELB, NAT Gateway, and Redshift, have seen significant improvements in the recovery of their workflows. However, some customers will continue to see their affected EC2 instances and EBS volumes as impaired until we achieve full recovery. While we do not currently have an ETA for full recovery, we are prioritizing this issue and will provide another update by 3:30 AM PDT or sooner if additional information becomes available.

4. investigating May 08, 2026, 11:06 AM UTC

   May 08 3:54 AM PDT We continue to make progress towards resolving the impaired EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region. At this time, we wanted to provide some more details on the issue. Beginning on May 7 at 4:20 PM PDT, we began experiencing an increase in instance impairments within the affected zone due to the loss of power during a thermal event. Engineers were automatically engaged within minutes and immediately began investigating multiple mitigations. By 9:12 PM PDT, we restored power to a subset of the affected infrastructure and observed some signs of recovery, which have remained stable. We continue working to bring additional cooling system capacity online, which will enable us to recover the remaining affected hardware in the impacted zone in a controlled and safe manner. Some AWS services, such as IoT Core, ELB, NAT Gateway, and Redshift, continue to see significant improvements in the recovery of their workflows. However, some customers will continue to see their affected EC2 instances and EBS volumes as impaired until we achieve full recovery. If immediate recovery is required, we recommend customers restore from EBS snapshots and/or replace affected resources by launching new replacement resources in one of the unaffected zones. Based on our current mitigation efforts, we expect full recovery to take several hours. We are prioritizing this issue and will provide another update by 6:30 AM PDT or sooner if additional information becomes available.

5. investigating May 09, 2026, 08:47 AM UTC

   [RESOLVED] Increased Error Rate and Latency May 08 8:04 PM PDT Starting May 7 4:20 PM PDT, we experienced increased impaired EC2 instances and degraded EBS volumes in a single facility (data center) within a single Availability Zone (use1-az4) in the US-EAST-1 Region. The issue was caused by a thermal event resulting in a loss of power. As part of our recovery effort, we shifted traffic away from the impacted Availability Zone for most services at May 7 5:06 PM. AWS services, like Elastic Load Balancing, Elastic Kubernetes Service, ElastiCache, Redshift, OpenSearch, Managed Streaming for Apache Kafka among others, that depend on the affected EC2 instances and EBS volumes in this Availability Zone, also experienced elevated error rates and latencies for some workflows and/or configurations. Our main effort during the event mitigation strategy was to bring back our cooling systems capacity. By May 8 1:50 PM, we were able to stabilize cooling system capacity to pre-event levels, which helped us to restore the majority of the impaired EC2 instances and EBS volumes. A small number of instances and EBS volumes remain impaired and we continue to work to recover all affected remaining resources. We will communicate with customers who are still impacted via the Your Account view of the AWS Health Dashboard. Customers that require further assistance with this event may contact AWS Support through the AWS Management Console or the AWS Support Center. May 08 4:00 PM PDT We have begun to see improvements in the overall number of affected EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region. The steps taken to supply additional cooling capacity have been showing steady signs of progress. Some EBS Volumes and EC2 instances affected by the issue will continue to experience impairments while we continue to drive these efforts. We continue to recommend that customers who require immediate recovery restore from EBS snapshots and/or replace affected resources by launching new replacement resources. In parallel, we have seen some improvements in Amazon Managed Streaming for Apache Kafka as a result of the parallel mitigation efforts being performed. We are still experiencing timeouts to partitions but are seeing continued progress. We do anticipate that recovery will still take several hours. We will provide an additional update by 7:30 PM or sooner if we have new information to provide. May 08 12:29 PM PDT We continue to work towards the recovery of the impaired EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region though efforts are slower than we had previously anticipated. We are taking measured steps to ensure that cooling capacity is brought online in a safe and controlled manner. As a result, EBS Volumes and EC2 instances affected by the issue will continue to experience impairments. We continue to recommend that customers who require immediate recovery restore from EBS snapshots and/or replace affected resourced by launching new replacement resources. Full recovery is still expected to take several hours. We will provide an additional update by 4:00 PM or sooner if we have new information to provide. May 08 11:12 AM PDT We are experiencing an increase in timeouts to Amazon Managed Streaming for Apache Kafka partitions on a subset of clusters as a result of the ongoing issue in a single Availability Zone (use1-az4) in the US-EAST-1 Region. We are working in parallel to determine a path towards mitigation for affected clusters. We will provide an additional update by 12:30 PM or sooner. May 08 9:30 AM PDT We have observed complete recovery of increased error rates and query failures for Redshift clusters in the US-EAST-1 Region. We were able to resolve the impact independently of the ongoing efforts to recover the affected hardware in the use1-az4 Availability Zone. The issue affecting Redshift has been resolved and the service is operating normally. We will provide an additional update regarding the efforts towards hardware restoration by 12:30 PM or sooner. May 08 8:58 AM PDT We continue our efforts to work towards the recovery of the impaired EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region. We are making progress towards the restoration of the cooling system capacity that is required to recover the affected hardware in the impacted zone. Some customers will continue to see their affected EC2 instances and EBS volumes as impaired until the affected racks are recovered. We continue to recommend that customers who require immediate recovery restore from EBS snapshots and/or replace affected resources by launching new replacement resources in one of the unaffected zones. As part of our parallel investigation, we have identified the root cause of the increased error rates and query failures for Redshift clusters in the US-EAST-1 Region. This has been confirmed to be related to impact from an upstream dependency. Affected customers may continue to see errors for resume and restart workflows, failover operations, and impact to general availability. We are actively working to resolve the issue. Our timeline for full recovery is still expected to take several hours and will be incremental as we bring racks online in phases. We will provide an additional update by 12:30 PM or sooner if we have new information to provide. May 08 6:51 AM PDT We continue working to resolve the impaired EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region caused by a thermal event. During such an event, servers automatically shut down when the temperatures exceeded the operating thresholds in order to protect the hardware. We are actively working to bring additional cooling system capacity online, which will enable us to recover the remaining affected hardware in the impacted zone. Some customers will continue to see their affected EC2 instances and EBS volumes as impaired until we achieve full recovery. If immediate recovery is required, we recommend customers restore from EBS snapshots and/or replace affected resources by launching new replacement resources in one of the unaffected zones. In parallel, we are investigating increased error rates and query failures for Redshift clusters in the US-EAST-1 Region. During this time, affected customers may see errors for resume and restart workflows, as well as failover operations and availability issues. Our engineers are actively working to resolve this issue. Full recovery is still expected to take several hours. We are prioritizing this issue and will provide another update by 9:00 AM PDT or sooner if additional information becomes available.

Read the full incident report →

Started Apr 19, 2026, 02:30 AM UTC· resolved Apr 19, 2026, 10:40 AM UTC

1. identified Apr 19, 2026, 08:35 AM UTC

   The issue causing PRS applications to not launch has been identified and is in the process of being resolved.

2. identified Apr 19, 2026, 08:36 AM UTC

   We are continuing to work on a fix for this issue.

3. resolved Apr 19, 2026, 10:40 AM UTC

   This issue has been resolved

Read the full incident report →

Started Feb 10, 2026, 10:19 PM UTC· resolved Feb 10, 2026, 10:54 PM UTC

1. investigating Feb 10, 2026, 10:19 PM UTC

   - HSDP ConnectIOT Concentrator Service is experiencing intermittent failures - Start time of the outage: 9:14PM UTC - Engineering teams are investigating the issue to determine the source of the issue - There is no ETR at this time. Additional updates will be posted as soon as they become available.

2. resolved Feb 10, 2026, 10:54 PM UTC

   The service experienced a temporary internal server error (5xx), which caused brief request failures. The service is now up and running.

Read the full incident report →

Started Jan 29, 2026, 09:00 AM UTC· resolved Jan 29, 2026, 09:00 AM UTC

1. resolved Jan 29, 2026, 02:07 PM UTC

   2026‑01‑29 04:01 (ET) Our team identified and began monitoring a service disruption affecting the Vault Broker service in the US‑East Production region. The appropriate teams were engaged and immediately began investigating and working toward remediation. 2026‑01‑29 05:17 (ET) Our Infrastructure team continues active investigation. We have identified a backend connectivity issue and are working to restore normal service operations. This issue is being treated as a priority, and we will provide the next update as soon as meaningful progress is made. 2026‑01‑29 05:54 (ET) Service has been fully restored and is now operating normally.

Read the full incident report →

Started Jan 28, 2026, 06:31 PM UTC· resolved Jan 28, 2026, 07:32 PM UTC

1. investigating Jan 28, 2026, 06:31 PM UTC

   Environments Impacted: Networking Issue in EU-WEST-1 Region Action Required: Informational Only What’s Happening: We have received word that AWS is currently experiencing a networking issue in EU-WEST-1. AWS has confirmed elevated latencies for network change propagation in the EU-WEST-1 Region. This causes delays when attempting to connect to newly launched instances using their assigned public IPs, as well as delays in establishing new VPC Peering connections. Other AWS Services are also impacted by this issue and may be impacted by delayed or stuck workflows such as pulling container images. Engineers with AWS were automatically engaged and are actively working on mitigating this issue. AWS is already seeing early signs of progressive recovery. They will continue to work toward full recovery and will continue to provide updates as they work toward full mitigation. They recommend customers continue to retry failed requests. As recovery progresses, additional requests will succeed. Additional information and updates are available on the AWS Health Dashboard page: https://health.aws.amazon.com/health/status Impact to Clients: Potential issues in EU-WEST-1 Primary Contact: For HSP AWS Accounts, if you are experiencing impaired services, please contact AWS Support. For all other Clients, contact HSP support by opening a ticket via the HealthSuite Support Portal or using one of the numbers below to contact our support line and speak to an engineer. HSP Support is available 24x7x365.

2. identified Jan 28, 2026, 06:51 PM UTC

   Jan 28 10:45 AM PST We continue to work toward fully mitigating the issue that is resulting in elevated latencies for network change propagation delays in the EU-WEST-1 Region. We have a high degree of confidence that our current mitigation efforts will fully mitigate the issue. Our current estimation is that these mitigations will complete within the next 60 to 120 minutes. We recommend customers continue to retry failed requests. We will provide additional information as recovery continues to progress.

3. identified Jan 28, 2026, 07:13 PM UTC

   Update: 18:51 UTC - AWS is seeing significant signs of recovery and continue to work toward full resolution. What’s Happening: We have received word that AWS is currently experiencing a networking issue in eu-west-1. AWS has confirmed elevated latencies for network change propagation in the EU-WEST-1 Region. This causes delays when attempting to connect to newly launched instances using their assigned public IPs, as well as delays in establishing new VPC Peering connections. Other AWS Services are also impacted by this issue and may be impacted by delayed or stuck workflows such as pulling container images. Engineers with AWS were automatically engaged and are actively working on mitigating this issue. AWS is already seeing early signs of progressive recovery. They will continue to work toward full recovery and will continue to provide updates as they work toward full mitigation. They recommend customers continue to retry failed requests. As recovery progresses, additional requests will succeed. There are 22 affected AWS services: AWS Deadline Cloud AWS Elemental AWS Fargate AWS Global Accelerator AWS NAT Gateway AWS WAF Amazon API Gateway Amazon Athena Amazon Cognito Amazon DynamoDB Amazon EMR Serverless Amazon ElastiCache Amazon Elastic Container Registry Amazon Elastic Container Service Amazon Elastic Kubernetes Service Amazon Elastic Load Balancing Amazon Elastic MapReduce Amazon OpenSearch Service Amazon Personalize Amazon Relational Database Service Amazon SageMaker Amazon Simple Storage Service Additional information and updates are available on the AWS Health Dashboard page: https://health.aws.amazon.com/health/status. Impact to Clients: Potential issues in EU-WEST-1 affecting Amazon Elastic Compute Cloud (ECC)

4. resolved Jan 28, 2026, 07:32 PM UTC

   [RESOLVED] Elevated latencies for network change propagation Jan 28 11:22 AM PST Between 7:08 AM and 10:48 AM PST, we experienced elevated latencies for network change propagation in the EU-WEST-1 Region. This was due to a delay in propagation of configuration updates on a sub-system which supports external and cross account connectivity. Customers experienced delays when attempting to connect to newly launched instances using their assigned public IPs, as well as delays in establishing new VPC Peering connections. Other AWS Services were also impacted by this issue and were impacted by delayed or stuck workflows such as pulling container images. Engineers were automatically engaged at 6:29 AM, prior to customer impact beginning. At 7:20 AM, root cause was identified. By 9:20 we began observing early signs of recovery. Our mitigation efforts completed at 10:43 AM and full recovery was observed at 10:48 AM. We recommend customers retry any failed requests. The issue has been resolved and all services are operating normally.

Read the full incident report →

Started Oct 30, 2024, 01:42 PM UTC· resolved Oct 30, 2024, 01:42 PM UTC

1. resolved Oct 30, 2024, 01:42 PM UTC

   The inference server app keeps crashing because "The security token included in the request is invalid"

Read the full incident report →