Home / Operations / OCELOT
SYS. STATUS
•
Orbital Client & External Liaison Terminal · INC-2024-0891
OCELOT
ORC’s integrated client portal, contact routing, quote management, and notification delivery system. Currently offline. We are aware. The situation is under active management. The previous estimated resolution date is no longer operative.
■ ACTIVE INCIDENT · INC-2024-0891 · OCELOT OFFLINE ·
DURATION: ·
STATUS: UNDER ACTIVE MANAGEMENT ·
ESTIMATED RESOLUTION: UNDER REVIEW ·
PREVIOUS ESTIMATE (Q4 2024) IS NO LONGER OPERATIVE
CURRENT UPTIME
0.00%
this calendar year
OFFLINE DURATION
—
and counting
RECONNECT ATTEMPTS
—
ALL FAILED
OPEN IT TICKETS
—
the same one. since 2024.
90-DAY UPTIME HISTORY
14 AUG 2023
■ Operational ■ Critical failure
Today
COMPONENT STATUS
Contact Form Delivery
Incoming client enquiries routed via OCELOT for processing
Quote Request Processing
S-01, S-02, S-03, S-04 quote submissions and routing
Client Notification System
Mission status updates, approvals, and correspondence delivery
Email Integration Layer
Outbound correspondence from operations leads to clients
Database Connection
Client records, mission history, and document storage
Authentication Module
Client portal login and session management
Status Update Notifications
Alerts delivered to subscribers when system status changes
This Status Page
Manual fallback. Not connected to OCELOT. Updated by IT when remembered.
LAST CHECKED: MANUALLY BY T. DAVIES · OCELOT CANNOT CHECK ITS OWN STATUS
CURRENT STATUS
OCELOT is offline.
All services affected.
All services affected.
Client enquiries should be submitted via the contact page. The contact page is processed manually by A. Kowalski until OCELOT is restored. Response times may be longer than usual. They have been longer than usual since August 2023.
LIVE RECONNECTION MONITOR
attempts since incident opened · all unsuccessful
LAST ATTEMPT:
RESULT: FAILED
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
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.
INCIDENT LOG · INC-2024-0891
OCELOT Offline — Incident Timeline
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.
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.
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
“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
“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
“We understand the problem now. Resolution is in progress.” Resolution did not follow.
12 NOV 2024
IT status 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 — INCIDENT START
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
“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.
03 / MANUAL OPS
How ORC is operating without OCELOT
OCELOT handled the majority of ORC’s client-facing and operational communications infrastructure. Since August 2023, all functions previously managed by OCELOT have been transferred to manual process. A. Kowalski manages the majority of these processes. A. Kowalski has not complained.
| Function | OCELOT’s role (when operational) | Current workaround | Responsible | Impact |
|---|---|---|---|---|
| Client enquiry routing | Automatic intake, categorisation, and routing to the appropriate ORC team member | Manual intake via contact page. A. Kowalski reads and routes all enquiries personally. | A. Kowalski | +1–2 working days |
| Quote request processing | Automated form routing to P. Patel, S-tier assignment, and acknowledgement dispatch | Manual via contact page. A. Kowalski forwards to P. Patel. P. Patel responds directly. | A. Kowalski · P. Patel | +3–5 working days |
| Mission status notifications | Automated client updates at mission milestones: launch, approach, capture, completion | Manual email from operations lead. C. Morrison also notifies on completion. | Operations lead · C. Morrison | Occasional delays |
| Document storage & retrieval | Centralised document management for all client records, mission files, and correspondence | Physical files maintained at Aeropark Estate. L. Sandhu manages the folder system. The folder system has a shelf. | L. Sandhu | Manageable |
| Report distribution | Automated delivery of C. Morrison’s post-mission reports to clients | C. Morrison emails reports directly. C. Morrison has described this as “not ideal but fine.” | C. Morrison | Minimal |
| Regulatory notification dispatch | Automated ORS submission acknowledgements and regulatory filing confirmations | L. Sandhu handles all regulatory notifications manually. L. Sandhu has confirmed this is within tolerance. L. Sandhu has a folder. | L. Sandhu | None confirmed |
| IT incident management | OCELOT was the primary incident management system for IT issues | T. Davies manages incidents manually. The primary incident is OCELOT. T. Davies is aware of this. | T. Davies | Ongoing |
NOTE · A. KOWALSKI
All OCELOT-dependent functions are being handled manually and are fully operational.
There have been no client-facing service failures attributable to OCELOT’s absence that have not been managed.
A. Kowalski would like clients to know that their enquiries are being read by a person and not a system.
A. Kowalski considers this to be, in some respects, an improvement.
04 / ATTEMPT LOG
T. Davies’s reconnection attempt log
A detailed record of significant reconnection approaches. T. Davies conducts automated attempts continuously. This log records the notable manual interventions. All attempts have failed. T. Davies is aware that this log is public. T. Davies has no comment on it.
| Date | Method | Result | Details |
|---|
SIGNIFICANT ATTEMPTS ONLY · AUTOMATED ATTEMPTS OCCUR CONTINUOUSLY · ALL AUTOMATED ATTEMPTS HAVE ALSO FAILED · T. DAVIES: AWARE · T. DAVIES: CONTINUING
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.” This description has not been revisited.
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
SUBMIT A RECONNECTION REQUEST
Have an idea for restoring OCELOT? Submit it here. T. Davies will receive it. T. Davies may have already tried it. T. Davies will try it again if not.
RAISE AN IT TICKET
There is currently one open ticket. It has been open since 2024. You may raise an additional ticket. T. Davies is aware that the ticket count will increase. T. Davies is fine with this.
OPEN TICKETS
—
INC-2024-0891 is ticket number one. It remains open.