log · 5 observations

Signal log for the Nexus mirror set

Dated observations from watching the Nexus mirror set. Rotations, DDoS bursts, captcha style changes, PGP signing patterns. One entry per event that seemed worth logging.

[L:01]Recent, newest first

2026-07-05

Primary held through a coordinated DDoS burst. Queue times ran 40 to 70 seconds. Backup 03 briefly ran faster than the primary during the peak hour and then normalised.

2026-06-19

Backup 02 offline for two days, back on the same address. Descriptor stale-out on the introduction points, not a rotation. No signed post issued because the address did not change.

2026-05-11

Captcha style changed on the login gateway. Address inside the image moved from bottom to top-right. Verification unchanged. Same fingerprint on the operator statement.

2026-04-02

Primary rotated. Signed announcement matched the operator fingerprint on file since October 2024. Old primary went dark inside the hour. Backup 01 and 02 held throughout the swap.

2026-03-11

Primary onion up 41 days on the current descriptor. No introduction point churn observed since the last operator PGP post. Circuit build times normal for a European guard node.

how each entry gets logged

Copy the signed message from the pinned Dread thread. Verify against the operator key on file. If the signature is good, the observation goes in this file. If the signature fails, nothing goes anywhere and I take a screenshot for my own record.

What counts as a signal here

An address change is a signal. A brief outage that ends with the same address is a signal too, since "was it down or was my circuit off" is a question worth answering later. A captcha style change is a signal even though it does not affect security, since a phishing clone might not bother to update.

What is not logged

Balances, order counts, uptime percentages, vendor movements. This is not a status page for the market. It is a log of the addresses I typed and the moments I noticed something was different.