A cybersecurity incident at a federal court contractor has interrupted the system that produces and distributes bankruptcy notices nationwide, leaving courts to improvise protections for debtors, creditors and lawyers while the outage continues. The federal judiciary said the incident affected systems operated by BAE Systems Inc. for the Bankruptcy Noticing Center, or BNC, and halted the center’s production and distribution of notices for bankruptcy courts across the country.
The disruption began Oct. 9 and remained unresolved when the Administrative Office of the U.S. Courts disclosed the cybersecurity incident on Oct. 15. The office said it was coordinating with affected courts and with BAE, which was investigating and working to restore service. Reuters reported that BAE described the incident as isolated to the BNC system and said it had taken immediate steps to respond.
What the outage stopped
The BNC is not the electronic court docket itself. It is the judiciary’s centralized service for producing and transmitting official bankruptcy notices, including paper and electronic communications that tell parties about filings, hearings, deadlines and court orders. The Administrative Office said access was unavailable to BNC-operated systems and several related websites, including the National Creditor Registration Service. The outage also stopped the BNC from producing and distributing notices on behalf of courts.
That distinction matters because the broader bankruptcy system has not simply shut down. The U.S. Bankruptcy Court for the Southern District of New York said in an Oct. 13 update that electronic Notices of Electronic Filing generated through CM/ECF continued to operate normally. But notices and orders ordinarily delivered through the BNC could be delayed, and users could not generate and print a List of Creditors through the usual process.
The same court said the disruption affected every U.S. bankruptcy court and that it had no estimate for restoration. That left a patchwork problem: the national notification service was unavailable, but local courts still had active cases, hearings and deadlines to administer.
Courts build temporary safeguards
Individual bankruptcy courts responded with orders intended to prevent parties from losing rights because a notice never arrived on time. The Eastern District of Texas said in its service update that it would continue accepting filings, opening cases and processing documents through standard procedures. It warned, however, that entry and service of notices and orders — including notices of meetings of creditors — could be delayed.
That court issued two general orders addressing deadline extensions and relief tied to the interruption. It also published a temporary process for retrieving creditor names and addresses from CM/ECF when the normal mailing-matrix function was unavailable. The instructions cautioned that the creditor list does not necessarily include every person or government office entitled to service, leaving lawyers and parties responsible for checking the applicable notice requirements.
The Southern District of New York likewise entered a general order addressing the service interruption. The Wall Street Journal reported that courts in different jurisdictions adopted varying emergency measures, illustrating how a single contractor outage can create different procedural consequences from one district to another.
Why notice is central to bankruptcy
Bankruptcy cases depend on deadlines and formal notice. Creditors may need to file claims, object to proposed treatment or appear at hearings. Debtors rely on notices about required documents, meetings and the status of a discharge. Trustees, government offices and other interested parties also act on scheduled dates. A failure to receive a notice can therefore raise due-process questions and produce disputes over whether a deadline should be enforced.
The courts’ early orders do not establish that every missed notice automatically excuses late action. They instead create local protections and procedures while judges retain authority over individual cases. Parties with active matters may need to review the website and standing orders of the court handling their case, monitor the docket directly and document any service problem rather than assume a nationwide rule applies.
Questions still unanswered
Public statements have not identified who caused the incident, described the precise method of compromise or said whether sensitive court information was accessed. The judiciary has also not announced a restoration timetable. Those omissions are appropriate areas of investigation, not evidence of a particular attacker or of a data breach beyond the systems known to be disrupted.
The episode nevertheless exposes a structural risk in federal court operations. A national process that serves all bankruptcy courts depended on systems run by one outside contractor. When those systems became unavailable, local courts had to recreate parts of the notice workflow, extend protections and warn users to check service manually.
The immediate priority is restoring verified, reliable notice delivery and reconciling documents that were not sent during the interruption. The longer-term questions concern redundancy, contractor oversight, incident reporting and whether courts can maintain an independent fallback for time-sensitive communications. Until the judiciary provides a restoration notice, the safest course for parties is to treat local court orders and direct docket monitoring as essential rather than optional.
