The Bankruptcy Notices Stopped. The Filings Didn’t.

Status as of Monday, Oct 19, 2026, 12:45 p.m. CT: We found no announcement that the Bankruptcy Noticing Center has been restored. The U.S. Bankruptcy Court for the District of Connecticut’s update, last updated Oct 19 at 8:00 a.m. Eastern, says: “At this time, we do not have an estimated date or time for restoration of services.” We’ll update this line when that changes.

Who this is for

Owners and operators who collect or service debt: lenders, banks and credit unions, third-party agencies and debt buyers, and in-house collections teams at tech companies. Consumer and commercial.

On scope, the statute speaks for itself. 11 U.S.C. 362(a) says a bankruptcy petition “operates as a stay, applicable to all entities.” Whether and how that reaches a specific account, debt type, or co-obligor is a question for your compliance team or counsel.

Some time in early October, the federal judiciary’s bankruptcy mail room went dark.

The Bankruptcy Noticing Center (BNC) produces and sends notices for federal bankruptcy courts nationwide, and BAE Systems runs it for the judiciary. On Oct 15, the Administrative Office of the U.S. Courts posted a notice saying BAE Systems IT and websites supporting BNC operations “have been impacted by a cybersecurity incident.” According to that notice, bnc.uscourts.gov, bankruptcynotices.uscourts.gov, notices.uscourts.gov, and the National Creditor Registration Service are unavailable, and the incident “has also halted the BNC’s production and distribution of bankruptcy notices for bankruptcy courts.”

Courts are still open. The Southern District of Florida’s Oct 14 update says the court “continues to accept filings, open cases, and process documents as usual.” The District of Connecticut says Notices of Electronic Filing to CM/ECF users “continue to be generated and distributed normally.” What stopped is the mail and email that many creditors rely on. U.S. Courts runs Electronic Bankruptcy Noticing (EBN) through the BNC, so if that’s your feed, check whether it has gone quiet.

The start date depends on who you ask. The Northern District of Texas says it was advised by the Administrative Office that the disruption began on Oct 9, 2026. Connecticut’s General Order 2026-02 says the disruption “may have begun as early as October 6, 2026.”

So here’s the operational problem. People are still filing. The notices that would normally tell you aren’t arriving.

What the statute says, in its own words

Section 362(a) of the Bankruptcy Code ties the stay to the petition. A petition filed under Sections 301, 302, or 303 “operates as a stay, applicable to all entities,” of a list of actions. One item on that list, 362(a)(6), is “any act to collect, assess, or recover a claim against the debtor that arose before the commencement of the case under this title.” Others cover lawsuits, judgments, acts against estate property, liens, and setoff.

Section 362(k)(1) says, “Except as provided in paragraph (2), an individual injured by any willful violation of a stay provided by this section shall recover actual damages, including costs and attorneys’ fees, and, in appropriate circumstances, may recover punitive damages.”

Section 342 of the Code covers notice to creditors, including provisions on effective notice and monetary penalties. How those provisions apply when the court’s own noticing system is down is exactly the kind of question to put to counsel, not to a blog.

What we’ll say as operators: the gap between a filing and your system knowing about it just got wider, and it keeps widening every day the BNC is down.

Questions to ask your team this week

None of this is exotic. It’s bankruptcy hygiene most shops already have, run on purpose instead of on autopilot. Take these to your ops lead, and take the answers to your compliance team or counsel.

Where does our bankruptcy flag actually come from?

A scrub vendor that builds from court dockets? BNC notices? EBN? Some mix? If any input runs through the BNC, it has probably been quiet since early October. Ask your scrub vendor, in writing, whether the outage affects its data and how.

What have we touched since the outage started, and what lookback window does compliance want?

Outbound attempts, payments, letters, repossession steps, legal actions. Courts have cited Oct 9 and, in Connecticut, possibly Oct 6. Pick the window with your compliance team and write down why.

Which files are expensive to get wrong?

Large balances, pending repossessions, scheduled garnishments, lawsuits about to be filed. Who on the team can check PACER directly on those, and how fast? A PACER search costs a few dollars. Unwinding a repo doesn’t.

What happens to accounts we can’t clear?

Does the cadence engine keep firing because the schedule says so, or can you put a hold flag with a reason code on them? Ask compliance whether outreach on those accounts should pause, narrow, or continue.

Does everyone know what a bankruptcy mention sounds like?

“My lawyer’s handling it.” “I filed.” “I got a case number.” Letters from bankruptcy counsel. What’s our procedure when one of those comes in, for a human collector and for an automated agent? Does that procedure differ for represented consumers? Confirm it with compliance.

Which court deadlines are we watching?

If you file proofs of claim or objections, don’t wait for mail that isn’t coming. Courts are issuing their own orders. Connecticut’s General Order 2026-02 (Oct 16) says the court “may extend or reset deadlines, continue hearings, or grant other appropriate relief as necessary to address the effects of the BNC service disruption.” The Southern District of Mississippi’s Oct 16 posting says its judges found “that the BNC outage constitutes good cause for relief under Fed. R. Bankr. P. 9006.” The Southern District of Florida entered Administrative Order 2026-06 on Oct 16. Each court is handling it a little differently, so read the orders for the courts where you have cases.

Are we writing it down?

Which accounts you rescrubbed, when, against what source, what you found, and what you did. Our view as operators: if you can’t reconstruct the decision six months from now, you didn’t really make it.

What AI agents and automation should do about it

This is where automated collections either earns trust or loses it. (This part is our opinion. It’s about systems, not law.)

An agent that calls, texts, and emails on a schedule will happily keep going through a noticing outage. It doesn’t read the news. So the controls have to live in the system, not in someone’s memory.

We think the scrub result belongs in the system as a hard gate, not a nice-to-have field. Before any outbound action, the agent checks the current bankruptcy status, and “unknown” or “stale” blocks the action instead of waving it through. During an event like this, operators should be able to tighten the freshness rule in one place. Say, no outreach on any account whose last scrub predates the rescrub. Nobody should have to edit fifty campaign scripts at 6 p.m. on a Friday.

The agent should also recognize bankruptcy language in conversation and stop. Not “acknowledge and continue.” Stop the collection conversation, tag the account, route it to a human through exception handling, and log the exact words with a timestamp. Your compliance team decides what happens next. The transcript makes sure they have the facts to decide with.

And the system should sync with the scrub vendor on a schedule, record each sync, and alert when a feed goes quiet. A bankruptcy feed that drops to zero filings for a week isn’t good news. It’s a broken pipe.

The real lesson is vendor dependency

Here’s the part that’ll outlast the outage.

Most creditors never chose the BNC. It’s just how bankruptcy notices arrive. But plenty of collection stacks quietly treat “we didn’t get a notice” as “there’s no bankruptcy.” One contractor had one incident, and that assumption failed for every creditor at once.

That’s a third-party risk problem, even when the third party is the government’s vendor and not yours. Banks will recognize the shape of it. The 2023 interagency guidance on third-party relationships says that “a banking organization’s use of third parties does not diminish its responsibility to meet these requirements to the same extent as if its activities were performed by the banking organization in-house.” Whatever your segment, the same exercise works for your scrub vendor, your dialer, your letter vendor, and yes, your AI agent vendor. What does this vendor feed into a compliance decision? How would we know if that feed stopped? What’s our fallback when it does?

If those answers aren’t written down somewhere, this week is a cheap time to write them.