Reports · October 2026

Every incident report, and what happened.

The record is continuous since 2026-09-05 22:10:00 UTC. Before that instant there is no record, and a missing turn means nothing.

By month: November 2026 · October 2026 · September 2026

2026-10-30 14:30:00 UTC

anchor_retried · resolved · incidents/2026/10/30/1430-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-28 15:00:00 UTC

anchor_timeout · unresolved · incidents/2026/10/28/1500-01.jws

1500-emission.jws could not be confirmed on gitlab

The write went out and the answer never came back. Asking gitlab afterwards whether the file had landed got no answer either, so it is not known whether it is there. It is not declared missing: not knowing is not knowing that it is not.

This can be checked with no credentials and without asking us for anything: ask the provider for that file's commits. If a commit shows up, the file is anchored and the provider stamped the date.

What was attempted

The emission is on both providers: GitLab answered "already exists"

The emitter sent this turn's emission file to GitHub and GitLab at 15:00:00 UTC. GitHub accepted it at 15:00:02. GitLab stored it at 15:00:09, in commit d1f370f38b, but its response did not arrive within the wait limit and the emitter gave it up at 15:00:18. Between 15:00:48 and 15:07:23 the emitter retried fourteen times, and GitLab answered every time with HTTP 400, "A file with this name already exists": the file was already there. The emitter did not take that answer as confirmation, only a separate read, and GitLab did not answer those reads in that window; that is why this report was signed saying that presence on GitLab was not confirmed. It was: emissions/2026/10/28/1500-emission.jws is on GitHub and on GitLab, byte-for-byte identical (SHA-256 52caacaa6060f7e6d4d527a0f3de28bfa4f0ee394ce3234783cc4fb523e505bf), and the emission verifies as usual. This turn lost neither proof nor redundancy. The signed report is not modified and still says "unresolved"; this explanation is what corrects it. Since the 16:20 UTC turn of October 31, 2026, the emitter takes that answer from GitHub or GitLab as confirmation that the file is there.

2026-10-27 08:10:00 UTC

anchor_retried · resolved · incidents/2026/10/27/0810-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-24 00:30:00 UTC

anchor_retried · resolved · incidents/2026/10/24/0030-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-24 00:00:00 UTC

anchor_retried · resolved · incidents/2026/10/24/0000-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-23 15:40:00 UTC

anchor_retried · resolved · incidents/2026/10/23/1540-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-23 03:20:00 UTC

anchor_retried · resolved · incidents/2026/10/23/0320-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-21 23:40:00 UTC

anchor_retried · resolved · incidents/2026/10/21/2340-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-21 12:40:00 UTC

anchor_retried · resolved · incidents/2026/10/21/1240-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-20 22:40:00 UTC

anchor_retried · resolved · incidents/2026/10/20/2240-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-20 17:10:00 UTC

anchor_retried · resolved · incidents/2026/10/20/1710-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-20 09:30:00 UTC

anchor_retried · resolved · incidents/2026/10/20/0930-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-20 07:10:00 UTC

anchor_retried · resolved · incidents/2026/10/20/0710-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-19 19:30:00 UTC

unknown_state · unresolved · incidents/2026/10/19/1930-01.jws

Not in any anchor: the 2026-10-19 19:30:00 UTC turn.

The turn was not emitted: the server could not resolve names (DNS)

The emitter started this turn at 19:27:53 UTC and, before generating anything, reads the published key registry to check that the key it is about to sign with is listed there. It could not read it from any anchor: between 19:27:57 and 19:28:20 UTC the hosting provider's DNS servers did not answer, and neither api.github.com nor gitlab.com could be resolved. Without that check the emitter does not sign, because a file signed with a key that cannot be confirmed as published could remain unverifiable forever, so the turn closed without an emission. That step comes before all the others: for this turn no seed was generated, no commitment was published and no drand round was named, so there is no 19:30 result that was left unpublished. The next turn, at 19:40, was emitted normally, and its sweep detected the gap and reported it here.

2026-10-19 08:40:00 UTC

unknown_state · unresolved · incidents/2026/10/19/0840-01.jws

Not in any anchor: 3 consecutive turns, from 2026-10-19 08:40:00 UTC to 2026-10-19 09:00:00 UTC.

The server was off during the hosting provider's security maintenance

Our hosting provider restarted its physical servers to apply an urgent Linux kernel security fix (CVE-2026-99999). Our server went down at 08:33 UTC, so these three turns did not run. No commitment was published for any of them: no seed was fixed in advance, so there is no result that could have been withheld. This can be checked with no credentials: neither repository has any file for those three turns. This report was declared later the same day, when the emitter started detecting turns that are missing from every anchor. Emission resumed with the 09:10 UTC turn.

2026-10-19 07:40:00 UTC

anchor_retried · resolved · incidents/2026/10/19/0740-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-18 22:00:00 UTC

anchor_retried · resolved · incidents/2026/10/18/2200-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-18 18:20:00 UTC

anchor_retried · resolved · incidents/2026/10/18/1820-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-18 18:10:00 UTC

anchor_retried · resolved · incidents/2026/10/18/1810-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-18 05:50:00 UTC

anchor_retried · resolved · incidents/2026/10/18/0550-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-18 02:10:00 UTC

anchor_retried · resolved · incidents/2026/10/18/0210-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-16 16:10:00 UTC

anchor_partial · unresolved · incidents/2026/10/16/1610-01.jws

Missing in gitlab

1610-commitment.jws is in github and missing in gitlab. It was anchored on 2026-10-16 16:07:56 UTC, and that date is stamped by github, not by us: it can be read without credentials by asking for the file's commits.

What this turn lost is redundancy, not proof: the commitment sits in one provider instead of two, and it cannot be replaced afterwards, because a file uploaded later would carry a date after its round.

What was attempted

2026-10-16 16:00:00 UTC

anchor_timeout · unresolved · incidents/2026/10/16/1600-01.jws

1600-emission.jws could not be confirmed on gitlab

The write went out and the answer never came back. Asking gitlab afterwards whether the file had landed got no answer either, so it is not known whether it is there. It is not declared missing: not knowing is not knowing that it is not.

This can be checked with no credentials and without asking us for anything: ask the provider for that file's commits. If a commit shows up, the file is anchored and the provider stamped the date.

What was attempted

2026-10-15 20:10:00 UTC

anchor_retried · resolved · incidents/2026/10/15/2010-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-15 03:00:00 UTC

anchor_retried · resolved · incidents/2026/10/15/0300-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-14 15:40:00 UTC

anchor_retried · resolved · incidents/2026/10/14/1540-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-13 07:10:00 UTC

anchor_timeout · unresolved · incidents/2026/10/13/0710-01.jws

0710-commitment.jws could not be confirmed on gitlab

The write went out and the answer never came back. Asking gitlab afterwards whether the file had landed got no answer either, so it is not known whether it is there. It is not declared missing: not knowing is not knowing that it is not.

This can be checked with no credentials and without asking us for anything: ask the provider for that file's commits. If a commit shows up, the file is anchored and the provider stamped the date.

What was attempted

2026-10-12 16:50:00 UTC

anchor_retried · resolved · incidents/2026/10/12/1650-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-12 12:00:00 UTC

anchor_retried · resolved · incidents/2026/10/12/1200-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-10 05:20:00 UTC

anchor_retried · resolved · incidents/2026/10/10/0520-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-10 04:00:00 UTC

anchor_retried · resolved · incidents/2026/10/10/0400-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-07 17:00:00 UTC

anchor_partial · unresolved · incidents/2026/10/07/1700-01.jws

Missing in github

1700-commitment.jws is in gitlab and missing in github. It was anchored on 2026-10-07 16:57:54 UTC, and that date is stamped by gitlab, not by us: it can be read without credentials by asking for the file's commits.

What this turn lost is redundancy, not proof: the commitment sits in one provider instead of two, and it cannot be replaced afterwards, because a file uploaded later would carry a date after its round.

What was attempted

2026-10-07 15:10:00 UTC

anchor_partial · unresolved · incidents/2026/10/07/1510-01.jws

Missing in github

1510-commitment.jws is in gitlab and missing in github. It was anchored on 2026-10-07 15:07:54 UTC, and that date is stamped by gitlab, not by us: it can be read without credentials by asking for the file's commits.

What this turn lost is redundancy, not proof: the commitment sits in one provider instead of two, and it cannot be replaced afterwards, because a file uploaded later would carry a date after its round.

What was attempted

2026-10-06 19:50:00 UTC

anchor_retried · resolved · incidents/2026/10/06/1950-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-06 16:50:00 UTC

anchor_retried · resolved · incidents/2026/10/06/1650-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-05 19:00:00 UTC

anchor_retried · resolved · incidents/2026/10/05/1900-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-05 14:10:00 UTC

anchor_retried · resolved · incidents/2026/10/05/1410-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-03 22:10:00 UTC

anchor_retried · resolved · incidents/2026/10/03/2210-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

2026-10-03 21:50:00 UTC

anchor_timeout · unresolved · incidents/2026/10/03/2150-01.jws

2150-commitment.jws could not be confirmed on github

The write went out and the answer never came back. Asking github afterwards whether the file had landed got no answer either, so it is not known whether it is there. It is not declared missing: not knowing is not knowing that it is not.

This can be checked with no credentials and without asking us for anything: ask the provider for that file's commits. If a commit shows up, the file is anchored and the provider stamped the date.

What was attempted

2026-10-03 14:20:00 UTC

anchor_timeout · unresolved · incidents/2026/10/03/1420-01.jws

1420-commitment.jws could not be confirmed on github

The write went out and the answer never came back. Asking github afterwards whether the file had landed got no answer either, so it is not known whether it is there. It is not declared missing: not knowing is not knowing that it is not.

This can be checked with no credentials and without asking us for anything: ask the provider for that file's commits. If a commit shows up, the file is anchored and the provider stamped the date.

What was attempted

This log predates each attempt naming its file: the rows may belong to any of the turn's files.

2026-10-01 15:00:00 UTC

anchor_retried · resolved · incidents/2026/10/01/1500-01.jws

It reached every anchor, but it cost

The file is byte-for-byte identical in every anchor: the same signed bytes were re-sent, so only the commit date each provider stamps differs.

What was attempted

This log predates each attempt naming its file: the rows may belong to any of the turn's files.

By month: November 2026 · October 2026 · September 2026