Linode Network Backbone

June 27, 2017 10:35 am

As we outlined in our last network update, our network engineering department has been hard at work revamping our entire Internet-facing network by turning up gobs of capacity and directly peering with hundreds of networks all over the globe. Since then, we have extended our network backbone to all datacenters in North America and Europe. This means any communications between Linode datacenters will never leave our ASN 63949. Having direct private connectivity between our sites takes the volatility of the internet out of the equation.

Customers can trust that their multi-site apps hosted with us will be able to communicate over the fastest and most reliable means possible. Our engineers worked closely with our vendors to pick the shortest fiber paths possible, which in turn gives our customers the lowest latency between locations. Across our current longest path (Fremont DC to Frankfurt DC), we were able to cut the RTT down by over 15ms. We have also seen the inevitable occurrences of internet-related jitter and packet loss disappear.

While delivering direct connectivity between Linode’s public interfaces is great, we do not plan to stop there. Our engineers have spent countless hours building relationships and forging peer agreements with hundreds of content and eyeball networks. Now with an accelerated and fortified network backbone, we can extend the benefits of these relationships that are currently contained in a single datacenter to any datacenter along our backbone. For example, customers in Newark will directly benefit from our robust peering relationships in Europe and vice versa. The less traffic sent through multiple transits hops the better cloud we provide for our customers.

Now that Linode’s North American and European DCs are integrated, we have begun addressing our AsiaPAC network. During a recent trip to Singapore, our network engineers lighted dark fiber to one of the most carrier-dense buildings in Asia, giving us the foundation to extend our backbone there, too.

Linode turns 14!

June 16, 2017 12:31 pm

We’re celebrating our 14th birthday!

We’d like to thank you, our customers, for your business and support. I’d also like to thank our entire staff for their dedication and commitment to you and to each other. We’ve got a great team helping great customers. Shameless plug: we’re hiring!

It’s been a busy year – we’ve kept our heads down working on many efforts. Here are some highlights:

Linode Block Storage service (in beta)

The Linode Block Storage service allows you to create and attach additional storage volumes to your Linode instances. Block Storage Volumes are highly available, fast, and inexpensive – $0.10 per GB (free during the beta).

The Block Storage service is currently in beta, in the Newark region only. We welcome any and all feedback, so if you’re interested in trying it out (it’s free!) or want to learn more, please see the original announcement for details.

New API and Linode Manager (both early access)

The new Linode API (documentation | announcement) is a RESTful, modern implementation for Linode’s services. It will become the foundation of all current and future services.

The new Linode Manager is an open source, in-browser application. Our objectives for the new Manager are simplicity, great UI/UX, a streamlining of many of the existing workflows, and to build this as the platform for our future.

Both the API and the new Manager are still in active development, however you can use it right now. Again, we appreciate all feedback!

API Documentation:
New Linode Manager:

Linode’s Global Network

In continuation of the work mentioned in our last networking post, our network engineering team has been busy building out Linode’s global backbone. We’re building our own transit backbone across the planet. More on that in an upcoming blog post next week.


We’ve expanded our Dallas, TX region with the opening of a second Dallas datacenter. This is a brand new, state of the art facility, and is seamlessly integrated into our Dallas region. There are already thousands of customers in this new facility. More detailed information in an upcoming blog post.

New Office

In addition to all of the hard work our core team at Linode has been working on over the past several months, we’ve also had a team of Linode contractors hard at work on our new office space in Old City Philadelphia. Progress is moving fast and our team is excited about moving into our newly restored digs at the end of this year. Once we’ve moved in, we welcome you to come pay us a visit if you happen to be in the city!

Thank you again for your support over the last 14 years. We are eternally grateful for each and every one of you.


Christopher S. Aker, CEO

High-Memory Instances and $5 Linodes

February 14, 2017 12:21 pm

Happy Valentine’s Day!

While our standard instances offer a balance of RAM, CPU, and storage and are great for general use-cases, some workloads (and budgets) would benefit greatly from specialization. Because of these varying needs we’re announcing our first specialized instance family: high-memory instances and also a new $5 Linode. The Linode lineup grows.

High Memory Instances

High-memory instances are optimized for memory-intensive workloads like high-performance databases, in-memory caching, rendering and data processing. High-memory instances offer a higher ratio of RAM to CPU and storage, start at 16GB of memory and scale up to 200GB, and range from $60 to $960 per month. See the chart below for specifics or visit our simple pricing page.

$5 plan – Linode 1GB

We’re also introducing the Linode 1GB, our lowest priced instance ever at only $5 per month. We believe this will add a great deal of utility to our service.


It’s worth mentioning that Linodes can be easily resized up or down, and even across instance types. Meaning, you can resize your existing Linode up in size, down in size, or even resize a standard instance to become a high-memory instance and vice-versa.


Legacy Xen-based Linodes are not eligible to resize into these new plans. You can easily upgrade your legacy Xen-based Linodes to our KVM platform by following the “Upgrade to KVM” link on the right side of your Linode’s dashboard.

Legacy pre-pay accounts are also not eligible for these new plans. You can easily upgrade your account to hourly billing. Find more information here.

Linode 2GB Storage Increase

And finally, the existing Linode 2GB ($10/mo) plan is receiving a free storage upgrade from 24GiB to 30GiB. While the additional space is applied instantly to your Linode, you will need to either resize your existing disk or create a new disk to use the space.

And finally finally, we’ve also increased the outbound network speed limit on all plans to be at minimum 1000 Mbits. Existing Linodes will need to reboot to pick up the new value, that’s it!

We’re always looking for ways to improve the ease-of-use and utility of Linode and our platform, so please let us know. We hope you find these new plans useful. Stay tuned; in the coming months we’ll be releasing into beta our new Linode Manager, RESTful API, and block storage service.


New Linode Datacenter: Tokyo 2

November 21, 2016 10:00 am

largeWe are proud to announce the opening of our ninth datacenter: Tokyo 2. There has been high demand for additional Linode capacity in this region and we’re excited to open up availability.

Tokyo 2 offers all of the features and services as our other datacenters, at standard Linode pricing. Connectivity into Tokyo 2 features a fine blend of peering and transit providers (with more to come) to ensure the highest possible bandwidth and lowest latencies.

Customers with Linodes in other datacenters (including Tokyo 1) wishing to move Linodes into Tokyo 2 can clone them to the new facility. The cloning method is recommended since you’ll be able to stage your services on their new IP addresses before changing your DNS records. Alternatively, you can open a support ticket and we can configure a migration for you.

For new Linodes, simply choose “Tokyo 2” as the location when creating a Linode.

Network Update: Multihomed, Increased Transit, Peering

November 2, 2016 10:00 am

Linode has completed initial Internet capacity upgrades in all facilities. All of our datacenters are now multihomed with several tier-1 transit providers and the largest peering exchanges in the world. This marks a milestone in Linode’s history: we now manage our own true service provider network, allowing us to deliver robust and reliable connectivity.

To accomplish this, our datacenters have been upgraded with Cisco ASR 9000 series edge routers, allowing us to scale to many terabits of capacity per datacenter. Currently, each datacenter has a few hundred gigabits of transit and peering, with more to come. We’re operating our network under ASN63949.

Why is this a good thing?

  • We are now completely independent to make routing decisions, allowing us to quickly route around trouble on the Internet in real time.
  • We’ve increased IP capacity to each facility by 5 to 10 times over our previous capacity amounts.
  • We have high capacity edge routers and self-lit fiber backhauls in carrier hotels providing many terabits of additional expansion capabilities. Since we are our own backhaul provider, bringing up additional capacity between locations is fast and easy.
  • We can do cool stuff in the future like inter-dc connectivity, per-customer VLANs, and Anycast announcements of some or all of our IP space.

Let’s take a look at the state of each datacenter:


Retrofitted: July 25, 2016
Transit: Telia, NTT, Cogent, Zayo (soon: GTT, Tata)
Peering: Dallas Equinix Internet Exchange

We chose 1950 Stemmons and 2323 Bryan Street, two major regional carrier hotels, as our points of presence in Dallas. Also known as The Infomart, 1950 Stemmons is one of the largest buildings in Dallas, measuring at over 1.5 million square feet. Power and connectivity are plentiful at the Infomart; the building has four diverse power feeds and 100+ carriers redundantly built into the building.


Retrofitted: September 23, 2016
Transit: Telia, Hurricane Electric, Cogent (soon: NTT, GTT, Tata)
Peering: San Jose Equinix Internet Exchange (soon: Any2 Los Angeles)

While there are several good options for points of presence in the Bay Area, we decided on 11 Great Oaks and 55 S Market, two large facilities with great carrier diversity. These are our longest fiber spans, requiring amplification in order to take a trip under the San Francisco Bay.


Retrofitted: September 21, 2016
Transit: Telia, NTT, Cogent, Zayo (soon: GTT, Tata)
Peering: Atlanta Telx Internet Exchange

In Atlanta we chose a single facility, 56 Marietta, to serve as our regional point of presence. This well-known carrier hotel was selected over all the other options in the Atlanta metro area simply because no other facilities could compete with Marietta’s connectivity. To ensure total physical redundancy, our diverse dark fiber enters 56 Marietta through different building entrances and lands in separate meet-me rooms using entirely distinct power systems.


Retrofitted: August 1, 2016
Transit: Telia, NTT, Cogent, Zayo (soon: GTT, Tata)
Peering: NYIIX, DE-CIX New York

In Newark, we chose to light points of presence in 165 Halsey and 111 8th Avenue, both famous carrier hotels in the NJ/NY metro area. We selected 165 Halsey in particular to give us physical diversity from the island of Manhattan. Having our physical footprint spread out over the entire New York metro area makes us much less susceptible to downtime during a catastrophic event like Superstorm Sandy.


Retrofitted: July 11, 2016
Transit: Telia, NTT, Cogent (soon: GTT, Tata, Vodafone, Sparkle)

In London, we chose 8/9 HEX and 14 Coriander Avenue to light points of presence. Because of the stature of these facilities and the more friendly peering climate in Europe, we are able to directly connect with hundreds of major networks over the largest Internet exchanges in Europe. This allows us to route up to 50% of our traffic over peering instead of transit, providing our customers with the shortest paths and lowest possible latencies to many of the largest European networks.


Retrofitted: N/A
Transit: Telstra, PCCW, Tata (soon: NTT)
Peering: Singapore Equinix Internet Exchange

Tier 1 networks in the South Asian transit market are much more siloed than in other parts of the world, making it difficult to provide good connectivity using any single provider. This presented an unforeseen challenge when launching this facility in 2015: for the first time, we needed to be truly multihomed. With this realization, we decided to delay Singapore so that we could install our first pair of Cisco ASR 9000s as edge routers and launch on what would become our global public ASN. The facility we chose for Singapore is well connected, obviating the need to light dark fiber to remote carrier hotels.


Retrofitted: N/A
Transit: Telia, Cogent (soon: GTT, Tata, Vodafone, Sparkle)
Peering: DE-CIX Frankfurt

Building on the experiences learned in Singapore, we now had a blueprint for all future Linode facilities. Choosing a colocation facility now considers how many quality networks are available to us, including in the colo facility itself. The Frankfurt datacenter is extremely well connected and we did not need to light dark fiber into remote carrier hotels.

Tokyo 2

Retrofitted: N/A
Transit: NTT, Tata, PCCW (more to come)
Peering: BBIX

We’re opening a brand new Tokyo facility next month. This will enable customers in the region to take advantage of several recent Linode announcements: KVM hypervisor, our latest plan specs including double the RAM and SSD servers, and mass availability. Stay tuned for the announcement within the next few weeks.

Linux “Dirty Cow” Vulnerability (CVE-2016-5195)

October 21, 2016 10:42 am

A privilege escalation vulnerability being branded as “Dirty Cow” (CVE-2016-5195) was recently discovered and fixed yesterday in the Linux Kernel. It has existed for 11 years, so pretty much every device running Linux is affected (this includes VMs, physical machines, mobile devices, and so on) and, in general, distros from every vendor are affected.

Linode has made available new 4.8.3 based kernels to address the issue – so if you’re running our kernels (as is the default), you should just need to reboot your Linodes to pick up the new kernel.

If you’re running a distribution’s kernel or your own kernel, you’ll need to apply updates on your own.

As always, there are subtleties and potential defenses and configurations which may make this a non-issue for your specific situation, so we’ll leave the assessment up to you – but our general advice is to upgrade your kernels and reboot as soon as possible.

For the curious, here’s the patch from Linus Torvalds.

PayPal Payments

July 26, 2016 11:01 am

paypalWe’re happy to announce our newest feature: Payments via PayPal. You can now add credit to your account by transferring funds from a PayPal account.

While any customer can use PayPal to fund their account, new customers will still need to sign up using a credit card. You can use PayPal from then on.

This is in part because we don’t yet have the ability to automatically transfer funds from PayPal. If you intend on paying only via PayPal, you will need to ensure that you have enough credit on your Linode account to cover your next invoice. Otherwise, our system will attempt to collect any remaining balance from the credit card you have on file.

To start using PayPal just log into your Linode Manager and go to the Account -> Make a Payment tab.


Introducing Fedora 24

June 22, 2016 3:45 pm

Today we are pleased to offer Fedora Server 24 for deployment on your Linode. The Fedora Project aims to provide the latest stable packages and approximately 13 months of support.

What’s New?

Fedora Server 24 installs lighter than previous versions due to the Fedora Project removing some packages they felt were unnecessary for their server build. The Fedora 24 ChangeSet outlines the major library and software updates like GNU Compiler Collection 6, Nodejs 5.10 and Python 3.5.

As always, you can use the stock Linux kernel we provide, or install a kernel of your choice using our kernel installation guide for KVM Linodes. For the full changelogs, see the Fedora 24 release notes.

How do I get Fedora 24?

A fresh disk image of Fedora Server 24 can be deployed directly from the Linode Manager. If you’re using an earlier version of Fedora, you can upgrade to version 24 using the DNF System Upgrade plugin. You’ll find instructions to do this and potential upgrade issues on Fedora’s Wiki.

Linode’s 13th Birthday – Gifts for All!

June 16, 2016 12:28 pm

It was 13 years ago today that Linode opened its doors and earned its first customers. Now, 13 years later, it’s amazing how much we’ve grown. According to a study by CloudHarmony, Linode is the 4th largest cloud provider to the top 10,000 Alexa websites, following only Amazon, Rackspace, and IBM. Not bad. We have helped over half a million customers, launched nearly 12 million Linode servers, and now have more than 100 employees, all while remaining independent and privately owned.

None of this would have been possible without the dedication and engagement of our employees, who care a great deal about you, our customer, and about the work we do. We’ve attracted some of the most passionate, brilliant, and handsome people I’ve ever met (BTW, we’re hiring). So, a big thanks to everyone here at Linode.

We also want to thank you for your business and support all these years. As a token of our gratitude, we’re announcing free RAM upgrades for both new and existing customers. Here’s the breakdown:

Old Plan New Plan Price
Linode 1 GB -> Linode 2 GB $10/mo ($0.015/hr)
Linode 2 GB -> Linode 4 GB $20/mo ($0.03/hr)
Linode 4 GB -> Linode 8 GB $40/mo ($0.06/hr)
Linode 8 GB -> Linode 12 GB $80/mo ($0.12/hr)
Linode 16 GB -> Linode 24 GB $160/mo ($0.24/hr)
Linode 32 GB -> Linode 48 GB $320/mo ($0.48/hr)
Linode 48 GB -> Linode 64 GB $480/mo ($0.72/hr)
Linode 64 GB -> Linode 80 GB $640/mo ($0.96/hr)
Linode 96 GB -> Linode 120 GB $960/mo ($1.44/hr)

View the full plan list

The free upgrade is available immediately. At the top of your Linode’s dashboard you will see the upgrade banner. It should be just the press of a button and a reboot for many of you, however sometimes a migration will be required – which typically just takes a few minutes.

This upgrade is available only for KVM Linodes. Legacy Xen Linodes will have to first upgrade to KVM before being able to take advantage of the RAM upgrade. You can upgrade your Xen Linodes to KVM using the “Upgrade to KVM” link on the lower-right side of your Linode’s dashboard.

Unfortunately, since Tokyo is sold out, the upgrade is not available there. We hope to have our second Tokyo facility online before the end of this year.

In addition to the new facility, our teams are working hard on the new API (in public alpha), the new open source Linode Manager, and the significant improvements to our networking infrastructure including transit, peering, and bandwidth upgrades. We’re also very excited about our future office in Philadelphia – a beautiful neoclassical 110-year-old former bank building right at the heart of N3RD Street. Renovations are underway and we hope to be working out of there in the spring.

We continue to build upon the foundations of a company that is big enough to handle its customers’ needs but small enough to care. We hope we’re accomplishing that. You have our eternal gratitude for your business. Stay tuned for more!


Arch Linux Network Configuration Update

June 13, 2016 5:14 pm

We are happy to announce that we have just pushed a new Arch image, updating it to the 2016.06.01 “release”. This image disables the predictable network interface naming convention using the suggested udev mask, so the default ethernet name is returned to eth0.

If you currently rely on predictable interface naming for any of your Linodes running Arch, make sure to update your configuration scripts before deploying from the newest image. If you want to read more about this configuration or static networking, see the documentation on, or consult our Static IP Configuration guide. Alternately, you can let Network Helper configure your IP addresses statically for you.