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. At that stage, the notice identified 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.
Update, 1 November 2026: access restored, notices still need checking
The national announcement has changed. In a 27 October update, the Administrative Office said BAE Systems had reported that the incident-related issues were resolved and the BNC was online again. That replaces the earlier availability position. It does not establish that every delayed notice has reached its recipient.
Nevada’s 30 October notice describes processing restarting effective 26 October, beginning with certificates for material collected on 7 October and mailings for material collected on 8 October. Backlogged work is being handled in phases alongside new work. Electronic notices follow validation; printed notices are released in prioritised batches as production and mailing capacity permit. The court says delayed paper notices will carry a warning that a stated response period may already have passed and an amended notice may follow.
The earlier 21 October Nevada FAQ remains useful as a record of the disruption. It said debtor electronic-notice account creation and changes were suspended, while registered CM/ECF users continued receiving Notices of Electronic Filing. It also warned that creditor lists could omit preferred electronic-notice addresses and other participants, and described a separate Party query. Those are dated operational instructions, not evidence that the services remain unavailable after restoration.
South Carolina’s filed 29 October Operating Order 26-05 says normal noticing resumed on or about 26 October, with a substantial earlier backlog expected to be served over the following week. That was an expectation, not proof of completion. It also says the interruption may have begun as early as 6 October. That possible start is separate from the 9 October contractor notification reported by Arkansas.
The national update and South Carolina order date the Bankruptcy Rules emergency declaration to 22 October; Nevada’s 30 October notice instead gives 23 October. South Carolina’s order says the declaration runs through 7 January 2027 unless terminated earlier. The declaration provides authority for certain deadline relief, not an automatic national extension. South Carolina expressly declines a blanket extension, requires a case-specific request for relief and keeps hearings in place unless otherwise ordered. Its account also excludes time periods imposed by statute. Check the responsible court’s applicable order and the particular matter’s position before treating any date as changed.
For an operational handover, keep the restoration notice, the delayed document and the evidence of actual service or receipt together. A returning system and an unresolved notice backlog can coexist. Preserve the original due date and any later court direction rather than replacing both with a single recovered status.
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.
