As part of our filing for Chapter 11 bankruptcy relief, Akamai has acquired select assets from Edgio, including certain customer contracts from our content delivery, applications, and security businesses, but not including Uplynk. We encourage any active Edgio delivery, applications, or security customers that are not already engaged with Akamai to migrate their services, to contact their local Akamai office or support@edg.io as soon as possible to help avoid service interruptions. Service will end on January 15, 2025.


Any Edgio Uplynk customers can reach out to support@uplynk.com for any questions or concerns.

Edgio
Edgio Console

Cache Request Flow

Edgio can cache the response provided by an origin server or the Edgio cloud on either an edge POP or an Origin Shield POP. The following diagrams demonstrate how we determine whether a response is served from cache for each of these components.

Origin Server

Once the asset has been cached on a POP, all future requests from the region served by that POP will be served directly from that POP while the cached content’s TTL has not expired. Once the TTL has expired, an edge server from that POP may revalidate the asset with either an Origin Shield POP or the origin server. The request flow for an origin configuration on which Origin Shield has not been enabled is illustrated below.

Origin Shield

If Origin Shield has been enabled on your origin, then the edge server may revalidate with an Origin Shield server. If the TTL for the asset cached on the Origin Shield server has not expired, then the edge server will use the Age header to extend its cached asset’s TTL.

Edgio Cloud

Edgio routes Cloud Functions and Edgio Sites requests similar to traffic sent to your origin servers. However, cache misses are forwarded to a cloud load balancer which distributes requests to a cloud worker.