Satcat - Notice history

All systems operational

Satcat.com - Operational

100% - uptime
Feb 2026
Mar 2026
Apr 2026

Satcat API - Operational

100% - uptime
Feb 2026
Mar 2026
Apr 2026

On-Demand Screening - Operational

100% - uptime
Feb 2026
Mar 2026
Apr 2026

Third-Party CDM Ingestion - Operational

100% - uptime
Feb 2026
Mar 2026
Apr 2026

CDM Notifications - Operational

100% - uptime
Feb 2026
Mar 2026
Apr 2026

Notice history

Apr 2026

Satcat Control Center Interruption
  • Resolved
    Resolved

    This incident has been resolved. Thank you for your patience!

  • Investigating
    Investigating

    We have received reports that some user are experiencing issues loading the Control Center on Satcat. Our team is investigating the issue.

Mar 2026

Satcat service interruption
  • Resolved
    Resolved

    This incident involving Satcat services Satcat.com, Satcat API is now resolved. Thank you for your patience as our team addressed this issue.

  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    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.

Feb 2026

Increased CDM Ingest Latency
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    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

  • Identified
    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.

Outage caused by upstream service provider
  • Resolved
    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.

  • Identified
    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.

Feb 2026 to Apr 2026

Next