4 ms·
Let's Encrypt issues 9M certs per day (https://letsencrypt.org/stats/ https://letsencrypt.org/stats/), and its market share is 50%+ (https://w3techs.com/technol
by gslin 1y ago
Let's Encrypt issues 9M certs per day (https://letsencrypt.org/stats/ https://letsencrypt.org/stats/), and its market share is 50%+ (https://w3techs.com/technologies/overview/ssl_certificate https://w3techs.com/technologies/overview/ssl_certificate), so I assume there are <20M certs issued per day.
If all certs are sent to just one CT log server, and each cert generates ~10KBytes outbound traffic, it's ~200GB/day, or ~20Mbps (full & even traffic), not in the same ballpark (2-3Gbps).
So I guess there are something I don't understnad?
- bo0tzz 1y agoI've been trying to get an understanding of this number myself as well. I'm not quite there yet, but I believe it's talking about read traffic, ie serving clients that are looking at the log, not handling new certificates coming in.
- FiloSottile 1y agoI added a footnote about it. It’s indeed read traffic, so it’s (certificate volume x number of monitors x compression ratio) on average. But then you have to let new monitors catch up, so you need burst. It’s unfortunately an estimate, because right now we see 300 Mbps peaks, but as Tuscolo moves to Usable and more monitors implement Static CT, 5-10x is plausible. It might turn out that 1 Gbps is enough and the P95 is 500 Mbps. Hard to tell right now, so I didn’t want to get people in trouble down the line. Happy to discuss this further with anyone interested in running a log via email or Slack!
- bo0tzz 1y agoThanks, that clarifies a lot!