<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><link rel="alternate" type="text/html" href="https://status.openpak.org/"/><title>CDN on Openpak Status</title><link>https://status.openpak.org/affected/cdn/</link><description>Incident history</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2026-03-24T23:55:00+00:00</lastBuildDate><updated>2026-03-24T23:55:00+00:00</updated><atom:link href="https://status.openpak.org/affected/cdn/index.xml" rel="self" type="application/rss+xml"/><item><title>[Resolved] appstream2 branch referencing stale commit</title><link>https://status.openpak.org/issues/2026-03-24-appstream2/</link><pubDate>Tue, 24 Mar 2026 23:55:00 +0000</pubDate><guid>https://status.openpak.org/issues/2026-03-24-appstream2/</guid><category>2026-03-25 02:00:00</category><description>&lt;p>A mismatch between the appstream2 branch and delta indexes caused local Flatpak
clients to fail to update appstream data. The issue is resolved now after
regenerating both the branch and the indexes.&lt;/p>
&lt;p>If you are still experiencing issues, please try the steps below to clear the
local copy of the appstream2 branch.
&lt;span class="faded">(01:33 UTC — Mar 25)&lt;/span>
&lt;/p>
&lt;pre tabindex="0">&lt;code># For system-wide installation
sudo ostree --repo=/var/lib/flatpak/repo refs --delete flathub:appstream2/x86_64
# For user installation
ostree --repo=$HOME/.local/share/flatpak/repo refs --delete flathub:appstream2/x86_64
# Update the appstream data
flatpak update --appstream
&lt;/code>&lt;/pre>&lt;p>Additionally, some client experienced timeouts when fetching delta indexes that
were removed from the server. This was caused by the CDN not caching 404
responses, resulting in requests queuing up behind nginx&amp;rsquo;s cache lock. A fix
was deployed to cache 404 responses, allowing clients to gracefully fall back
to full downloads.
&lt;span class="faded">(02:08 UTC — Mar 25)&lt;/span>
&lt;/p></description><content type="html">&lt;p>A mismatch between the appstream2 branch and delta indexes caused local Flatpak
clients to fail to update appstream data. The issue is resolved now after
regenerating both the branch and the indexes.&lt;/p>
&lt;p>If you are still experiencing issues, please try the steps below to clear the
local copy of the appstream2 branch.
&lt;span class="faded">(01:33 UTC — Mar 25)&lt;/span>
&lt;/p>
&lt;pre tabindex="0">&lt;code># For system-wide installation
sudo ostree --repo=/var/lib/flatpak/repo refs --delete flathub:appstream2/x86_64
# For user installation
ostree --repo=$HOME/.local/share/flatpak/repo refs --delete flathub:appstream2/x86_64
# Update the appstream data
flatpak update --appstream
&lt;/code>&lt;/pre>&lt;p>Additionally, some client experienced timeouts when fetching delta indexes that
were removed from the server. This was caused by the CDN not caching 404
responses, resulting in requests queuing up behind nginx&amp;rsquo;s cache lock. A fix
was deployed to cache 404 responses, allowing clients to gracefully fall back
to full downloads.
&lt;span class="faded">(02:08 UTC — Mar 25)&lt;/span>
&lt;/p></content></item><item><title>[Resolved] CDN cache invalidation issue</title><link>https://status.openpak.org/issues/2026-02-13-cdn-cache-2/</link><pubDate>Fri, 13 Feb 2026 05:38:00 +0000</pubDate><guid>https://status.openpak.org/issues/2026-02-13-cdn-cache-2/</guid><category>2026-02-14 07:00:00</category><description>&lt;p>Due to a brief downtime, one of the origin servers missed purging operation and
was serving stale and non-existent index files. As a result Flathub builds
failed while attempting to download dependencies and any general Flatpak
clients experienced hangs or download failures.&lt;/p>
&lt;p>The issue was resolved after the cache was invalidated.
&lt;span class="faded">(07:00 UTC — Feb 14)&lt;/span>
&lt;/p></description><content type="html">&lt;p>Due to a brief downtime, one of the origin servers missed purging operation and
was serving stale and non-existent index files. As a result Flathub builds
failed while attempting to download dependencies and any general Flatpak
clients experienced hangs or download failures.&lt;/p>
&lt;p>The issue was resolved after the cache was invalidated.
&lt;span class="faded">(07:00 UTC — Feb 14)&lt;/span>
&lt;/p></content></item><item><title>[Resolved] CDN cache invalidation issue</title><link>https://status.openpak.org/issues/2026-01-13-cdn-cache/</link><pubDate>Tue, 13 Jan 2026 05:51:00 +0000</pubDate><guid>https://status.openpak.org/issues/2026-01-13-cdn-cache/</guid><category>2026-01-13 06:40:00</category><description>&lt;p>Due to a CDN cache invalidation issue, the CDN served a summary file referencing a non-existent file, causing Flatpak clients to hang or fail with 404 errors.
&lt;span class="faded">(05:51 UTC — Jan 13)&lt;/span>
&lt;/p>
&lt;p>&lt;strong>Resolved:&lt;/strong> The issue was resolved after invalidating the cache again.
&lt;span class="faded">(06:40 UTC — Jan 13)&lt;/span>
&lt;/p></description><content type="html">&lt;p>Due to a CDN cache invalidation issue, the CDN served a summary file referencing a non-existent file, causing Flatpak clients to hang or fail with 404 errors.
&lt;span class="faded">(05:51 UTC — Jan 13)&lt;/span>
&lt;/p>
&lt;p>&lt;strong>Resolved:&lt;/strong> The issue was resolved after invalidating the cache again.
&lt;span class="faded">(06:40 UTC — Jan 13)&lt;/span>
&lt;/p></content></item></channel></rss>