Blog

The legacy WAF isn’t ubiquitous because it’s the perfect technology. Its success comes down to being mandated, despite four ways it often fails.

While some bots are benign search engine crawlers or website health monitors, others are on the prowl with nefarious intent, looking to execute account takeovers and compromise APIs. In this…

We experienced a global outage due to an undiscovered software bug that surfaced on June 8 when it was triggered by a valid customer configuration change. Here's a rundown of what happened…

Alongside the Bytecode Alliance, Fastly’s WebAssembly team recently led a rigorous security assessment of Cranelift, an open-source, next-generation code generator for use in WebAssembly to…

Building protocols in a way that anticipates future change in order to prevent ossification is critical. Because it’s impossible to upgrade everyone on the internet at the same time; it…

QUIC version 1 is officially formalized, and QUIC deployments will now move away from using temporary draft versions to the newly minted version 1.

As part of May’s Asian American and Pacific Islander (AAPI) Heritage Month, we hosted a panel of Asian leaders from tech organizations that reflected on ways their cultural backgrounds…

Authentication is one of the most obvious uses for edge computing. Understanding who your users are as early and as close as possible to their location yields powerful customizations and…

As Kubernetes has become widespread for container orchestration needs, it’s natural for security questions to arise. Here are answers to the Kubernetes questions we hear most often.

We recently discovered a compiler bug in part of the WebAssembly compiler that we use for Compute@Edge, that could have allowed a WebAssembly module to access memory outside of its sandboxed…

Online payments giant PayPal uses Fastly’s edge platform to deliver a more secure, faster, and more reliable user experience at a time when digital payments are surging.

Following the DRY principle isn’t just for engineers. It also cuts the time it takes to make updates in multiple places and reduces errors for our documentation team.