Bankruptcy Notices Stopped
Filing a document, sending a notice and proving receipt are separate operational questions. An incident report needs to say which one it can answer.
On 15 October, the US Courts confirmed a cybersecurity incident affecting BAE Systems technology for the Bankruptcy Noticing Center. The contractor operates its systems for the federal judiciary; BNC notice production and distribution had stopped nationwide. Access to bnc.uscourts.gov, bankruptcynotices.uscourts.gov, notices.uscourts.gov and the National Creditor Registration Service was unavailable. BAE was investigating and working to restore operations. The notice identifies no actor, ransomware, entry route, data-access outcome or restoration estimate.
The Arkansas court notice dated 13 October places BAE’s notification of the disruption late on 9 October. Keep that operational history separate from the later public explanation of its cause. None of these pages supplies an exact publication time.
Court operations need their own check
The Eastern District of Texas said on 14 October that filings, new cases and document processing would continue. Notices, orders and 341 Notices could be delayed. It linked two local general orders addressing extensions and deadline relief.
The Northern District of Texas said on 15 October that hearings would proceed unless ordered otherwise. It described requests for deadline or hearing relief, not an automatic extension, and also confirmed that filings and case processing continued. These are local arrangements, not national relief.
The District of South Carolina’s 13 October notice said its CM/ECF Notice of Electronic Filing email system continued normally. That is a statement about this district’s NEFs, not a national finding that every court email or notification route works.
A useful handover is matter-specific
Consider a hypothetical operations team waiting for a time-sensitive notice. Its dashboard says that the associated document was filed, but the expected message has not arrived. BlackTree recommends retaining both observations. The filing entry and the missing message describe different events; neither should be overwritten merely to produce a single status colour.
A practical handover should identify the responsible court, expected notice, observed docket entry, expected recipients, delivery channel, accountable owner and next check. Reference the official status page or order used, together with the time it was read. Keep filed, entered, served and received as separate states. This is a proposed evidence record, not a legal determination that service has occurred.
Both Texas notices describe a CM/ECF creditor-list workaround for the affected mailing matrix. They warn that the list omits some interested parties. Use the courts’ own instructions and check the applicable service requirements; do not mistake an available address list for a complete recipient set.
The same discipline applies to automation. In the hypothetical example, a mailbox check can establish what arrived in that mailbox. It cannot, by itself, explain why something did not arrive. Record the check’s scope rather than reporting an unexplained absence as proof of successful delivery or a particular cyber mechanism.
Recovery needs its own evidence
When a restoration statement becomes available, record precisely what it restores and what remains untested. A working web page and a completed notice delivery are not interchangeable acceptance tests. The appropriate operational owner should define the expected result and retain the evidence supporting the decision.
Keep the investigation statement separate. An availability finding does not establish a conclusion about earlier access or data handling. Conversely, an unanswered investigation question should remain visible rather than being filled with an attribution guess. BlackTree has not independently tested these court systems or examined an affected case.
This report explains the public operational notices, not a party’s legal obligations. Use official court channels and qualified advice for case-specific deadlines, hearings and service. Preserve delivery-failure evidence and the basis of any workaround so the next person can understand what was actually checked.
