<?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://status.cordice.org/</link>
    <description>Incidents affecting Cordice.</description>
    <language>en</language>
    <atom:link href="https://status.cordice.org/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Cordice unavailable while moving to a new server</title>
      <link>https://status.cordice.org/incidents/2026-10-26-move-to-new-server/</link>
      <guid isPermaLink="true">https://status.cordice.org/incidents/2026-10-26-move-to-new-server/</guid>
      <pubDate>Mon, 26 Oct 2026 09:00:00 GMT</pubDate>
      <description>Major outage — Recovered 2 hours ago</description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p><strong>Major outage</strong> — affecting web-client, api, events, voice, file-service, mail</p><p><strong>Investigating</strong> 2026-10-26T09:00:00.000Z — The server Cordice ran on stopped answering. The apps, sign-in, messages and calls are unavailable. The website and the developer documentation are not affected.</p><p><strong>Identified</strong> 2026-11-10T12:00:00.000Z — The old server is not coming back. Cordice is moving to a new server of its own in Uzbekistan, with user files in encrypted storage and calls on a dedicated call service.</p><p><strong>Monitoring</strong> 2026-11-11T14:55:00.000Z — Cordice is running on the new server. The apps, sign-in by email, files and calls work again. Accounts start fresh: data from the old server was not carried over.</p><p><strong>Resolved</strong> 2026-11-11T14:55:00.000Z — Every component is checked again every five minutes, each by the server&apos;s own test of the service behind it.</p>]]></content:encoded>
    </item>
    <item>
      <title>Events server stopped accepting connections</title>
      <link>https://status.cordice.org/incidents/2026-08-11-events-websocket/</link>
      <guid isPermaLink="true">https://status.cordice.org/incidents/2026-08-11-events-websocket/</guid>
      <pubDate>Tue, 11 Aug 2026 18:42:00 GMT</pubDate>
      <description>Major outage — Recovered 2 months 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>
