Year-to-date operational summary for the calendar-year-specific query population.
Year-to-date 2026: 99.94 percent aggregate uptime, three mirror rotations, four advisory-level incidents, all of which resolved within an hour. The single longest outage of the year occurred during the March DDoS event and lasted 26 minutes from advisory issuance to recovery. The most operationally significant moment of the year was the spring rotation, which introduced two new guard pools without buyer-side downtime.
Reading this page in late 2026: the trend through Q1 and Q2 has been monotonically toward stability. Q3 and Q4 outlook depends on the cold-storage signer rotation timeline (currently in pre-announce); the public timeline will appear here when signed.
Availability held while individual mirrors moved in and out of degraded states. That is what a multi address setup is supposed to look like, and it is the reason aggregate figures stay high while any single address has a rougher record.
Address rotations, which are routine, and periods of flood pressure that produced slow mirrors rather than unreachable ones. Nothing in the record suggests a structural change in how the platform runs.
Spotting whether degraded states are getting more frequent, which is the signal worth watching. A single bad week means nothing. A trend across months is a different matter and it is visible only over a window this long.
How the platform ends. Every marketplace that ever disappeared had an unremarkable availability record right up until the day it did, which is why the advice about not leaving a balance outside an open order does not depend on any of these numbers.
Component states, the 90 day uptime history and the incident log live on the status dashboard. This page covers one question in depth rather than repeating the board.