<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.satcat.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.satcat.com"/>
  <link rel="self" type="application/atom+xml" href="https://status.satcat.com/history.atom"/>
  <title>Satcat Status - Incident history</title>
  <updated>2026-04-09T20:53:10.538+00:00</updated>
  <author>
    <name>Satcat</name>
  </author>
  
<entry>
  <id>tag:status.satcat.com,2005:Incident/cmnryev1n03iop6bisf8agiwa</id>
  <published>2026-04-09T20:53:10.538+00:00</published>
  <updated>2026-04-09T20:53:10.538+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.satcat.com/incident/cmnryev1n03iop6bisf8agiwa"/>
  <title>Satcat Control Center Interruption</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 19 minutes</p>
    <p><strong>Affected Components:</strong> Satcat.com</p>
    <p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>20:53:10</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have received reports that some user are experiencing issues loading the Control Center on Satcat. Our team is investigating the issue..</p>
<p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>21:12:38</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. Thank you for your patience!.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.satcat.com,2005:Incident/cmmjns1yw001ofsyvjdq41mqm</id>
  <published>2026-03-09T20:53:40.150+00:00</published>
  <updated>2026-03-09T20:58:33.212+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.satcat.com/incident/cmmjns1yw001ofsyvjdq41mqm"/>
  <title>Satcat service interruption</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 minutes</p>
    <p><strong>Affected Components:</strong> Satcat.com, Satcat API</p>
    <p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>20:58:33</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>20:53:40</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have identified that Satcat services Satcat.com, Satcat API are experiencing a significant service interruption. We will continue to monitor the issue and provide updates..</p>
<p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>21:07:35</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident involving Satcat services Satcat.com, Satcat API is now resolved. Thank you for your patience as our team addressed this issue..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.satcat.com,2005:Incident/cmm0qv1jo00prrdjpzyj2ukle</id>
  <published>2026-02-24T14:00:04.918+00:00</published>
  <updated>2026-02-24T14:00:04.918+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.satcat.com/incident/cmm0qv1jo00prrdjpzyj2ukle"/>
  <title>Increased CDM Ingest Latency</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 13 minutes</p>
    <p><strong>Affected Components:</strong> Third-Party CDM Ingestion, Satcat.com, CDM Notifications</p>
    <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>14:00:04</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified an issue causing increased ingestion latency for CDM data from space-track.org. We have identified the root cause of the issue and are working to deploy a fix..</p>
<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>15:41:17</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and CDM ingestion is now functioning normally. We will continue to monitor to ensure the delayed data is ingested as soon as possible.</p>
<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>16:13:19</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.satcat.com,2005:Incident/cmlk3vq9200861wxzgvw83mqu</id>
  <published>2026-02-12T22:03:00.000+00:00</published>
  <updated>2026-02-13T00:54:44.584+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.satcat.com/incident/cmlk3vq9200861wxzgvw83mqu"/>
  <title>Outage caused by upstream service provider</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> CDM Notifications, Satcat API, Satcat.com, On-Demand Screening, Third-Party CDM Ingestion</p>
    <p><small>Feb <var data-var='date'> 13</var>, <var data-var='time'>00:54:44</var> GMT+0</small><br /><strong>Resolved</strong> -
  The upstream service provider resolved the issue and service was restored on Satcat. CDM data from external service providers (e.g. space-track.org) is being backfilled and accompanying notifications will be sent as data becomes available..</p>
<p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>22:03:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are currently experiencing a service disruption affecting our notifications, user interface (UI), and API/SDK availability.

An outage of an upstream service provider is causing this issue. Our team is actively monitoring the situation and working to restore full functionality as soon as possible..</p>

        ]]>
  </content>
</entry>

</feed>