Satcat Status - Incident history https://status.satcat.com Satcat Thu, 9 Apr 2026 20:53:10 +0000 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