<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cordice Status</title>
    <link>https://perch.cordice.org/</link>
    <description>Incidents affecting Cordice.</description>
    <language>en</language>
    <atom:link href="https://perch.cordice.org/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Events server stopped accepting connections</title>
      <link>https://perch.cordice.org/incidents/2026-08-11-events-websocket/</link>
      <guid isPermaLink="true">https://perch.cordice.org/incidents/2026-08-11-events-websocket/</guid>
      <pubDate>Tue, 11 Aug 2026 18:42:00 GMT</pubDate>
      <description>Major outage — Recovered 6 days ago</description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p><strong>Major outage</strong> — affecting events</p><p><strong>Investigating</strong> 2026-08-11T18:42:00.000Z — The live connection is refusing new clients. Messages already sent are safe and nothing has been lost, but apps will not receive anything new until this is fixed, and reopening the app will not help.</p><p><strong>Identified</strong> 2026-08-11T19:15:00.000Z — The events service had stopped answering its health path while still holding its port, so the proxy kept handing it connections it would not take. Restarting it restores service; we are looking at why it wedged.</p><p><strong>Resolved</strong> 2026-08-11T20:00:00.000Z — Connections have been accepted normally for the last twenty minutes. Total time affected was 78 minutes.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
