<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Feedoptimise Systems Status — Incident Feed</title>
  <id>https://status.feedoptimise.com/</id>
  <link rel="alternate" href="https://status.feedoptimise.com/" />
  <link rel="self" type="application/atom+xml" href="https://status.feedoptimise.com/rss.xml" />
  <updated>2026-04-15T15:00:00Z</updated>

  <author>
    <name>Feedoptimise</name>
  </author>

  <entry>
    <title>SFTP server — brief interruption during routine update</title>
    <id>https://status.feedoptimise.com/#incident-sftp-server-2026-04-15</id>
    <link rel="alternate" href="https://status.feedoptimise.com/" />
    <published>2026-04-15T14:15:00Z</published>
    <updated>2026-04-15T15:00:00Z</updated>
    <category term="outage" label="Outage" />
    <category term="affected_system" label="sftp.server" />
    <summary type="text">SFTP server was temporarily unavailable, causing connection refused errors for clients attempting to upload files.</summary>
    <content type="html"><![CDATA[
      <p><strong>Label:</strong> SFTP server briefly unavailable</p>
      <p><strong>Provider:</strong> Feedoptimise</p>
      <p><strong>Duration:</strong> ~45 minutes (14:15–15:00 UTC)</p>
      <p><strong>Affected systems:</strong> sftp.server</p>
      <p><strong>Cause:</strong> A routine SSH component update caused a brief unexpected service interruption.</p>
      <p><strong>Notes:</strong> The update was expected to be seamless. Service was restored promptly and file uploads resumed normally.</p>
    ]]></content>
  </entry>

  <entry>
    <title>Cloudflare disruption (minor impact) — configuration change regression</title>
    <id>https://status.feedoptimise.com/#incident-cloudflare-2025-12-05</id>
    <link rel="alternate" href="https://status.feedoptimise.com/" />
    <published>2025-12-05T00:00:00Z</published>
    <updated>2025-12-05T00:25:00Z</updated>
    <category term="cloudflare" label="Cloudflare" />
    <category term="degradation" label="Degradation" />
    <category term="affected_system" label="api" />
    <category term="affected_system" label="app" />
    <category term="affected_system" label="image-editor" />
    <category term="affected_system" label="homepage" />
    <category term="affected_system" label="css" />
    <summary type="text">Cloudflare disruption caused minor slowdowns for some requests.</summary>
    <content type="html"><![CDATA[
      <p><strong>Label:</strong> Cloudflare disruption</p>
      <p><strong>Provider:</strong> Cloudflare</p>
      <p><strong>Duration:</strong> Peak disruption ~25 minutes; residual issues for a couple of hours.</p>
      <p><strong>Affected systems:</strong> api, app, image-editor, homepage, css</p>
      <p><strong>Cause:</strong> A Cloudflare configuration change intended to mitigate a vulnerability in React Server Components accidentally triggered internal system errors.</p>
      <p><strong>Notes:</strong> Impact on our side was limited (minor slowdown). Services stabilised as Cloudflare mitigations rolled out.</p>
    ]]></content>
  </entry>

  <entry>
    <title>Cloudflare disruption (minor impact) — configuration change regression</title>
    <id>https://status.feedoptimise.com/#incident-cloudflare-feeds-export-2025-12-05</id>
    <link rel="alternate" href="https://status.feedoptimise.com/" />
    <published>2025-12-05T00:00:00Z</published>
    <updated>2025-12-05T00:25:00Z</updated>
    <category term="cloudflare" label="Cloudflare" />
    <category term="degradation" label="Degradation" />
    <category term="affected_system" label="feeds.export" />
    <summary type="text">Cloudflare disruption caused minor slowdowns for some requests.</summary>
    <content type="html"><![CDATA[
      <p><strong>Label:</strong> Cloudflare disruption</p>
      <p><strong>Provider:</strong> Cloudflare</p>
      <p><strong>Duration:</strong> Peak disruption ~25 minutes; residual issues for a couple of hours.</p>
      <p><strong>Affected systems:</strong> feeds.export</p>
      <p><strong>Cause:</strong> A Cloudflare configuration change intended to mitigate a vulnerability in React Server Components accidentally triggered internal system errors.</p>
      <p><strong>Notes:</strong> Impact on our side was limited (minor slowdown) and affacted only feeds exposed over URL. Services stabilised as Cloudflare mitigations rolled out.</p>
    ]]></content>
  </entry>

  <entry>
    <title>Cloudflare Bot Management latent bug causing widespread outage</title>
    <id>https://status.feedoptimise.com/#incident-cloudflare-2025-11-18</id>
    <link rel="alternate" href="https://status.feedoptimise.com/" />
    <published>2025-11-18T11:20:00Z</published>
    <updated>2025-11-18T17:20:00Z</updated>
    <category term="cloudflare" label="Cloudflare" />
    <category term="outage" label="Outage" />
    <category term="affected_system" label="api" />
    <category term="affected_system" label="app" />
    <category term="affected_system" label="image-editor" />
    <category term="affected_system" label="homepage" />
    <category term="affected_system" label="css" />
    <summary type="text">Cloudflare Bot Management failure disrupted traffic routing globally.</summary>
    <content type="html"><![CDATA[
      <p><strong>Label:</strong> Cloudflare outage</p>
      <p><strong>Provider:</strong> Cloudflare</p>
      <p><strong>Duration:</strong> Cloudflare failures ~3h (11:20–14:30 UTC); full restoration ~6h.</p>
      <p><strong>Affected systems:</strong> api, app, image-editor, homepage, css</p>
      <p><strong>Cause:</strong> A latent bug in Cloudflare Bot Management: a database permission change caused a configuration file to grow too large, crashing core traffic-routing software.</p>
      <p><strong>Notes:</strong> On our side impact lasted ~10 minutes — we switched away from Cloudflare and routed traffic directly.</p>
    ]]></content>
  </entry>

  <entry>
    <title>Cloudflare Bot Management latent bug causing widespread outage</title>
    <id>https://status.feedoptimise.com/#incident-cloudflare-feeds-export-2025-11-18</id>
    <link rel="alternate" href="https://status.feedoptimise.com/" />
    <published>2025-11-18T11:20:00Z</published>
    <updated>2025-11-18T17:20:00Z</updated>
    <category term="cloudflare" label="Cloudflare" />
    <category term="outage" label="Outage" />
    <category term="affected_system" label="feeds.export" />
    <summary type="text">Cloudflare Bot Management failure disrupted traffic routing globally.</summary>
    <content type="html"><![CDATA[
      <p><strong>Label:</strong> Cloudflare outage</p>
      <p><strong>Provider:</strong> Cloudflare</p>
      <p><strong>Duration:</strong> Cloudflare failures ~3h (11:20–14:30 UTC); full restoration ~6h.</p>
      <p><strong>Affected systems:</strong> feeds.export</p>
      <p><strong>Cause:</strong> A latent bug in Cloudflare Bot Management: a database permission change caused a configuration file to grow too large, crashing core traffic-routing software.</p>
      <p><strong>Notes:</strong> On our side impact lasted ~10 minutes and affacted only feeds exposed over URL — we switched away from Cloudflare and routed traffic directly.</p>
    ]]></content>
  </entry>
</feed>
