OCELOT

■ ACTIVE INCIDENT · INC-2024-0891 · OCELOT OFFLINE · DURATION: 653 DAYS · STATUS: UNDER ACTIVE MANAGEMENT · ESTIMATED RESOLUTION: UNDER REVIEW · PREVIOUS ESTIMATE (Q4 2024) IS NO LONGER OPERATIVE

CURRENT UPTIME

0.00%

this calendar year

DAYS OFFLINE

653

and counting

RECONNECT ATTEMPTS

1,412

all failed

OPEN IT TICKETS

the same one. since 2024.

90-day uptime history

14 AUG 2023

■ Operational ■ Degraded ■ Critical failure

Today

Component status

Contact Form Delivery

Incoming client enquiries routed via OCELOT for processing

Critical failure

Quote Request Processing

S-01, S-02, S-03, S-04 quote submissions and routing

Critical failure

Client Notification System

Mission status updates, approvals, and correspondence delivery

Critical failure

Email Integration Layer

Outbound correspondence from operations leads to clients

Critical failure

Database Connection

Client records, mission history, and document storage

Critical failure

Authentication Module

Client portal login and session management

Critical failure

Status Update Notifications

Alerts delivered to subscribers when system status changes

Critical failure

This Status Page

Manual fallback. Not connected to OCELOT. Updated by IT when remembered.

Operational

Incident log · INC-2024-0891

NOTE FROM IT DEPT · PINNED · SEP 2024: This incident is being actively managed. We anticipate resolution by end of Q4 2024. Please continue to use the contact page for urgent enquiries. Staff should route all client communication manually until OCELOT is restored.
ADDENDUM · MAY 2026: The above note was written in September 2024. We are reviewing the Q4 2024 estimate. The situation remains fluid. We remain optimistic in the broad sense.

24 MAY 2026 · 07:14 BST

Reconnection attempt 1,412 · Failed

Automated reconnection attempt initiated at scheduled interval. OCELOT did not respond. This is consistent with all previous attempts. Logged automatically.

14 MAY 2026

Patch v2.4.1 deployed · Failed

IT deployed patch v2.4.1 following extended testing. Initial diagnostic showed promising response from OCELOT core module. OCELOT subsequently stopped responding to diagnostics as well.

“We were optimistic about this one.” — IT Dept, 14 May 2026, 16:02

02 APR 2026

Third-party consultant engaged · Inconclusive

External systems consultant retained to assess OCELOT architecture. Consultant submitted preliminary report identifying 14 potential root causes. Consultant is currently uncontactable. Their contact system appears to also be offline.

11 JAN 2026

Full system reinstall attempted · Failed (novel failure mode)

IT performed complete wipe and reinstall of OCELOT environment. OCELOT reinstalled with an error in the base configuration that had not previously existed. IT notes this represents “meaningful progress in understanding what not to do.”

03 NOV 2025

Escalated to original vendor · Pending

Support ticket raised with OCELOT’s original vendor. Vendor acknowledged receipt. Vendor’s support portal is currently experiencing intermittent availability. We are monitoring.

19 AUG 2025

IT status update

IT issued internal update: “We are getting closer. We believe the issue may be related to the authentication module, the database layer, the email integration, the core routing logic, or some combination of these. Further investigation ongoing.”

04 MAR 2025

IT status update

IT issued internal update: “We understand the problem now. Resolution is in progress.” Resolution did not follow.

12 NOV 2024

IT status update

IT issued internal update: “We are aware of the problem.” This was not in question.

02 SEP 2024

Formal incident ticket opened · INC-2024-0891

Following extended informal investigation, IT opened formal incident ticket INC-2024-0891. Estimated resolution: Q4 2024. Priority: High. Current status: Open.

14 AUG 2023 · 23:47 BST

OCELOT went offline

OCELOT ceased operation at 23:47 BST. Initial assessment suggested a routine timeout. Further assessment revised this conclusion. Root cause investigation opened. Root cause investigation ongoing. Root cause: unknown.

“We expect this to be resolved by morning.” — IT Dept, 14 Aug 2023, 23:52

14 AUG 2023 · 09:00 BST

OCELOT v2.3.7 deployed · Operational

Routine version update deployed successfully. All systems nominal. Uptime: 100%. Everything fine.

CURRENT STATUS

OCELOT is offline.
All services affected.

Client enquiries should be submitted via the contact page. The contact page is processed manually by staff until OCELOT is restored. Response times may be longer than usual. They have been longer than usual since August 2023.

STATUS UPDATES

Subscribe to be notified when OCELOT status changes.

Notifications are delivered via OCELOT.

NEED URGENT HELP?

For active missions: contact your named operations lead directly. Their number is in your welcome pack.

For new enquiries: contact page. Manual processing. 1–2 working days.

For IT issues with OCELOT: it@orbitalrecoverycrew.com.

The IT team email is not routed through OCELOT. It is a normal email address. We checked.

LIVE RECONNECTION MONITOR

attempts since incident opened

all unsuccessful

LAST ATTEMPT: 07:14 BST

RESULT: FAILED

ABOUT OCELOT

OCELOT (Orbital Client & External Liaison Terminal) was commissioned in 2019 and went live in 2021 following an 18-month implementation. It was described at launch as “a significant step forward in client communication infrastructure.”

SYSTEM DETAILS

Version: 2.3.7 (last stable)
Environment: [REDACTED]
Hosting: On-premises, Hangar 7
Backup system: OCELOT
Failover: OCELOT
Disaster recovery: OCELOT

RELATED SYSTEMS

ORC Mission Control: Operational
Flight Operations Terminal: Operational
Internal Comms (non-OCELOT): Operational
This Status Page: Operational
OCELOT: Offline

Subscription request received.