QUIC is now RFC 9000
QUIC version 1 is officially formalized, and QUIC deployments will now move away from using temporary draft versions to the newly minted version 1.
Fastly's edge cloud platform delivers faster, safer, and more scalable sites and apps to customers. Elevate your edge CDN, video delivery, security, and more.
Visit fastly.com → RSS feedOn Hacker News May 2016 – Aug 2025
Networking & Internet 7Systems & Performance 5Infrastructure & DevOps 4Software Engineering 3Tech Industry & Business 2Web & Frontend 1
QUIC version 1 is officially formalized, and QUIC deployments will now move away from using temporary draft versions to the newly minted version 1.
A couple of weeks ago Cloudflare, one of our competitors, claimed that their edge compute platform is roughly three times as fast as Compute@Edge. The false claim is a great example of how statistics can be used to mislead.
HTTP headers are an important way of controlling how caches and browsers process your web content. But many are used incorrectly or pointlessly, which adds overhead at a critical time in the loading of your page, and may not work as you intended.
We're thrilled to be so invested in QUIC, a new transport protocol that is more responsive, secure, and flexible than what the internet uses today. Learn why, straight from our very own Jana Iyengar, one of the editors of the core document.
QUIC, the new internet transport protocol set to replace TCP, was comprehensively built by tech industry leaders over nearly seven years. Go behind the scenes to see how QUIC evolved from a lofty experiment to a standard set to modernize the internet.
This post is the first in a series detailing the evolution of network software at Fastly. We’re unique amongst our peers in that from inception, we’ve always viewed networking as an integral part of our product rather than a cost center. We rarely share what we do with the wider networking community however, in part…
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, why, and what we're doing about it.