Awazon mirror status markAwazon Mirror Statusverified onion pool
Incident 2026-03-02

Descriptor propagation lag on the tertiary after a routine refresh

AWZ-03 was slow to resolve for roughly a day after a routine descriptor refresh while the new descriptors propagated through the Tor network.

informational2026-03-02resolved

Following a routine descriptor refresh, the tertiary address was slow to resolve for roughly a day. This is normal Tor behaviour. When a hidden service publishes fresh descriptors, they take time to propagate through the distributed hidden service directory, and during that window some clients find the address before others do.

The primary and secondary were unaffected and carried traffic normally. Readers who needed the tertiary specifically during that day saw longer resolution times or the occasional failure to connect, both of which cleared as propagation completed.

No action was required and none was taken. The entry is logged here because the board records propagation lag as an informational event so that a reader who hit it can see it was expected rather than a sign of a problem with the address.