Rate Limiting Issues with DigiCert CT Logs
48 views
Skip to first unread message
Michel Le Bihan
Oct 22, 2025, 3:31:22 PM (14 days ago) Oct 22
to Certificate Transparency Policy
Hi all,
I'm monitoring CT logs to inspect newly issued certificates and running into issues with 429 errors on DigiCert logs.
Their rate limit appears to be only 0.15-0.18 req/s. Meanwhile, their https://wyvern.ct.digicert.com/2026h1/ log is growing by approximately 2,700 entries per minute (~44.56/s). Since each request returns at most 256 entries, I'd need roughly 0.174 req/s just to keep up in the ideal case. This margin is extremely tight, and my monitor occasionally falls behind. Once that happens, it becomes impossible to catch up given the rate limit.
Additionally, they don't set a `Retry-After` header, so I'm forced to heuristically guess at retry timing, which is suboptimal.
Has anyone else experienced similar issues or found workarounds for monitoring high-volume DigiCert logs?
Best regards,
Michel Le Bihan
I'm monitoring CT logs to inspect newly issued certificates and running into issues with 429 errors on DigiCert logs.
Their rate limit appears to be only 0.15-0.18 req/s. Meanwhile, their https://wyvern.ct.digicert.com/2026h1/ log is growing by approximately 2,700 entries per minute (~44.56/s). Since each request returns at most 256 entries, I'd need roughly 0.174 req/s just to keep up in the ideal case. This margin is extremely tight, and my monitor occasionally falls behind. Once that happens, it becomes impossible to catch up given the rate limit.
Additionally, they don't set a `Retry-After` header, so I'm forced to heuristically guess at retry timing, which is suboptimal.
Has anyone else experienced similar issues or found workarounds for monitoring high-volume DigiCert logs?
Best regards,
Michel Le Bihan
Reply all
Reply to author
Forward
0 new messages