This page was machine-translated and may differ from the original. View original

Limelight Networks expands global CDN capacity by 39%

Google 우선 소스Published2017.12.22 11:30
Server capacity expanded 175% compared to previous levels, power consumption reduced

Limelight Networks announced that it has expanded the capacity of its global CDN (Content Delivery Network) by 39% (increased to 28 Tbps) to support stable streaming of large-volume content transmitted over networks. Additionally, Limelight increased server capacity by 175% compared to previous levels while reducing power consumption, and added 11 new network points of presence (PoPs) this year.

Limelight added new network points of presence (PoPs) in Brazil, Canada, Kuwait, France, India, Italy, Spain, and the United States, and upgraded more than 20 locations worldwide to meet market demand for CDN services and features. These investments demonstrate Limelight's long-term goal of expanding its CDN in major countries around the world.

While expanding its global network in this manner, Limelight reduced carbon emissions by approximately 1,600 tons this year through proprietary software and network upgrades, and achieved a 10% reduction in power costs.

Dan Carney, Senior Vice President of Operations at Limelight Networks, stated: "Investments in our network and software are translating into expanded service coverage, increased capacity, enhanced network performance, and improved customer service quality. By continuing to invest in our network and innovating our software, we are committed to providing our customers with the best-performing and most reliable solutions for transmitting various types of online content."

Meanwhile, Limelight continues to expand its network capacity in line with the exponential growth trend of online traffic. Limelight stores digital content in cached form across more than 80 network points of presence (PoPs) worldwide. Limelight's dense architecture increases cache hit rates and delivers content to users from the fastest location without having to return to the content origin server.
To request a correction, reply or follow-up report on this article, see how to file a request. Previously published statements are collected in corrections & replies.
김지혜 Reporter