Status notices
This page records every delayed or interrupted print, with the facts and the cause where it is known. Notices are posted under Operations Manual PB-02 and stay on this page after the event closes. The newest notice is first. The keys that sign every released print are listed at the end of the page, under Print-signing keys.
Print 2026-10-15: corrected by 2026-10-15-r1
| What | The August 2026 headline of print 2026-10-15, $BIRTH-N 64,610, read California, New Hampshire and Utah as zero births. The July 2026 research read also read New Hampshire as zero. |
| Cause | The federal provisional export the print read (CDC WONDER, captured 2 October 2026) was saved with the setting “Show Zero Values” on, so WONDER printed 0 for every state and month it had not yet loaded. The engine read those zeros as counts. It now skips a zero at every step of the source order (DMX decision of 31 October 2026). |
| Correction | Print 2026-10-15-r1, released 31 October 2026 at 20:22:05 UTC under Operations Manual PB-03, inside the 30-day correction window. It reads the same sources at the same cutoff, 13 October 2026 at 17:00 ET. August $BIRTH-N is 317,455 (90% band 301,043 to 330,693) over Arizona and Oregon, with the degraded live-signal coverage flag. July $BIRTH-N is 313,401. The April free layer and the S-series are unchanged. |
| Integrity | Signed under the current key, dmx-print-2026-11, and timestamped by DigiCert and Sectigo at 20:24:40 UTC. The verification run passed: file hashes, signature, both timestamps, the index entry and the revision log. The original print stays in the archive, signed and timestamped, and the index marks it superseded. |
| Found | 31 October 2026, in a check of the record that followed an outside review of the print page before it was first published. The original print was never posted on this site or sent to registrants. |
| Record | Revision-log entry 2026-10-15/r1, kind correction. Its key sentence names the 14 October key as retired; under the key policy of 22 October that key is the fallback key, as listed below. |
| Where | The corrected print and its birth_public.csv are at /prints/2026-10-15-r1/. The original is at /prints/2026-10-15/, marked superseded. |
| This notice | Posted 31 October 2026. |
Source-rights review before release, closed 30 October
| From | Print 2026-11-16, scheduled for 09:00 ET on Monday 16 November 2026 |
|---|---|
| Planned while open | Each print is still assembled at its cutoff, approved, signed, timestamped by two independent authorities at its scheduled time, and archived. It is not published while the pause lasts. |
| Why | DMX is confirming the terms on which it may publish an index built from one federal source, the NCHS provisional natality series read through CDC WONDER. The pause lasts until that review closes. |
| Planned on close | The withheld prints are released with their original signatures and timestamps, so anyone can check that each was fixed on its scheduled date. Values do not change. |
| Closed | 30 October 2026, before print 2026-11-16 was due. Release was never interrupted, and no print was withheld. Print 2026-11-16 releases on schedule. |
| Outcome | The founder of DMX signed a written determination, based on documented research, that the free national print may use the NCHS provisional series. The determination covers national-level values only, with no count of nine or fewer and NCHS and CDC WONDER credited with a provisional-data caveat. It is DMX's own determination. NCHS has not authorized or endorsed this use, and counsel has not reviewed it. Paid delivery, use in contracts, and any state or county value from this source still need separate written clearance, as Terms 9(g) states. |
| This notice | Posted 29 October 2026. Updated 30 October 2026. |
Print 2026-10-15: released late
| Print ID | 2026-10-15. The ID keeps the scheduled date. The index and the manifest mark the print delayed: true. |
| Scheduled release | 15 October 2026, 09:00 ET (13:00 UTC) |
| Release started | 16 October 2026, 12:33:04 ET (16:33:04 UTC), 1,653 minutes after the scheduled time. The release command records this time as released_at, then waits for the signature. |
| Signed bundle complete | 16 October 2026, 12:34:49 ET (16:34:49 UTC). Signature, both timestamps and the verification run finished, and the bundle was archived for publication. |
| Values | Unchanged. The cutoff stands, and every value is the one fixed at the scheduled cutoff. The delay moved the release time only (methodology section 13.7.6). |
| Cause | This is the first print released under the full publication framework, with a signed manifest. The signing step currently runs by hand and needs the Administrator at a terminal to unlock the signing key. That step did not run at 09:00 ET on 15 October. The miss was found after 17:00 ET, so under the delayed-release rule the release moved to the next business day. It ran at 12:33 ET on 16 October. |
| Integrity | The released manifest is signed and carries two RFC 3161 timestamps, from DigiCert and Sectigo, both at 16:34:49 UTC on 16 October. The verification run on the archived bundle passed: file hashes, signature, both timestamps, the index entry and the revision log. |
| Record | The revision-log entry 2026-10-15/release carries the scheduled time, the actual time and the delay. |
| Where | The print page and birth_public.csv are at /prints/2026-10-15/. The signed manifest and its timestamps are held in the DMX archive. The print was corrected on 31 October 2026 by 2026-10-15-r1; see the correction notice. |
| This notice | The procedure calls for a notice within 30 minutes of a missed release. This notice was posted on 16 October 2026, after the release, so the notice itself was late. |
| Count | First delayed print under the full publication framework in the last twelve months. Under section 13.7.6, more than two in twelve months triggers a report with a remediation plan. Print 2026-09-15, released late under the interim procedure, is listed below and does not count. |
| Postmortem | Completed 16 October 2026. Cause: release depended on the Key custodian typing the key passphrase at a terminal, and no alert fired at 09:00 ET when that step had not run. Corrective actions: an amended release procedure and a 09:00 and 09:30 release check on the server, both due before the 12 November cutoff. This entry will be updated when they close. |
Print 2026-09-15: released late
| Print ID | 2026-09-15. The ID keeps the scheduled date. The index and the manifest mark the print delayed: true. It was released under the interim publication procedure (Operations Manual PB-00), before the full publication framework began. |
| Scheduled release | 15 September 2026, 09:00 ET (13:00 UTC) |
| Released | 16 September 2026, 13:44:53 ET (17:44:53 UTC), 1,725 minutes (28.7 hours) after the scheduled time. The release ran by hand. |
| Values | Unchanged. The bundle released on 16 September is the one assembled and checked before the scheduled time: run 35, gates written at 02:36 UTC on 15 September, pass with the coverage flag. Nothing in it changed between the two dates. |
| Cause | The release step ran by hand under the interim procedure. It did not run at 09:00 ET on 15 September, and it ran on 16 September. |
| Integrity | The release manifest carries no signature and no external timestamp. The capture attestations behind every input are signed and timestamped. |
| Record | The index and the revision-log entry for print 2026-09-15 carry the scheduled time and the actual time. The revision-log entry also describes a timer release with a signature and a timestamp. The release manifest records a hand release with neither, and the manifest is correct. |
| Where | The print page and birth_public.csv are at /prints/2026-09-15/. |
| This notice | Posted 1 November 2026, 46 days after the release. No notice was posted at the time. An outside review of this site found the gap on 31 October 2026. |
| Count | The limit in section 13.7.6 counts prints released under the full publication framework, so this print is listed here and does not count toward it. |
Questions about a print are answered by print ID and revision-log reference. Write to eileen@dmxanalytics.info.
Print-signing keys
Every released print carries a manifest.json signed by DMX with an Ed25519 key, in the OpenSSH signature format (ssh-keygen -Y, namespace dmx-print), and two RFC 3161 timestamps over that signature. The keys are published here and nowhere else: a key sent by email is not a DMX key (Operations Manual PB-22). The public key files are served at /prints/keys/print.pub (current), /prints/keys/print-20261014.pub (fallback) and /prints/keys/print.pub.sig (the rotation signature described below). A key is retired at rotation and never revoked unless a compromise is found, so a print keeps verifying under the key that signed it. Only two keys can sign a new release: the current key, and the fallback key when the signing service is unreachable at release time. A retired key verifies the prints it signed and signs nothing new. This section was first posted on 22 October 2026.
| Key | Fingerprint (SHA-256) | Status | Signs |
|---|---|---|---|
dmx-print-2026-11. Generated 18 October 2026 inside a managed signing service (Google Cloud KMS); the private half cannot be exported and never touches a DMX server. | SHA256:01j4SFe09RMBU3shvNjhiul694f1CvRZ23SNVgS7DLI | Current from 20 October 2026 | Print 2026-10-15-r1 and every print from 2026-11-16 |
dmx-print key custodian 2026-10-14. Generated 14 October 2026 as a passphrase-protected file held by the Key custodian, off every server. | SHA256:KOvOJlxkZzeycslOt+ahGffr3dCYxBwDGcvlsw8OWuE | Fallback from 20 October 2026. Signs a new release only by hand, and only when the signing service is unreachable at release time. It becomes a retired key at the next rotation. | Print 2026-10-15 |
The two public keys, one OpenSSH line each. Compare the line you download with the line printed here before you trust either.
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIA0NDweTr1mr+XwSlXtCrChU0AKAeUkscDRKbsg71JvA dmx-print-2026-11
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOxvfqphP4PTdr0wYC0i0/gwyblQnJK0Hb3cDzRbNNCK dmx-print key custodian 2026-10-14
Rotation. On 20 October 2026 the fallback key signed the current key's public line, in namespace dmx-print-rotation. That signature is print.pub.sig. It ties the new key to the old one, so a reader who trusted the 14 October key can check that the 2026-11 key was introduced by its holder and not substituted. The revision-log entry of print 2026-10-15-r1, the first release under the current key, also names the rotation.
To verify a print. With manifest.json and manifest.sig from a released print, and OpenSSH 8.1 or later:
curl -sO https://dmxanalytics.info/prints/keys/print.pub
curl -sO https://dmxanalytics.info/prints/keys/print-20261014.pub
for k in print.pub print-20261014.pub; do printf 'dmx-print %s\n' "$(cut -d' ' -f1,2 $k)"; done > allowed_signers
ssh-keygen -Y verify -f allowed_signers -I dmx-print -n dmx-print -s manifest.sig < manifest.json
The last command prints Good "dmx-print" signature for dmx-print with ED25519 key followed by the fingerprint of the key that signed, which must be one of the two above. To check the rotation signature itself:
curl -sO https://dmxanalytics.info/prints/keys/print.pub.sig
printf 'dmx-print %s\n' "$(cut -d' ' -f1,2 print-20261014.pub)" > rotation_signers
ssh-keygen -Y verify -f rotation_signers -I dmx-print -n dmx-print-rotation -s print.pub.sig < print.pub
Expect Good "dmx-print-rotation" signature with the fallback key's fingerprint. Questions about a key go to eileen@dmxanalytics.info; the answer will point back to this page.