outages.live
Live
Akamai Cloud (Linode)Maintenance ·

Scheduled maintenance for Block storage switches - AP-West (Mumbai)

MaintenanceOfficial update

We will be performing maintenance on our Block Storage switches in Mumbai on Thursday, November 12th at 11: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.

The latest update from Akamai Cloud (Linode).

State

Scheduled

Starts

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Akamai Cloud (Linode)

Scheduled

We will be performing maintenance on our Block Storage switches in Mumbai on Thursday, November 12th at 11: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.

Affected components

4
AP-West (Mumbai)AP-West (Mumbai) Block StorageRegions - AP-West (Mumbai)Block Storage - AP-West (Mumbai) Block Storage

Akamai Cloud (Linode) in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

30

Days with an incident

89

Median duration

5 h 8 min

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

15 days
median 5 h 8 min
90 days agoToday

Other Akamai Cloud (Linode) incidents

All incidents

Akamai Cloud (Linode)·Customer Security Advisory: OpenSSH Password Authentication Bypass Vulnerability

Akamai is aware of the password authentication bypass vulnerability affecting certain Linux systems using musl libc that was recently mitigated by an urgent OpenSSH update . Since Alpine Linux is specifically called out as being affected, we wanted to assure customers that Linode’s Alpine images are not affected by this vulnerability. Linodes using password-less provisioning do not have password authentication enabled by default unless customers change this configuration option in sshd_config after launch, while linodes launched using a password do not have any unlocked user accounts with a password hash set to ‘*’. However, we would like to use this opportunity as a reminder for customers to consider disabling password authentication permanently in favor of more secure mechanisms such as SSH keys or SSH CA certificates.

Resolved

Akamai Cloud (Linode)·Emerging Host Issue

Akamai Cloud (Linode) reports degraded service on Linode.com. Migrations and booting failed for some hosts across all regions. Akamai Cloud (Linode) identified the issue and implemented a fix. The incident is resolved and lasted about 4 hours 24 minutes.

Resolved

Akamai Cloud (Linode)·Connectivity Issue - FR-PAR-2 (Paris 2)

Connectivity does not work for services in the Akamai Cloud (Linode) FR-PAR-2 (Paris 2) data center. Users had intermittent connection timeouts and errors. Akamai Cloud (Linode) reports that the incident is resolved. The incident lasted about 2 hours and 50 minutes.

Resolved

Akamai Cloud (Linode)·Connectivity Issue - IN-MAA and IN-BOM-2

Connectivity does not work for services in the IN-MAA (Chennai) and IN-BOM-2 (Mumbai 2) data centers. Akamai Cloud reports that the incident is resolved. The outage lasted 3 hours and 12 minutes.

Resolved

Akamai Cloud (Linode)·Service Issue - US-Southeast (Atlanta)

Akamai Cloud (Linode) reports a service issue that affects US-Southeast (Atlanta) and the Regions - US-Southeast (Atlanta) component. The problem is resolved. It lasted 2891 minutes.

Resolved

Follow Akamai Cloud (Linode)

Your coding agent knows when Akamai Cloud (Linode) is down, and tells you when a failure is theirs, not yours. You can also get Akamai Cloud (Linode) incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "linode" and tell me if Akamai Cloud (Linode) has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=linode
Slack
/feed subscribe https://outages.live/feed.xml?providers=linode

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane