Global archive stagnation? Release files not updated since Feb 24th 14:16 UTC

Ihor Barabash <[email protected]> Wed, 25 Feb 2026 16:45:56 +0200

Newsgroups	gmane.linux.debian.user.mirrors
Message-ID	<AM7PPF61CE32106C10F50D92A91AAA09491E675A@AM7PPF61CE32106.EURP195.PROD.OUTLOOK.COM>

--------------AYIkort0mD0KMdDRCTwNRb5n
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hello Debian Mirror Team and Community,

I am writing to inquire about a possible stagnation in the Debian 
archive updates.

We've observed that the Release files on *ftp.debian.org* (and 
subsequently on our mirror, *mirror.volia.net*) have not been updated 
since *2026-02-24 14:16 UTC*. Our monitoring systems are reporting a 
critical age for the repository, and it appears this is an upstream 
situation rather than a local sync issue.

Specifically, the trixie-updates and several other components seem to be 
frozen at that timestamp.

Is this a known global situation? Has there been a hitch in the dinstall 
process or a temporary freeze on the master side? It might be worth the 
community's attention to ensure the sync propagation is healthy.

Looking forward to any information or updates on this.

*Best regards,
Ihor Barabash*


--------------AYIkort0mD0KMdDRCTwNRb5n
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body>
    <p data-path-to-node="8">Hello Debian Mirror Team and Community,</p>
    <p data-path-to-node="9">I am writing to inquire about a possible
      stagnation in the Debian archive updates.</p>
    <p data-path-to-node="10">We've observed that the Release files on <b>ftp.debian.org</b>
      (and subsequently on our mirror, <b>mirror.volia.net</b>) have
      not been updated since <b>2026-02-24 14:16 UTC</b>. Our
      monitoring systems are reporting a critical age for the
      repository, and it appears this is an upstream situation rather
      than a local sync issue.</p>
    <p data-path-to-node="11">Specifically, the trixie-updates and
      several other components seem to be frozen at that timestamp.</p>
    <p data-path-to-node="12">Is this a known global situation? Has
      there been a hitch in the dinstall process or a temporary freeze
      on the master side? It might be worth the community's attention to
      ensure the sync propagation is healthy.</p>
    <p data-path-to-node="13">Looking forward to any information or
      updates on this.</p>
    <p data-path-to-node="14"><b>Best regards,<br>
        Ihor Barabash</b><br>
      <br>
    </p>
    <p><br>
    </p>
  </body>
</html>

--------------AYIkort0mD0KMdDRCTwNRb5n--