Scheduled maintenance for Block storage switches - CA-Central (Toronto)
Scheduled Maintenance
Report for Linode
Postmortem
On August 4, 2026 between 03:00 and 07:00 UTC, scheduled maintenance on a rack network switch was executed as planned. The post-change validation by SMEs revealed an unexpected degradation in the Toronto Block Storage cluster that lasted between approximately 04:00 and 08:00 UTC.
Network communication drops during the switches maintenance activity caused storage cluster services to go offline, leading to a spike in system request delays. Immediate SME intervention stabilized the cluster: restarted all offline services, and cleared the request backlog.
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.
Completed
All Linode boot failures have now been resolved and the issue affecting the Block Storage servers has also been resolved.
Update
Scheduled maintenance is currently in progress. Customers might be seeing linode boot failures where block storage volumes are attached. New volumes are also being seen stuck in creating state. We're actively working on getting these issues fixed. In case, a critical linode is not able to boot, please try detaching any block storage volume and rebooting the linode as a workaround.
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Scheduled
We will be performing maintenance on our Block Storage switches in Toronto on Tuesday, August 4th at 03:00 UTC for a duration of 4 hours. Because of our redundant switching infrastructure, we do not expect any downtime during this maintenance. However, a brief period of packet loss or increased latency may be observed.
This scheduled maintenance affected: Regions (CA-Central (Toronto)) and Block Storage (CA-Central (Toronto) Block Storage).