1. You don't need to use the website to update (and normal users shouldn't **) - Help > About will serve you the most recent version for what you have installed

2. As someone who is very involved in releases, I cannot agree that the website being out of date is a frequent problem - but it does happen a few times a year. Part of what you might be interpreting is that the advisories are sometimes posted prior to the release being ready.

> I've contacted the team several times and was told this was a replication issue with the site or the CDN. The issue still hasn't been fixed.

Yes, this release automation occasionally has glitches. Most times it gets resolved. In the case of 128.6.0, if I remember correctly it would have been exceedingly difficult to resolve, and it was known that creating 128.6.1 would resolve the issue.

I see from your other postings that are doing some form of patch management. In that case, be aware that new versions appearing on the website are also at the mercy of caching. A more reliable means of staying up to date is monitor for changes at https://product-details.mozilla.org/1.0/thunderbird_versions.json and then download the appropriate version from https://ftp.mozilla.org/pub/thunderbird/releases/

Hopefully this answered your question?

There have been consistent issues with the CDN and the website offering the latest release over the last year. That's a fact, I know it because I've experienced it, I don't need gaslighting of what I've actually experienced.

I'm aware of all the other methods of obtaining the latest binary and delivering it. My issues was with the website and it seems to have improved but I'll wait and see.

There has been an ongoing problem with the latest updated binary showing up on the main thunderbird.net for days after it has been released. This is a serious problem because users cannot access patches that keep them safe from security vulnerabilities. I've contacted the team several times and was told this was a replication issue with the site or the CDN. The issue still hasn't been fixed.

CDN operations are entirely on the Mozilla side, so it's unlikely for us (Thunderbird) to hear about such things.

In what country or region are you located? Has Firefox also been affected when you discovered these issues with Thunderbird? And at what email address or website (bug report# or github issue#) have you reported these issues? (names of who responded will also be helpful if you have them, feel free to PM me)