Linode Status

Current Status
Managed Database : Hostname display missing for Managed Database clusters
Incident Report for Linode
Postmortem

On October 29, 2024, at 11:44 UTC, we discovered an issue in the Cloud Manager where hostnames for Managed Database clusters were not displaying correctly. This issue was limited to the Cloud Manager web interface, while hostnames remained fully accessible through our API. 

The issue stemmed from a recent change made in preparation for a future feature update, which involved adjustments to the interface layout and the creation of two distinct components: an updated component and the original component. The original component contained a bug where a necessary validation check was omitted. As a result, the existing code attempted to read from the peers property instead of accessing the hosts property, leading to the display issue for hostnames.

We identified the root cause and developed a fix to restore the missing hostnames. By 17:46 UTC, the solution was implemented, and we closely monitored it to ensure full functionality was restored. At 19:59 UTC, we confirmed the issue was resolved, with no impact on data integrity or connectivity during the incident.

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.

Posted Nov 15, 2024 - 15:12 UTC

Resolved
This incident has been resolved.
Posted Oct 29, 2024 - 19:59 UTC
Monitoring
A fix has been implemented and we are monitoring the results.
Posted Oct 29, 2024 - 17:46 UTC
Identified
Display Issue has been identified and fix is in progress, this impacts the display only, Hostname is available through the API.
Posted Oct 29, 2024 - 15:45 UTC
Investigating
Display Issue has been identified and fix is in progress, this impacts the display only, Hostname is available through the API.
Posted Oct 29, 2024 - 15:28 UTC
This incident affected: Managed Databases.