<?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.packit.dev"/>
    <title>Fedora CI on Packit Service Status</title>
    <link>https://status.packit.dev/affected/fedora-ci/</link>
    <description>Incident history</description>
    <generator>github.com/cstate</generator>
    <language>en</language>
    
    <lastBuildDate>2026-08-12T00:00:00+02:00</lastBuildDate>
    <updated>2026-08-12T00:00:00+02:00</updated>
    
    
    
      <atom:link href="https://status.packit.dev/affected/fedora-ci/index.xml" rel="self" type="application/rss+xml" />
    
    
      <item>
        <title>No pull-request statuses from Packit Fedora CI</title>
        <link>https://status.packit.dev/issues/2026-08-12-fedora-ci-403-forbidden/</link>
        <pubDate>Wed, 12 Aug 2026 00:00:00 +0200</pubDate>
        <guid>https://status.packit.dev/issues/2026-08-12-fedora-ci-403-forbidden/</guid>
        <category></category>
        <description>Packit is getting 403 Forbidden errors from src.fedoraproject.org API when attempting to update check statuses. As a result, there are no Fedora CI statuses on pull requests even though the jobs are running and you can find them at https://dashboard.packit.dev/jobs/koji and https://dashboard.packit.dev/jobs/testing-farm.
We are currently investigating this issue with the Fedora infrastructure team.</description>
        <content type="html">&lt;p&gt;Packit is getting &lt;code&gt;403 Forbidden&lt;/code&gt; errors from src.fedoraproject.org API when attempting to update check statuses. As a result, there are no Fedora CI statuses on pull requests even though the jobs are running and you can find them at &lt;a href=&#34;https://dashboard.packit.dev/jobs/koji&#34;&gt;https://dashboard.packit.dev/jobs/koji&lt;/a&gt; and &lt;a href=&#34;https://dashboard.packit.dev/jobs/testing-farm&#34;&gt;https://dashboard.packit.dev/jobs/testing-farm&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We are currently investigating this issue with the Fedora infrastructure team.&lt;/p&gt;
</content>
      </item>
    
  </channel>
</rss>
