Every alert, every run, last 30 days.

Updated after the run of Nov 11, 9:19 pm CT.

One row per match between a saved name and a new filing. Company and portfolio names are left off this public page, because a named match would show whom a subscriber watches. Each subscriber sees their own alerts by name, with the same timestamps, under My portfolio & alerts.

Filings stored in the last 30 days, and how many days passed between the court's filing date and the day this system first stored the record. A filing cannot be alerted on before it is stored, so this is the floor on how fast any alert can be. Each source began with a one-time load of older filings; those are counted as stored but left out of the timing figures, which cover only filings dated after the source was first watched.

The job is scheduled twice a day, at about 6:30 am and 5:30 pm Central, so a filing that reaches the public record during the day can be alerted the same day. The scheduler sometimes starts a run late; the times below are when each run actually started. Each run also re-sends any alert whose email failed during the previous week.

The raw records behind this page are public at ops/alert-runs.json and ops/alert-audit.json, and every update is a dated commit in the site's history.

Every new Chapter 11 petition in every U.S. bankruptcy court; new federal civil suits naming a saved entity; SEC Form 8-K filings under Items 1.03, 2.04 and 3.01; and commercial cases in Hillsborough County, Florida and the Harris County, Texas justice courts. State trial courts anywhere else are not watched. The full scope is on the coverage page.