Linode Status

On February 13, 2024 at 22:32 UTC, the front page of Linode.com began presenting a 301 error to visitors, preventing access to the site. Our administrators were alerted to this immediately and at 23:12 UTC, partial site access was restored by reloading the web server and purging caches. By 23:30 UTC access to Linode.com was restored and investigation into the cause of this downtime began.

On February 14, 2024 at 22:30 UTC, our administrators determined that a software configuration issue was causing erroneous redirects to occur at login, resulting in a 301 error being displayed to visitors of Linode.com. To address this issue, a CDN delivery rule preventing caching of any 301 responses on the root path was prepared. Testing of this configuration began on February 14, 2024 at 23:06 UTC.

On February 15, 2024 at 17:46 UTC, testing of the configuration changes was complete, and they were deployed at 18:35 UTC. Our administrators then entered a period of monitoring for further issues. On February 18 2024 at 15:28 UTC, monitoring was complete with no further concerns and the status page was updated to Resolved.

Origin logs indicate that the issue was triggered in response to an SSO login (re-authentication). Therefore, SMEs are also testing a plugin configuration change whereby users will always be redirected to the WordPress admin path after login (never to the home page). Testing for this change will occur between February 21-23, with possible production change to be rolled out the week of February 26.