Fastly is one of the major CDN vendors globally. As a regular consumer you wouldn’t be aware of their service, until a failure hits. Today the service faced a configuration issue, that apparently hit global pages like NYTimes and Bloomberg, but also Amazon, Reddit and Twitter, as reported in multiple sources. The issue is reported resolved by the vendor as of this writing. Details on their status page:
Fastly’s Status Page – Global CDN Disruption.
While a lot of people debate DNS-over-https (and it’s dependencies), IETF has a specification for DNS-over-QUIC on it’s standards track.
This document describes the use of QUIC to provide transport privacy for DNS. The encryption provided by QUIC has similar properties to that provided by TLS, while QUIC transport eliminates the head-of-line blocking issues inherent with TCP and provides more efficient error corrections than UDP. DNS over QUIC (DNS/QUIC) has privacy properties similar to DNS over TLS specified in RFC7858, and performance similar to classic DNS over UDP.
Source: Specification of DNS over Dedicated QUIC Connections
Already on Friday, Fastly, one of the more prominent representatives of the Website acceleration technology business, went public. Despite two days old, still worth mentioning. The San Francisco based company can be found under the label NASDAQ: FSLY. Measured by the initially offered price of 16$/share, the first day of trading close at $24.20 can be considered a successful IPO.
Today, we listed on the New York Stock Exchange, marking our first day of trading as a public company.
Quote from the article.
Source: Fastly’s Initial Public Commit
Crunchbase has a First Look At The Fastly IPO Filing
— news.crunchbase.com/news/first-look-at-the-fastly-ipo-filing/