<?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-09-27T16:15:56.959+00:00</updated>
  <author>
    <name>Satcat</name>
  </author>
  
<entry>
  <id>tag:status.satcat.com,2005:Incident/cmuk0t0tj07lt0wlcvo0kgtud</id>
  <published>2026-09-27T16:15:56.959+00:00</published>
  <updated>2026-09-27T16:15:56.959+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.satcat.com/incident/cmuk0t0tj07lt0wlcvo0kgtud"/>
  <title>18th SDS SP Ephemeris Catalog Partially Outdated</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 3 hours and 49 minutes</p>
    <p><strong>Affected Components:</strong> On-Demand Screening</p>
    <p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>16:15:56</var> GMT+0</small><br /><strong>Investigating</strong> -
  The SP Ephemeris catalog published by 18th SDS for 2026-09-27 has a high number of outdated ephemerides, which has caused time coverage issues for screenings for some Satcat Screener users. We are in contact with the Space-track administrators about the issue. This issue does not impact the O/O Ephemeris Repository catalog. If you have any questions about screening while this issue is in effect, please contact support@kayhan.space..</p>
<p><small>Sep <var data-var='date'> 28</var>, <var data-var='time'>16:20:33</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The 2026-09-28 SP ephemeris catalog has been published by Space-track and ingested into Satcat. The new catalog has an improved rate of current ephemerides, but around 40% of the catalog has still not been updated by Space-track. We have confirmed that the Space-track administrators are aware of the issue and are actively investigating..</p>
<p><small>Sep <var data-var='date'> 28</var>, <var data-var='time'>20:04:30</var> GMT+0</small><br /><strong>Resolved</strong> -
  Space-track has issued an updated catalog for 09-28 which is fully up-to-date and has been ingested into Satcat successfully. This incident is now resolved. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.satcat.com,2005:Incident/cmu48e5by038a13nkno4tc87s</id>
  <published>2026-09-16T15:04:01.453+00:00</published>
  <updated>2026-09-16T15:04:01.453+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.satcat.com/incident/cmu48e5by038a13nkno4tc87s"/>
  <title>Satcat experiencing service degradation</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> Third-Party CDM Ingestion, CDM Notifications, Satcat API, On-Demand Screening, Satcat.com</p>
    <p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>15:04:01</var> GMT+0</small><br /><strong>Investigating</strong> -
  Some users are currently experiencing issues connecting to Satcat. We are investigating the problem and working to restore access as quickly as possible..</p>
<p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>15:15:34</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have rolled out an infrastructure change to mitigate the issue and are observing recovery of system performance. We are continuing to monitor the system..</p>
<p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>15:33:43</var> GMT+0</small><br /><strong>Resolved</strong> -
  We are now observing nominal performance of the system. We will continue to monitor for any further interruptions..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.satcat.com,2005:Incident/cmsds5kvb03tk0kmrgpqumjdl</id>
  <published>2026-08-03T22:07:44.957+00:00</published>
  <updated>2026-08-03T22:07:44.957+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.satcat.com/incident/cmsds5kvb03tk0kmrgpqumjdl"/>
  <title>Satcat API Performance Degredation</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> Satcat API, On-Demand Screening</p>
    <p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>22:07:44</var> GMT+0</small><br /><strong>Identified</strong> -
  We are investigating reports of degraded performance of the Satcat API. We have identified the underlying issue and our team is working to deploy a hotfix..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>22:18:10</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have implemented a fix and are observing a recovery in API error rates. Thank you for your patience..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.satcat.com,2005:Incident/cmrqi9ljy058s0zn0druvcf6f</id>
  <published>2026-07-18T15:12:14.420+00:00</published>
  <updated>2026-07-18T15:12:14.420+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.satcat.com/incident/cmrqi9ljy058s0zn0druvcf6f"/>
  <title>Satcat.com Disruption</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 39 minutes</p>
    <p><strong>Affected Components:</strong> Satcat.com, Third-Party CDM Ingestion, CDM Notifications, Satcat API, On-Demand Screening</p>
    <p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>15:12:14</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified a disruption to [Satcat.com](http://Satcat.com). A fix is being put in place. We will update you soon.</p>
<p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>15:24:34</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>15:21:41</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>15:51:08</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.satcat.com,2005:Incident/cmr5712oi00010kn92vi4epvo</id>
  <published>2026-07-03T17:14:31.049+00:00</published>
  <updated>2026-07-03T17:14:31.049+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.satcat.com/incident/cmr5712oi00010kn92vi4epvo"/>
  <title>Space-track CDM Interruption</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 7 minutes</p>
    <p><strong>Affected Components:</strong> Third-Party CDM Ingestion</p>
    <p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>17:14:31</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are aware of an apparent interruption of service on [space-track.org](http://space-track.org) which is not publishing updated CDM data. We are in contact with the space-track team and will continue to monitor for any updates..</p>
<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>18:43:49</var> GMT+0</small><br /><strong>Identified</strong> -
  Space-Track&#039;s CDM feed is down with no ETA available. We have temporarily upgraded all Essentials accounts to Pro and are automatically screening your ephemeris against the full catalog. We recommend all operators upload your latest ephemerides and screen maneuver plans to maintain spaceflight safety..</p>
<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>23:21:45</var> GMT+0</small><br /><strong>Resolved</strong> -
  We are seeing CDM data flowing from [space-track.org](http://space-track.org) again within the past hour. We will continue to monitor for any further interruptions..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.satcat.com,2005:Incident/cmqsl77od02pu2iotv2pxju1g</id>
  <published>2026-06-24T21:30:11.845+00:00</published>
  <updated>2026-06-24T22:00:49.191+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.satcat.com/incident/cmqsl77od02pu2iotv2pxju1g"/>
  <title>Satcat CDM Ingestion Degradation</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 31 minutes</p>
    <p><strong>Affected Components:</strong> Third-Party CDM Ingestion</p>
    <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>22:00:49</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>21:30:11</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have identified that CDM ingestion from Space-Track is showing increased latency. Our team is currently investigating the issue..</p>

        ]]>
  </content>
</entry>

<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>