Satcat Status - Incident history https://status.satcat.com Satcat Sun, 27 Sep 2026 16:15:56 +0000 18th SDS SP Ephemeris Catalog Partially Outdated Type: Incident Duration: 1 day, 3 hours and 49 minutes Affected Components: On-Demand Screening Sep 27, 16:15:56 GMT+0 - Investigating - 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. Sep 28, 16:20:33 GMT+0 - Monitoring - 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. Sep 28, 20:04:30 GMT+0 - Resolved - 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. Type: Incident

Duration: 1 day, 3 hours and 49 minutes

Affected Components:

<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> ]]> Sun, 27 Sep 2026 16:15:56 +0000 https://status.satcat.com/incident/cmuk0t0tj07lt0wlcvo0kgtud https://status.satcat.com/incident/cmuk0t0tj07lt0wlcvo0kgtud Satcat experiencing service degradation Type: Incident Duration: 30 minutes Affected Components: Third-Party CDM Ingestion, CDM Notifications, Satcat API, On-Demand Screening, Satcat.com Sep 16, 15:04:01 GMT+0 - Investigating - Some users are currently experiencing issues connecting to Satcat. We are investigating the problem and working to restore access as quickly as possible. Sep 16, 15:15:34 GMT+0 - Monitoring - 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. Sep 16, 15:33:43 GMT+0 - Resolved - We are now observing nominal performance of the system. We will continue to monitor for any further interruptions. Type: Incident

Duration: 30 minutes

Affected Components: , , , ,

<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> ]]> Wed, 16 Sep 2026 15:04:01 +0000 https://status.satcat.com/incident/cmu48e5by038a13nkno4tc87s https://status.satcat.com/incident/cmu48e5by038a13nkno4tc87s Satcat API Performance Degredation Type: Incident Duration: 10 minutes Affected Components: Satcat API, On-Demand Screening Aug 3, 22:07:44 GMT+0 - Identified - 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. Aug 3, 22:18:10 GMT+0 - Resolved - We have implemented a fix and are observing a recovery in API error rates. Thank you for your patience. Type: Incident

Duration: 10 minutes

Affected Components: ,

<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> ]]> Mon, 3 Aug 2026 22:07:44 +0000 https://status.satcat.com/incident/cmsds5kvb03tk0kmrgpqumjdl https://status.satcat.com/incident/cmsds5kvb03tk0kmrgpqumjdl Satcat.com Disruption Type: Incident Duration: 39 minutes Affected Components: Satcat.com, Third-Party CDM Ingestion, CDM Notifications, Satcat API, On-Demand Screening Jul 18, 15:12:14 GMT+0 - Identified - We have identified a disruption to [Satcat.com](http://Satcat.com). A fix is being put in place. We will update you soon Jul 18, 15:24:34 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 18, 15:21:41 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 18, 15:51:08 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 39 minutes

Affected Components: , , , ,

<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> ]]> Sat, 18 Jul 2026 15:12:14 +0000 https://status.satcat.com/incident/cmrqi9ljy058s0zn0druvcf6f https://status.satcat.com/incident/cmrqi9ljy058s0zn0druvcf6f Space-track CDM Interruption Type: Incident Duration: 6 hours and 7 minutes Affected Components: Third-Party CDM Ingestion Jul 3, 17:14:31 GMT+0 - Investigating - 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. Jul 3, 18:43:49 GMT+0 - Identified - Space-Track'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. Jul 3, 23:21:45 GMT+0 - Resolved - 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. Type: Incident

Duration: 6 hours and 7 minutes

Affected Components:

<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'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> ]]> Fri, 3 Jul 2026 17:14:31 +0000 https://status.satcat.com/incident/cmr5712oi00010kn92vi4epvo https://status.satcat.com/incident/cmr5712oi00010kn92vi4epvo Satcat CDM Ingestion Degradation Type: Incident Duration: 31 minutes Affected Components: Third-Party CDM Ingestion Jun 24, 22:00:49 GMT+0 - Resolved - This incident has been resolved. Jun 24, 21:30:11 GMT+0 - Investigating - We have identified that CDM ingestion from Space-Track is showing increased latency. Our team is currently investigating the issue. Type: Incident

Duration: 31 minutes

Affected Components:

<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> ]]> Wed, 24 Jun 2026 21:30:11 +0000 https://status.satcat.com/incident/cmqsl77od02pu2iotv2pxju1g https://status.satcat.com/incident/cmqsl77od02pu2iotv2pxju1g Satcat Control Center Interruption Type: Incident Duration: 19 minutes Affected Components: Satcat.com Apr 9, 20:53:10 GMT+0 - Investigating - We have received reports that some user are experiencing issues loading the Control Center on Satcat. Our team is investigating the issue. Apr 9, 21:12:38 GMT+0 - Resolved - This incident has been resolved. Thank you for your patience! Type: Incident

Duration: 19 minutes

Affected Components:

<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> ]]> Thu, 9 Apr 2026 20:53:10 +0000 https://status.satcat.com/incident/cmnryev1n03iop6bisf8agiwa https://status.satcat.com/incident/cmnryev1n03iop6bisf8agiwa Satcat service interruption Type: Incident Duration: 14 minutes Affected Components: Satcat.com, Satcat API Mar 9, 20:58:33 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 9, 20:53:40 GMT+0 - Investigating - 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. Mar 9, 21:07:35 GMT+0 - Resolved - This incident involving Satcat services Satcat.com, Satcat API is now resolved. Thank you for your patience as our team addressed this issue. Type: Incident

Duration: 14 minutes

Affected Components: ,

<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> ]]> Mon, 9 Mar 2026 20:53:40 +0000 https://status.satcat.com/incident/cmmjns1yw001ofsyvjdq41mqm https://status.satcat.com/incident/cmmjns1yw001ofsyvjdq41mqm Increased CDM Ingest Latency Type: Incident Duration: 2 hours and 13 minutes Affected Components: Third-Party CDM Ingestion, Satcat.com, CDM Notifications Feb 24, 14:00:04 GMT+0 - Identified - 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. Feb 24, 15:41:17 GMT+0 - Monitoring - 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 Feb 24, 16:13:19 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 hours and 13 minutes

Affected Components: , ,

<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> ]]> Tue, 24 Feb 2026 14:00:04 +0000 https://status.satcat.com/incident/cmm0qv1jo00prrdjpzyj2ukle https://status.satcat.com/incident/cmm0qv1jo00prrdjpzyj2ukle Outage caused by upstream service provider Type: Incident Affected Components: CDM Notifications, Satcat API, Satcat.com, On-Demand Screening, Third-Party CDM Ingestion Feb 13, 00:54:44 GMT+0 - Resolved - 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. Feb 12, 22:03:00 GMT+0 - Identified - 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. Type: Incident

Affected Components: , , , ,

<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> ]]> Thu, 12 Feb 2026 22:03:00 +0000 https://status.satcat.com/incident/cmlk3vq9200861wxzgvw83mqu https://status.satcat.com/incident/cmlk3vq9200861wxzgvw83mqu