Argon/Xenon rate limits

[Maxime Thiebaut]

Hi All,

The Argon/Xenon logs seem to limit the returned entries to 32 per request. Are there any plans to increase this?

Catching-up Argon/Xenon logs currently requires a significant amount of time whereas Cloudflare's 1024 limit only requires a few days.

At 32 entries per request, 10 requests per second, catching-up Xenon2025h1 (957,944,243 certificates) would already take 34+ days alone without taking the avg 375,724 certs/hr throughput into account. In comparison, 1024 entries per request would take just above 1 day.

Thanks,
Maxime

[Philippe Boneff]

Hi Maxime,

We don't have any plan at the moment to increase this number. We're currently focusing our efforts on https://c2sp.org/static-ct-api, which would make fetching entries from logs much easier and faster.

Note that there are other limitations than the number of entries returned by requests such as server 429, which would also behave differently between various log operators. There's a series of tools on this page allowing you to fetch entries while taking into account these various behaviours. In practice, on average, I think you should be able to request more than 32*10=320 entries per second on Argon/Xenon, and catch-up on the logs in less than 34 days.

Cheers,

Philippe

--
You received this message because you are subscribed to the Google Groups "Certificate Transparency Policy" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ct-policy+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/ct-policy/59507cc0-daf3-4ef1-9d0a-d9a2540a814an%40chromium.org.