Linode Status

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Resolved: We have not observed any further issues related to this and will now consider the situation resolved. Please open a Support ticket if you have any questions or concerns.

Monitoring: After investigation, we have confirmed that the connectivity issues in these locations were due to a problem outside of our network with an upstream provider. Connectivity has been restored, and we are monitoring for any subsequent problems.

Investigating: Our team is investigating an emerging service issue affecting connectivity in EU-West(London) and EU-Central (Frankfurt). We will share additional updates as we have more information.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Resolved: We have not observed any further issues related to this and will now consider the situation resolved. Please open a Support ticket if you have any questions or concerns.

Monitoring: After investigation, we have confirmed that the connectivity issues in these locations were due to a problem outside of our network with an upstream provider. Connectivity has been restored, and we are monitoring for any subsequent problems.

Investigating: Our team is investigating an emerging service issue affecting connectivity in EU-West(London) and EU-Central (Frankfurt). We will share additional updates as we have more information.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Monitoring: At this time we have been able to correct the issues affecting connectivity in our AP-Northeast-2 (Tokyo 2) and JP-TYO-3 (Tokyo 3) data centers. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.

Investigating: Our subject matter experts are continuing to investigate this issue. The next update will be provided as we make progress.

Investigating: Our team is investigating an emerging service issue affecting connectivity to Compute Instances in our Tokyo 2 data center. We will share additional updates as we have more information.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Identified: The issue has been identified and a fix is being implemented.

Investigating: Our team is investigating an issue affecting the Object Storage service in our LAX location. During this time, users may experience connection timeouts and errors with this service.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Monitoring: At this time we have been able to correct the issues affecting connectivity in our AP-Northeast-2 (Tokyo 2) and JP-TYO-3 (Tokyo 3) data centers. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.

Investigating: Our subject matter experts are continuing to investigate this issue. The next update will be provided as we make progress.

Investigating: Our team is investigating an emerging service issue affecting connectivity to Compute Instances in our Tokyo 2 data center. We will share additional updates as we have more information.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.

Postmortem: Starting around 20:29 UTC on May 5, 2025, Compute customers were unable to boot servers utilizing Red Hat Enterprise Linux (RHEL)-based distributions (Alma Linux, Rocky, CentOS, etc).

Investigation into the issue revealed that this started following the rollout of the new GRUB2 image (software release). The release was intended to support the latest version of Fedora and to fix compatibility issues with newer RHEL-based distributions. However, a software defect inadvertently broke compatibility with older RHEL-based distributions. The image failed to boot and was sitting at the GRUB prompt following this update. 

Upon discovering the root cause of this situation, we rolled back this release. This action was completed and the immediate impact was mitigated at 02:56 UTC on May 6, 2025. Customers running a Linode-supplied kernel were not impacted by this incident, regardless of distribution. Our teams are continuing to investigate this event and will take appropriate actions to prevent any recurrence. 

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: The issue started at 20:29 UTC on May 5, 2025. The investigation revealed that the issue started following the rollout of the software release to support the latest version of Fedora. We rolled back the release to mitigate the impact. We can confirm that the issue is now mitigated as of 02:56 UTC on May 6, 2025 and no longer occurring. We apologize for the impact and thank you for your patience and continued support. Our subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Investigating: Our subject matter experts are actively investigating this issue. We will provide the next update as we make progress.

Investigating: The current workaround for the issue is booting your Linode with the Latest 64-bit kernel. You can change the kernel your Linode is using to boot by following the instructions here: https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance

Investigating: Our team is investigating a service issue affecting the boot process of Red Hat Enterprise Linux (RHEL)-based distributions. Systems running non-64-bit kernels may fail to boot, while distributions using the 64-bit kernel remain unaffected.